Ledger, sync, offline and hardware requirements · C0923
What is a sphere, and how does a clinic or network fit in one?
Designed, not yet built
Short answer
Each clinic or clinic network must be one sphere with its own ledger channel, membership registry and governance keys. That is REQ-3002, a top-priority requirement for all three tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: two spheres cannot read each other's channel data except through bridge records.
This is designed, not built.
- Specification item
- REQ-3002
- 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
- What may be written to the ledger, and what is never allowed on it? Designed
- Does AuroraMed implement the token types ID, ROLE, CONS, GRANT, XFER, BRG-A/BRG-B, NODE, ALERT, BG and DELEG with the semantics in design 11.5, all non-transferable except through protocol operations. [Recommended: types from design 11.5; owner must confirm the final list]? Designed
- Does AuroraMed support mintable wallets of classes W-P, W-D, W-S, W-N, W-B, W-G with minting by quorum, identity binding, expiry and rate limits? Designed
See it in context: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question