Org Bring-up
A gate, not a nudge. Until the blocking steps are met, an admin sees this checklist instead of the dashboard — and early builders sit in a read-only holding state. Once complete, this becomes revisitable Org Settings.
The blocking steps are satisfied, so the control plane is live: agents can be built, teams can be staffed, and Organization Memory is unlocked. Revisit any step below to re-confirm or tighten — but the gate itself never re-arms once the floor is met.
3 models enabled. At least one model must be allowed before any agent can be built.
3 teams created (Platform Engineering, Contracts & Proposals, Mission Software).
FedRAMP-High confirmed. Narrow-only — frameworks can be removed here, never expanded (honesty guard).
Frameworks can be confirmed or removed here, never expanded — an honesty guard so the platform never claims coverage it cannot demonstrate.
Convention `rai-<team>-<role>` confirmed; 2 aliases registered.
Confirmed v2. Organization Memory stays disabled until this is set.
Organization Memory stays disabled until the Classification Policy is confirmed — no org-scoped recall before the labels and flows are set.
Users who federate in before bring-up completes are not turned away and not silently granted access. They land in a read-only holding state until an admin resolves their IdP group claim — no auto-created teams, no implicit roles.
Review pending arrivals in Federation & Access