Ledger, sync, offline and hardware requirements · C0948
Does the pilot include the scroll-rate lock?
Designed, not yet built
Short answer
REQ-3112 is a top-priority requirement for all three tiers: the scroll-rate lock must require re-authentication when history-tab throughput exceeds the threshold (still an open decision), computed server-side by information rendered, with different weights for HISTORY and RESULTS_TRIAGE. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says scripted paging trips the lock; triage scrolling does not. Parts of it are explicitly marked as open in the specification.
This is designed, not built.
- Specification item
- REQ-3112
- 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 does an erasure request reach the backups and replicas? Designed
- What relaxes in a declared emergency? Designed
- Can one person bulk-export records? Designed
- How would a restored backup be checked before going live? Designed
See it in context: Sync, backup, read limiter and safe degradation · Search the help center · Ask a question