Ledger, sync, offline and hardware requirements · C0945
How are backups tiered, and what makes them tamper-evident?
Designed, not yet built
Short answer
No. The specification describes it, but the pilot does not include it. For reference, REQ-3109 (a top-priority requirement, all three tiers) says the system must implement 3-2-1-1-0 backup tiers T0-T5 with immutable copy and offline copy, and must anchor backup ranges on the ledger. Check: anchor exists for each range; tamper of a bundle is detected on restore.
This is designed, not built.
- Specification item
- REQ-3109
- 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
- Does AuroraMed pad bundle sizes and add batching jitter as a limited traffic-analysis countermeasure? Designed
- How would a restored backup be checked before going live? Designed
- How does an erasure request reach the backups and replicas? Designed
- Who has to approve resuming sync after a pause? Designed
See it in context: Sync, backup, read limiter and safe degradation · Search the help center · Ask a question