Platform Management Console
Status: Normative
Date: 2026-08-11
Parent: INTEGRATEWISE_ARCHITECTURE_v2.2.md
The Platform Management Console is the operator/admin surface for configuring, governing and observing the Platform Backend. It is not the User Workbench.
Canonical navigation
- Integration Manager
- Connector Marketplace
- Activation Hub
- Capability Manager
- MCP Pool
- AI Models
- Knowledge
- Memory & Continuity
- Automation
- Pipelines
- Governance
- Observability
- Administration
- Organizations
- Users
- Roles
- Permissions
- Audit
- Billing
- Deployments
- API Keys
- Security
Module ownership
| Module | Responsibility |
|---|---|
| Integration Manager | connector projections, connection health, sync, webhooks, schemas and lifecycle |
| Connector Marketplace | discover, activate, reuse, revoke and replace supported connector types |
| Activation Hub | tenant/product/package activation and readiness state |
| Capability Manager | Tool Capability registry, schemas, versions, policies, grants and availability |
| MCP Pool | MCP server/tool registry, routing, version/health and exposure policy |
| AI Models | model/provider registry, routing policy, usage and model availability |
| Knowledge | governed knowledge assets and retrieval configuration |
| Memory & Continuity | memory lifecycle, context continuity and retention controls |
| Automation | durable automated/recurring workflow definitions using governed capabilities |
| Pipelines | ingestion, normalization, enrichment, reconciliation and operational pipeline state |
| Governance | policy, proposals, approvals, execution authority and enforcement |
| Observability | traces, metrics, logs, health, capability execution and connector telemetry |
| Administration | tenant/user/access, audit, commercial, deployment, API-key and security administration |
Hard routing constraint
Configuration Manager behavior may be embedded into the modules above, but all configuration must be connector-aware and capability-aware.
The following flows may not assume a provider independently:
Configuration
Activation
Integration
Discovery
Schema
Capability execution
Each must resolve through the current tenant's connector projection registry, effective grants, schemas, health and capability registry.
Separation from User Workbench
The Platform Console configures the system. The User Workbench performs business work.
Platform-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.
Capability Manager as central contract
Capability 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.
Activation rule
Activation is not complete when a connector merely authenticates. A usable activation proves:
identity bound
+ connector projection healthy
+ schema discovered/validated
+ effective capabilities resolved
+ required package activated
+ initial Spine hydration complete or explicitly deferred
+ Governance policy attached
+ Workbench projection available
Observability rule
Operators 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.