{"slug":"developers/11_PLATFORM_MODULES_UI","title":"11 — Platform Modules UI","section":"developers","sectionLabel":"Developers","status":"current","type":"document","path":"developers/11_PLATFORM_MODULES_UI.mdx","bytes":1474,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Active frontend handoff\n\nThe Platform section contains six shared modules. They are real governed\nprojections over Platform services, not architectural layers and not Twin\ndestinations.\n\n| Module                | Primary frontend responsibility                                    |\n| --------------------- | ------------------------------------------------------------------ |\n| Integration Manager   | Connector installations, sync, webhooks and schema mappings        |\n| Configuration Manager | Tenant projection profile, depth matrix, policies and availability |\n| Activation Hub        | Onboarding readiness, hydration progress and activation blockers   |\n| Network Graphs        | Tenant-authorized Spine entity/binding relationship graph          |\n| Governance            | Approvals, policies, proposal versions and audit evidence          |\n| Continuity            | Context, governed memory, provenance and retention state           |\n\nEach module receives its navigation permission and actions from discovery. The\nfrontend must not expose a module because a route happens to exist.\n\nCommon response requirements are `tenant_id`, `projection_id`, `as_of`,\n`freshness`, `permissions`, `capabilities`, `provenance`, `partial_failures` and\n`trace_id`.\n\nThe Platform UI cannot directly call Connector Workers, internal MCP Pool,\nHermes, Neon, D1/KV, R2 or provider APIs. All communication crosses the\nauthenticated Gateway.\n"}