Expand description
Circle metadata, access records, controls, and creation objects.
Structs§
- Access
Envelope Body - The wire body of one recipient’s access envelope. Every field here is signed.
- Active
Circle Epoch Core - Circle
Access Leaf Body - The wire body of one recipient’s Circle access leaf. Every field here is signed.
- Circle
Bootstrap Coverage Ref - The exact retained bootstrap coverage a recipient device’s live Circle
projection was seeded from: the activating Store commit, the control it
activated under, and the bootstrap reference (its exact cut and image hash
live inside that reference, not re-declared here). Names one row of
circle_bootstrap_coverage. - Circle
Bootstrap Ref - Exact Circle database image offered when one recipient becomes active.
- Circle
Control Body - The wire body of one Circle control. Every field here is signed.
- Circle
Control Coord - Exact coordinate of one signed circle control entry.
- Circle
Control Coord Error - Circle
Control Value - Circle
Epoch Close - Circle
Epoch Close Cancellation Ref - Circle
Epoch Close Exclusion Ref - Circle
Epoch Close Intent Ref - Circle
Epoch Close Outcome Ref - Circle
Epoch Close Participant - Circle
Epoch Close Response Ref - Circle
Epoch Successor - Circle
Metadata Body - The wire body of one Circle metadata entry. Every field here is signed.
- Circle
Metadata Coord - Circle
Metadata Head Ref - Circle
Roster Policy Objects - Circle
Transition Draft - Circle
Transition Draft Policy - Circle
Transition Policy Objects - Deleted
Circle - A terminal deletion. It freezes the epoch spine it terminated — the same
MergeActiveCircleEpochanEpochClosefreezes — so historical package verification and exact reclamation keep the epoch, key fingerprint, and roster-head spine with no live access material. - Merge
Active Circle Epoch - Merge
Circle Control Head Ref - Merge
Circle Control Order - Merge
Circle Metadata State Ref - Prepared
Access Leaf - Prepared
Circle Access - Prepared
Circle Control - Prepared
Circle Transition - Resolved
Conflict Branch - One losing branch of a resolved control conflict, carried so the resolution can cover every branch’s frontier rather than only the chosen branch’s: the branch’s control head, its metadata and roster head frontiers, and the metadata entry that branch selected. The resolution unions these into its own frontier so no author-stream head is re-allocated once the conflict collapses, and re-derives its name as the deterministic metadata selection across the union.
- Store
Membership State Ref - The exact Store membership state whose identities require access dispositions.
Enums§
- Circle
Access Disposition - Circle
Control State - Circle
Epoch Close Response Slot Value - The exactly-one value a participant’s create-once close-response slot holds: the device’s own signed response, or an Owner-signed exclusion of that device.
- Circle
Epoch Close Settlement - One participant’s contribution to a close outcome: either its verified device response (whose frontier joins the cutoff) or an Owner exclusion (which does not). The outcome carries one per participant.
- Circle
Epoch Close Slot Value - The exactly-one value the create-once epoch-close outcome slot holds. Readers parse this tagged form and dispatch on the settled arm: a final outcome rotates to a successor epoch, a cancellation reopens the frozen epoch.
- Circle
Epoch Origin - Circle
Roster Draft Policy - Circle
Semantic Slot - Circle
Transition Error - Merge
Circle Owner Authority Ref - Merkle
Step
Functions§
- circle_
control_ head_ prefix - circle_
epoch_ close_ intent_ semantic_ prefix - circle_
epoch_ close_ outcome_ semantic_ prefix - circle_
epoch_ close_ response_ semantic_ prefix - circle_
metadata_ head_ prefix - circle_
roster_ head_ prefix - circle_
semantic_ prefix - merge_
frontier_ head - Insert
headinto a frontier keyed by author stream, keeping the deeper (higher-sequence) head when the stream already carries one. Merging every conflicting branch’s heads this way yields the union frontier: each stream is covered at its deepest position across all branches, so a device that authored on that stream continues from its own head instead of re-allocating it. - merkle_
root_ and_ proofs - recipient_
slot - recipient_
slot_ with_ peer - verify_
circle_ semantic_ prefix - verify_
merkle_ proof