PROTOCOL OVERVIEW
STATUS: v1.0-RC
PHASE: RESEARCH_CANDIDATE
PHASE: RESEARCH_CANDIDATE
Five-Layer Architecture
LCPS
PROTOCOL OBJECT
CPS-0001 Continuity Receipt · Assertions · Trust Model · Verification Contract
rc
LRFC
SPECIFICATION
RFC-0001 Motion Signature · RFC-0002 Continuity Proof
published
LEE
EVIDENCE ENGINES
EE-001 Presence · EE-002 Causal Coupling · EE-003 Challenge
active
LVS
VERIFICATION
Dual-Engine Pipeline · Escalation Logic · CFC Detection
active
LSDK
DEVELOPER SURFACE
npm install @thecontinuitylab/myshape · verifyContinuity()
published
Specification Implementation
CPS-0001rc
Continuity Protocol Core
Protocol object, semantics, trust model, verification contract. Engine-independent. v1.0-RC.
RFC-0001draft
Motion Signature Format
PES, jerk detection, cross-modal matching, challenge-response protocol
RFC-0002draft
Continuity Proof Format
Evidence receipts, CFC catalog, predecessor chaining, verification policy
EE-001active
Presence Detection
4D entropy scoring: micro-timing, noise residual, frequency entropy, perturbation
EE-002active
Causal Coupling
IMU + camera event matching ±500ms. Temporal alignment: 100%
EE-003active
Challenge Response
3-round gyroscope challenge. Jittered timing. Anti-replay.
VS-001active
Verification Session
Dual-engine pipeline. Passive → escalate → aggregate → verdict
npmpublished
SDK
verifyContinuity(). npm install @thecontinuitylab/myshape. 120 tests. Apache-2.0.
Protocol Engines
| Engine | Description |
|---|---|
| Presence Detection (EE-001) | 4D entropy scoring from IMU data. Distinguishes embodied entities from synthetic motion. |
| Causal Coupling (EE-002) | Cross-modal event binding. Proves IMU and camera observe the same physical event. |
| Gyroscope Challenge (EE-003) | 3-round randomized directional challenge with jittered timing. Defeats replay. |
| Verification Session (VS-001) | Dual-engine pipeline. Passive presence + active challenge escalation. |
| Reference Verifier | CPS-0001 conformance suite. 23 assertions, 10 scenarios. Zero engine deps. |
Protocol Status
●
Research Candidatev1.0-RC · CPS-0001 frozen · 120 tests · reference verifier · conformance suite○
Protocol CandidateCommunity review · third-party implementations · interoperability validation○
Stablev1.0 release · RFC 3161 public timestamp · ecosystem adoptionProtocol Lifecycle
01
CaptureSensor DataIMU at 60Hz + camera at 7Hz. All processing on-device. No raw data leaves the device.02
ExtractEvidence EnginesJerk peak detection, direction changes, cross-modal matching. Per-component diagnostics.03
EvaluateVerification PolicyConfidence thresholds. Escalation logic. CFC checks. Evidence → Verdict.04
ReceiptEvidence ReceiptSHA-256 hash-chained. Verifiable by any conforming verifier. RFC-0002 compliant.05
VerifyAny VerifierOpen specification. Reference implementation. Anyone can build a compatible verifier.From sensor capture to cryptographic receipt. Each step independently verifiable. No raw data stored. No centralized intermediary.
Protocol Ecosystem
PROTOCOL OBJECTCPS-0001
ContinuityReceiptAssertion · Evidence · Context · SignatureV₁-V₇Verification contract · engine-independentConformance23 tests · 10 scenarios · zero deps
SPECIFICATION LAYEROPEN_STANDARDS
RFC-0001Motion Signature FormatRFC-0002Continuity Proof Format
EVIDENCE ENGINESVERIFICATION
EE-001Presence Detection · 100% floorEE-002Causal Coupling · N=316EE-003Gyroscope Challenge · N=200VS-001Dual-Engine Pipeline · 93%
DEVELOPER SURFACESDK_AND_TOOLS
npm SDK@thecontinuitylab/myshapeReference VerifierZero engine deps · TypeScriptGitHubOpen source · Apache 2.0
EXPERIMENTAL DATAREPRODUCIBLE
576 Runs4 engines · consumer hardwareHuggingFaceDataset · open access120 TestsAutomated verification · CI
RESEARCH FOUNDATIONTHE_CONTINUITY_LAB
CPS-0001Core Protocol SpecificationResearch NotesRN-001 · RN-003 · CPS-0001Failure ReportsFD-001 · DL-001