Continuity Core
Concept identity, automatic checkpoints, project resurrection, and source-authority separation
Continuity Core addresses a failure that appears above individual apps: projects, concepts, decisions, aliases, receipts, and implementation state are scattered across providers, repositories, files, and conversations. It defines an account-level continuity substrate with stable concept identity, event-sourced canon, alias and supersession edges, automatic checkpoints, source and authority labels, and a resurrection protocol that can reconstruct what a dormant project is, what is accepted, what is blocked, and what should happen next.
Current evidence state
SPECIFIED
This label describes the strongest public-safe state of the specific paper claims. Open the paper's claim ledger for claim-level distinctions and limitations.
Publication
- Full paper:
/papers/p25-continuity-core - Claim ledger:
content/papers/p25-continuity-core/claim-ledger.json - Source manifest:
content/papers/p25-continuity-core/source-manifest.json - Diagrams: 3
- Approximate body length: 1,230 words
Demonstrations
d17-continuity-resurrection
Benchmarks
b12-continuity-recovery
Public boundary
The research entry publishes a public-safe architecture and evidence record. It does not grant implementation rights or expose restricted claim-ready material.