Activation Hub

The Activation Hub converts an authenticated organization into an operational workspace by walking seven readiness gates in order.

Each gate must pass before the next stage can begin. An Activation Blocker (incomplete auth, missing connector, insufficient scopes, unresolved mapping, no admin, missing policy, failed pipeline) halts go-live until cleared. The Twin explains what's happening, why a step is blocked, and what value unlocks after completion.

The Seven Readiness Gates

Gate 1 — Identity ready

Verified principal, tenant, workspace.

• Confirms: A authenticated user is bound to a specific tenant and workspace.
• Blockers: Missing or unverified identity, no tenant assignment, workspace not provisioned.
• Unlocks: Progression to Stage 2 — Discover. Without identity resolution, no further steps are possible.
• Twin context: The Twin can identify the user and their tenant scope.

Gate 2 — Workspace ready

Configured workspace with a resolved capability set.

• Confirms: The workspace has been set up with the necessary configuration and the user has a resolved set of capabilities available.
• Blockers: Workspace not provisioned, capability set not resolved for this user/tenant combination, missing configuration.
• Unlocks: Progression to Stage 3 — Connect. With a workspace and capability set, the user can see what's available.
• Underneath: Capability Resolver intersects everything discovered against tenant policy, role, and context.

Gate 3 — Connections ready

Scoped, healthy connector projections for the systems this workspace needs.

• Confirms: Each host-owned connection has become a narrow connector projection — never a copy of the provider credential. Connections are healthy, scoped, and operational.
• Blockers: Connections not established, projections not healthy, scopes insufficient, consent not obtained.
• Unlocks: Progression to Stages 4-5 — Load & Normalize. With healthy connections, records can be pulled and hydrated.
• Underneath: one connection fans out into read / sync / Twin-search / approved-write projections without duplicating the credential.

Gate 4 — Spine ready

Canonical entities resolved, relationships preserved, provenance attached.

• Confirms: The Loader has pulled permitted records and the Normalizer has turned provider-specific shapes into canonical Spine entities and relationships. Relationships are preserved and provenance is attached.
• Blockers: Historical ingestion not complete (but activation does not require complete historical ingestion — priority is time to first useful Workbench), relationships not preserved, provenance missing.
• Unlocks: Progression to Views ready (Gate 5) and Twin ready (Gate 6). The connected truth is now available for role-routed views and Twin context.
• Important: Priority: time to first useful Workbench — do not force complete historical ingestion before activation.

Gate 5 — Views ready

Role-routed department views render.

• Confirms: Department-specific views (Tables, Boards, Calendars) render correctly with the user's data, KPIs, and capabilities.
• Blockers: Views not configured for this role/department, data not mapped to role-routed lenses, KPI strips not populated.
• Unlocks: Progression to Twin ready (Gate 6). The user can now open their role-routed Workbench.
• Underneath: The five-zone shell is populated with role-appropriate data, KPIs, and capabilities.

Gate 6 — Twin ready

Twin can retrieve context and propose.

• Confirms: The Twin can retrieve context for a selected item and explain/organize/generate/propose for that specific item.
• Blockers: Twin not configured, context retrieval failing, no proposal capability, policy restrictions on Twin operations.
• Unlocks: Progression to Governance ready (Gate 7). The user can now invoke the Twin on specific items and begin the OODA loop.
• Underneath: The Twin is invoked on a selected object (account, task, risk, signal, doc, KPI) — that selection creates a context path — and the Twin fetches context, then explains, organizes, generates, or proposes for that specific item. It closes on navigate-away.

Gate 7 — Governance ready

Approval flow configured and tested.

• Confirms: The governance approval flow is configured and tested. Policy evaluates permissions, risk class (R0–R4), approval need, and expected effects.
• Blockers: Approval flow not configured, policies not tested, risk classes not defined, HITL approval not operational.
• Unlocks: Progression to Stage 7 — Work. The user can now open their role-routed Workbench and begin the Propose→Govern→Execute→Reconcile→Learn loop.
• Underneath: policy evaluates permissions, risk class (R0–R4), approval need, and expected effects. Nothing consequential runs without a human decision.

Activation Flow Summary

The through-line

Identity ready → Workspace ready → Connections ready → Spine ready → Views ready → Twin ready → Governance ready → Work

Connect once. The Spine assembles the truth. Work begins with context already attached — and every action the user takes teaches the workspace how to help next time.

Cross-Reference to User Journey Stages

Quick Start from Activation

Built 2026-08-20 · Nextra 4 · Theme nextra-theme-docs