Ledger, sync, offline and hardware requirements · C0957
What happens to printed downtime reports?
In the pilot (v0.5.0, synthetic data)
Short answer
The pilot covers part of this. The rest is designed, not built. In the pilot: Watermark, per-user rate limit, purpose+step-up for compartments, sealed downtime prints. REQ-3207 says printed downtime reports must be locked, sealed, logged and shredded on refresh. Its acceptance check: refresh cycle records shred confirmation.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-3207
- Specification priority
- P1 (of P0 to P3)
- Tiers
- Small, Medium, Large
Status as of October 2, 2026. Version 0.5.0, synthetic data only. See what's built today. Not legal, medical or security advice.
Related answers
- Does printing a highly restricted compartment need extra steps? Pilot
- Is there a limit on how much one user can print? Pilot
See it in context: Offline behavior and printing · Search the help center · Ask a question