Groups
Model proof-carrying membership and offline conflict resolution without imposing Mission Group semantics.
Use a Platform Group for membership that merges across offline peers. Membership changes carry proof of authority. Your application defines what membership permits.
Identify members and authority
A Group contains a GroupId, membership state, and an optional DID identity for use as an authorization trust anchor. Members are principal DIDs or nested groups. The primitive does not distinguish people, devices, or sensors.
Generated GroupId values use UUIDv7. The identifier representation also supports strings such as DIDs. An identifier alone establishes neither membership nor permission.
Direct membership checks differ from recursive principal resolution. Your application supplies nested-group lookup. Resolution bounds nesting and rejects cycles or excessive depth.
Merge authorized membership changes
The membership state is a conflict-free replicated data type, or CRDT. Each member has an increasing counter. Odd counters mean active membership, and even counters mean removal. State merge retains the higher counter.
Proof-carrying operations describe Create, Add, or Remove, with an author and causal dependencies. StrongRemoveResolver verifies proofs, filters concurrent operations by removed members, and invalidates operations that depend solely on rejected operations. Mutual concurrent removals both apply.
Production membership management needs an application-approved ProofVerifier. GroupApi::new() uses TrustAllVerifier for trusted environments and tests. It is not a production authorization policy. Construction and in-memory registration do not provide durable storage, replication, or revocation propagation.
Keep Mission scopes separate
A Mission Group organizes a module's teams and can bind an immutable access policy. Organizations, Mission Groups, and teams have distinct roles and authority rules. Shared GroupId representation does not make organization and Mission Group scopes interchangeable.
An independent Platform application needs no Mission admission. It owns trust roots, membership policy, persistence, and the mapping from group membership to authorized actions. Follow identity and authorization for receive checks.
Use the Group reference for exact operations and resolver behavior. See Mission membership only for Mission semantics. Continue with document access scopes, storage and replication, and the Platform language references.