{"slug":"architecture/PLATFORM_MANAGEMENT_CONSOLE","title":"Platform Management Console","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/PLATFORM_MANAGEMENT_CONSOLE.mdx","bytes":4188,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Normative  \n**Date:** 2026-08-11  \n**Parent:** [`INTEGRATEWISE_ARCHITECTURE_v2.2.md`](INTEGRATEWISE_ARCHITECTURE_v2.2.md)\n\nThe Platform Management Console is the operator/admin surface for configuring, governing and observing the Platform Backend. It is not the User Workbench.\n\n## Canonical navigation\n\n1. Integration Manager\n2. Connector Marketplace\n3. Activation Hub\n4. Capability Manager\n5. MCP Pool\n6. AI Models\n7. Knowledge\n8. Memory & Continuity\n9. Automation\n10. Pipelines\n11. Governance\n12. Observability\n13. Administration\n\n- Organizations\n- Users\n- Roles\n- Permissions\n- Audit\n- Billing\n- Deployments\n- API Keys\n- Security\n\n## Module ownership\n\n| Module                | Responsibility                                                                         |\n| --------------------- | -------------------------------------------------------------------------------------- |\n| Integration Manager   | connector projections, connection health, sync, webhooks, schemas and lifecycle        |\n| Connector Marketplace | discover, activate, reuse, revoke and replace supported connector types                |\n| Activation Hub        | tenant/product/package activation and readiness state                                  |\n| Capability Manager    | Tool Capability registry, schemas, versions, policies, grants and availability         |\n| MCP Pool              | MCP server/tool registry, routing, version/health and exposure policy                  |\n| AI Models             | model/provider registry, routing policy, usage and model availability                  |\n| Knowledge             | governed knowledge assets and retrieval configuration                                  |\n| Memory & Continuity   | memory lifecycle, context continuity and retention controls                            |\n| Automation            | durable automated/recurring workflow definitions using governed capabilities           |\n| Pipelines             | ingestion, normalization, enrichment, reconciliation and operational pipeline state    |\n| Governance            | policy, proposals, approvals, execution authority and enforcement                      |\n| Observability         | traces, metrics, logs, health, capability execution and connector telemetry            |\n| Administration        | tenant/user/access, audit, commercial, deployment, API-key and security administration |\n\n## Hard routing constraint\n\nConfiguration Manager behavior may be embedded into the modules above, but all configuration must be connector-aware and capability-aware.\n\nThe following flows may not assume a provider independently:\n\n```text\nConfiguration\nActivation\nIntegration\nDiscovery\nSchema\nCapability execution\n```\n\nEach must resolve through the current tenant's connector projection registry, effective grants, schemas, health and capability registry.\n\n## Separation from User Workbench\n\nThe Platform Console configures the system. The User Workbench performs business work.\n\nPlatform-only concepts such as connector installation internals, MCP registration, model provider configuration, deployment bindings and organization security policy should not leak into ordinary Workbench navigation unless surfaced as a role-appropriate projection.\n\n## Capability Manager as central contract\n\nCapability Manager is the authoritative operator view for Tool Capability definitions and policy attachment. Workbenches consume its effective projections; they do not own independent capability definitions.\n\n## Activation rule\n\nActivation is not complete when a connector merely authenticates. A usable activation proves:\n\n```text\nidentity bound\n+ connector projection healthy\n+ schema discovered/validated\n+ effective capabilities resolved\n+ required package activated\n+ initial Spine hydration complete or explicitly deferred\n+ Governance policy attached\n+ Workbench projection available\n```\n\n## Observability rule\n\nOperators must be able to trace a user-visible execution from Workbench intent through capability resolution, Governance decision, proposal/approval where applicable, executor/Hermes, provider/internal result, reconciliation and resulting Spine outcome.\n"}