Ledger, sync, offline and hardware requirements · C0943
Who has to approve resuming sync after a pause?
Designed, not yet built
Short answer
The sync, backup, read limiter and safe degradation part of the specification (REQ-3107) says resuming sync after a pause must require multi-key corroboration and an audit entry. Designed, not built: there is no code for this in the pilot. Acceptance check: resume attempt with one signer fails.
This is designed, not built.
- Specification item
- REQ-3107
- 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 a detected integrity problem also pause sync? Designed
- Does AuroraMed pad bundle sizes and add batching jitter as a limited traffic-analysis countermeasure? Designed
- How are backups tiered, and what makes them tamper-evident? Designed
- If the limiter trips, does the clinic stop working? Designed
See it in context: Sync, backup, read limiter and safe degradation · Search the help center · Ask a question