AuroraMed v0.2.0 is a synthetic-data pilot. See exactly what's built →

Ledger, sync, offline and hardware requirements · C0957

What happens to printed downtime reports?

Designed, not yet built

Short answer

Designed, not built: there is no code for this in the pilot. REQ-3207 says printed downtime reports must be locked, sealed, logged and shredded on refresh. Its acceptance check: refresh cycle records shred confirmation.

This is designed, not built.

Specification item
REQ-3207
Specification priority
P1 (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

See it in context: Offline behavior and printing · Search the help center · Ask a question

See the synthetic-data demo first.Request a demo