Ledger, sync, offline and hardware requirements · C0947
How does an erasure request reach the backups and replicas?
Designed, not yet built
Short answer
Designed, not built: there is no code for this in the pilot. REQ-3111 says erasure requests must propagate as tombstone bundles and key destruction events. Its acceptance check: restored backup lacks decryptable erased data.
This is designed, not built.
- Specification item
- REQ-3111
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Small, Medium, Large
Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.
Related answers
- How would a restored backup be checked before going live? Designed
- Does the pilot include the scroll-rate lock? Designed
- What relaxes in a declared emergency? Designed
- How are backups tiered, and what makes them tamper-evident? Designed
See it in context: Sync, backup, read limiter and safe degradation · Search the help center · Ask a question