Membership Setup

What It Models

Setup is the common handling of membership configuration and structure records. It explains identity, version checks, authority, transactional saves, initial data, imports, exports and workspace removal without creating another stored business entity.

Identity and Attributes

Permanent configuration identities support stable references and imports. Versions and actor stamps describe changes, while lifecycle and bulk declarations describe how whole workspaces are handled. Structure operations have specific exceptions to mandatory version checks.

Relationships

Setup spans hierarchy, units, programs and packages. Platform coordinates lifecycle and data jobs, and Membership supplies participant and operation declarations. Configuration export and lifecycle execution are wired through the memberships participant.

Invariants

The structured rows specify common guarantees and their exceptions. An unchanged configuration save advances the version without creating a content revision. Soft external references remain outside the protection provided by local foreign keys.

How It Is Stored and Shared

Configuration provides the reusable store, route builder and error translation. Structure uses its own replacement and tree operations. Seeds are recorded in the shared ledger, and bulk execution depends on Platform wiring beyond the locally verified operation declarations.

Open Design Questions

Product must settle replacement and paging consistency, the unused lock flag and whether purge should clear applied seeds. Console permission mapping and missing administration screens remain prerequisites for browser-based setup.