Current
11 — Platform Modules UI
Status: Active frontend handoff
The Platform section contains six shared modules. They are real governed
projections over Platform services, not architectural layers and not Twin
destinations.
| Module | Primary frontend responsibility |
|---|---|
| Integration Manager | Connector installations, sync, webhooks and schema mappings |
| Configuration Manager | Tenant projection profile, depth matrix, policies and availability |
| Activation Hub | Onboarding readiness, hydration progress and activation blockers |
| Network Graphs | Tenant-authorized Spine entity/binding relationship graph |
| Governance | Approvals, policies, proposal versions and audit evidence |
| Continuity | Context, governed memory, provenance and retention state |
Each module receives its navigation permission and actions from discovery. The
frontend must not expose a module because a route happens to exist.
Common response requirements are tenant_id, projection_id, as_of,
freshness, permissions, capabilities, provenance, partial_failures and
trace_id.
The Platform UI cannot directly call Connector Workers, internal MCP Pool,
Hermes, Neon, D1/KV, R2 or provider APIs. All communication crosses the
authenticated Gateway.