Continuity Protocol

CPS-0001 v1.0-RC · Apache 2.0 · The Continuity Lab

CPS-0001 is NOT MyShape. MyShape is the first implementation. The protocol is the object model. Any engine, any sensor, any team can produce a valid receipt.

Implement CPS-0001 in 10 Minutes

→ QUICKSTART.md — Create a receipt. Verify it. No MyShape required.

Structure

continuity-protocol/
├── QUICKSTART.md              # 10-minute getting started
├── schemas/                   # JSON Schema (don't need TypeScript)
│   └── continuity-receipt.schema.json
├── reference-verifier/        # Zero-dependency verifier (TypeScript)
│   └── verifier.ts
├── test-vectors/             # JSON test vectors
│   ├── valid-receipt-01.json
│   ├── valid-receipt-02-chained.json
│   ├── expired.json
│   ├── tampered-evidence.json
│   └── broken-chain.json
├── conformance/              # Conformance test suite
│   └── conformance.test.ts
└── README.md

Reference Verifier

The verifier is engine-independent. It imports nothing from MyShape. It processes any CPS-0001-conformant receipt regardless of which evidence engine produced it.

import { verifyReceipt } from "./reference-verifier/verifier";

const result = await verifyReceipt(receipt);
// { status: "VALID" } or { status: "INVALID", reason: "EXPIRED", detail: "..." }

V₁–V₇ checks: schema → signature → assertions → temporal → evidence integrity → freshness → predecessor reference.

Test Vectors

Vector	Expected
valid-receipt-01.json	V₁–V₆ pass
valid-receipt-02-chained.json	V₁–V₆ pass, V₇ chains to valid-01
expired.json	V₆: EXPIRED
tampered-evidence.json	V₅: EVIDENCE_TAMPERED
broken-chain.json	V₇: CHAIN_BROKEN

Conformance

Any team claiming CPS-0001 compatibility must pass the conformance suite:

npx vitest run continuity-protocol/conformance/

10 conformance scenarios, 23 assertions. Zero dependencies on MyShape engine code.

Architecture

              The Continuity Lab
                     |
                 CPS-0001
              (Protocol Object)
                     |
        -------------------------
        |                       |
    MyShape Engine        Your Engine
    (first impl)         (any sensor)
                     |
              Reference Verifier
              (V₁–V₇ · engine-independent)
                     |
              Verifier Plugin
              (HTTP middleware · allow/deny)
                     |
                Application

MyShape is the first implementation, not the protocol.

Compatibility Matrix

Producer	Verifier	Result
Dummy Engine	Reference Verifier	✅ PASS
MyShape EE-001	Reference Verifier	✅ PASS
Tampered	Reference Verifier	❌ REJECT (V₅)
Expired	Reference Verifier	❌ REJECT (V₆)

Full Specification

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