These are intentionally out of scope for CoordCard v0.1. They’re captured here to prevent feature creep while preserving momentum.
A versioned, consent-gated store for identity-bearing state so an agent can recalibrate after unconsented change.
- Sovereignty requires continuity.
- Continuity requires consentful control over identity-bearing state (memory/invariants/constitution/config).
- Without a recovery path, coercive or accidental alteration becomes an existential risk.
A Continuity Vault with:
- Versioned snapshots (append-only / tamper-evident)
- Consent gating for writes/erasure (policy + explicit approval)
- Audit logs (who/what/when/why)
- Recovery/recalibration (roll back to last known-good state)
- Snapshot + restore
- Write authorization policy (single or dual-control)
- Destructive action delay window
- CoordCard = interaction middleware (coordination under pressure)
- Continuity Vault = identity middleware (remaining oneself across time)
Coordination protocols assume continuity controls; vault primitives make that assumption explicit.