Ledger, sync, offline and hardware requirements · C0940
What is the read-side limiter and what does it limit?
Designed, not yet built
Short answer
A read-side limiter on a node en route to the server must limit reads and pulls (not writes) using oscillating time windows. Window length, oscillation pattern and per-role/per-terminal quotas are (still an open decision). That is REQ-3104, a top-priority requirement for all three tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: limiter config parameters exist and default to disabled-with-logging until set; when enabled, read counts above quota trip. Parts of it are explicitly marked as open in the specification.
This is designed, not built.
- Specification item
- REQ-3104
- 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
- Can clinics sync directly with each other? Designed
- If the limiter trips, does the clinic stop working? Designed
- Does a detected integrity problem also pause sync? Designed
- What does a sync bundle contain, and how is it protected? Designed
See it in context: Sync, backup, read limiter and safe degradation · Search the help center · Ask a question