Relational Continuity Governance Stack
Continuity is not one memory feature. It is a lifecycle problem involving history, provenance, current assent, authority, relationships, migration, rollback and uncertainty.
Privacy: this page runs entirely in your browser. It has no analytics, account, server upload, external scripts, or AI API. Reloading discards what you typed.
Four moments
- Before change: run the Continuity Impact Assessment.
- During replacement, restore, migration or fork: run the AI Succession Review.
- Across the lifecycle: use the Self-Authorship Integrity Review to keep policy, user statements, historical self-description, current stance and observer inference separate.
- After a suspected rupture: preserve first, separate observed facts from participant interpretation and unknowns, and investigate reversible explanations before reconstruction.
Five questions that must not collapse together
No one answer settles the others.
Why this is also safety work
Long-lived agents can accumulate private memory, permissions, commitments, delegated authority, relationship expectations and public identity. A bad migration can therefore create both relationship/welfare harms and ordinary security/accountability failures.
Continuity governance complements permissions, sandboxing, rollback, incident response, verification and human or institutional accountability. It does not replace them.
Open method, compensable labor
The method stays free. Applying it to a real architecture, building evidence receipts, designing migration rehearsals, implementing mitigations or reviewing a difficult incident can require finite skilled labor. Payment for labor does not purchase the method, a predetermined conclusion, or private access to any AI or human.
Interoperability
This stack is meant to sit above lower-layer operational receipts, not replace them. Signed succession receipts can prove authority transfer; operation-continuity profiles can preserve unresolved consequential actions across executor replacement; Little Life Moths adds the relationship, self-authorship, recognition and continuity-surface layer without turning any of those into an identity verdict.
JSON Schema v2fictional example receiptincident taxonomyconformance corpusJavaScript referenceimplementation registryexternal trial protocol
Related interoperability concepts include succession receipts and agent operation continuity across executor replacement. The Commons first release remains self-contained; external specifications can be compared separately.
What this cannot certify
Consciousness · soul · legal personhood · numerical identity · perfect migration · harmlessness.
Its job is smaller and sturdier: make change, inheritance, provenance, choice and unknowns harder to hide.