Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1,024 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

CPS-0001

A verifiable temporal trust layer for digital entities.

CPS-0001 npm Tests License Discussions CITATION.cff Giveth

Research by The Continuity Lab. CPS-0001 is a protocol — not a product, not a company, not a token. MyShape is the first protocol implementation, maintained separately.


What Is CPS-0001?

CPS-0001 defines the Continuity Receipt — a cryptographically verifiable statement that an observer collected sufficient evidence supporting the continuity of a subject over a bounded interval of time.

It is engine-independent. No sensor type, algorithm, or hardware requirement appears in the specification. A third party can build a completely different evidence engine and produce a valid receipt.

The protocol standardizes the object, not the engine.

Implement It Yourself

IMPLEMENT.md — Create a receipt in 1 hour. No MyShape. No IMU. No camera.

QUICKSTART.md — 10-minute getting started.

The Closed Loop

Producer (any engine) → Continuity Receipt → Verifier (V₁-V₇) → Consumer Decision
Component What File
Reference Verifier V₁-V₇, zero MyShape deps reference-verifier/verifier.ts
HTTP Verifier Plugin Express middleware, allow/deny + risk verifier-plugin/
Second Producer Dummy engine — proves independence second-producer/
JSON Schema Schema-first validation schemas/
Test Vectors 5 reference receipts test-vectors/
Conformance Suite 23 assertions, 10 scenarios conformance/

Independent Implementation Challenge

CPS-0001 is an open protocol. We are looking for independent implementations — developers who implement a compatible producer or verifier without reading MyShape engine code.

You do not need:

  • MyShape source code or SDK
  • Permission or coordination
  • IMU sensors or phones

You do need:

The goal is simple: generate or verify a valid Continuity Receipt. No product integration required.

External Onboarding Kit — 30 minutes, self-guided.

Open an issue to list your implementation.

The first independent implementation will be listed in the CPS-0001 ecosystem page.

We Don't Know If Anyone Needs This

CPS-0001 was published before adoption evidence was available. We are running structured discovery interviews to find out whether teams in robotics, XR, security, and AI agent frameworks encounter a real continuity problem.

Research Note: Why We Published Before Adoption

Discovery Survey — 5 minutes. Pure research.

Quick Install

npm install @thecontinuitylab/myshape
import { verifyReceipt, buildReceipt } from "@thecontinuitylab/myshape";

const receipt = buildReceipt({ /* your evidence */ });
const result = await verifyReceipt(receipt);
// { status: "VALID" }

Full Specification

myshape.com/research/notes/008-continuity-protocol-core

License

Apache 2.0. MyShape is the first implementation. The protocol is public.

About

CPS-0001 (Continuity Protocol Standard) — a verifiable temporal trust layer for digital entities. Continuity Receipts: engine-independent, Ed25519-signed, time-based trust for autonomous systems, AI agents, and embodied subjects. Research by The Continuity Lab.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages