Expand description
Circle identities, audience routing, and control coordinates.
Re-exports§
pub use super::circle_control::*;pub use super::circle_roster::*;
Structs§
- Access
Leaf Id - Circle
- One Circle as
Circles::listreports it: its id, display name, the local identity’s role when it holds active access, and the derived state. The name is absent for a Circle with no resolved metadata (inactive, conflicted, or deleted); the role is present only when the local identity holds active roster membership. - Circle
Close Participant - One participant in an in-flight epoch close and its slot settlement.
- Circle
Close Status - The read-only status of a Circle’s in-flight epoch close: which participant slots hold responses, exclusions, or nothing.
- Circle
Epoch Close Id - The stable identity of one Circle epoch close, derived from the durable
operation that opened it. It names the close a
Circles::close_statusinspects and the reserved response and outcome slots that settle it; a close’s identity is fixed for its lifetime and survives cancellation and retry. - Circle
Epoch Id - Circle
Id - A self-certifying 128-bit circle identity encoded as canonical lowercase base32.
- Circle
IdError - Circle
Member Info - Circle
Operation Id - Circle
Operation Info - RowRouting
Id - HMAC identity of one scoped row. It is stable across audience moves and Store-key rotations because it derives from the unique generation-1 key.
- RowRouting
IdError - RowRouting
Key
Enums§
- Audience
- The one audience a synced row belongs to.
- Circle
Close Settlement - The settlement of one participant device’s create-once epoch-close response slot: it published its own applied frontier, an Owner excluded it, or the slot is still empty.
- Circle
Info - One Circle as the local application sees it. A Circle with a single resolved
control is
Active; a Circle whose control history forked into concurrent valid successors isConflictedand carries no name, role, or key until an Owner resolves it. A conflicted Circle refuses authoring and package publication, so it has no single resolved roster or metadata to report. - Circle
Operation Block - Why a durable Circle operation cannot currently publish. One variant per production block site; each future block site adds its own.
- Circle
Operation Kind - Circle
Operation State - Circle
Publication Blocked - Why publishing new content into a Circle is refused. Carried as the durable typed reason on a blocked host write and on a refused Circle lifecycle operation.
- Circle
Role - Circle
State - The public derived state of one Circle. Mapped once from the internal current
state;
Circles::listreports it per Circle. - RowRouting
KeyError