{"slug":"platform/ecosystem-integration-view","title":"13 · Ecosystem & Integration View","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/ecosystem-integration-view.mdx","bytes":3028,"description":"Ecosystems, connectors, APIs, webhooks, MCP, MCP Pool, external systems, synchronization, ingestion, and actions — how One Auth scopes reach the outside world.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## Ecosystems Are Where Business Reality Lives\n\nThe Business Context Spine does not replace Salesforce, M365, Jira, or NetSuite. Those **ecosystems** are where business information and actions reside. The platform connects to them in a governed way.\n\n```text\nIW One Auth (scoped per ecosystem)\n      │\n      ├── Connectors (typed, versioned, tenant-scoped)\n      ├── APIs / Webhooks / Events (provider contracts)\n      ├── MCP + MCP Pool (model-context side, governed routing)\n      └── External Systems (the actual SaaS / on-prem system)\n            │\n            ├── Synchronization (read) → Loader → Normalizer → Spine\n            └── Actions (write) ← Hermes ← Governance ← Capability Fabric\n```\n\n## Integration Surfaces\n\n| Surface | What it does | Governed by |\n|---|---|---|\n| **Connectors** | Typed, versioned bridge to a provider (Salesforce, M365, Slack, etc.) — handles auth, discovery, normalization hints | Tenant + One Auth scopes + activation |\n| **APIs / Webhooks** | Provider contracts for read and event-driven ingest | Connector + pipeline contracts |\n| **MCP** | Tool / context surface for AI — routes through MCP Pool with tenant and Work scoping | MCP Pool routing boundary — not an open public MCP |\n| **Sync / Ingestion** | Continuous and event-driven loading of external state into the Spine | Four-flows pipeline |\n\n## One Auth to Ecosystems\n\nConnecting an ecosystem **is** a One Auth scope grant — not a separate OAuth bolt-on.\n\n* Scopes are tenant- and user- and Work-context aware.\n* Discovery enumerates capabilities per connected ecosystem; activation decides what becomes available to this runtime.\n* Reads hydrate the Spine via governed ingestion; **writes never bypass governance and Hermes**.\n\n## MCP Pool\n\n\nMCP in SpineWorkspace is **not** an unrestricted public MCP. It is a governed MCP Pool with tenant, Work, and capability scoping and explicit routing to Hermes.\n\n\n* MCP exposes capabilities to AI under the Capability Fabric.\n* The Pool routes to executors, but Hermes remains the only path that actually executes authorized external mutations with evidence capture.\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    What exists vs what should become active for this tenant/runtime/context.\n  \n  \n    How discovered capabilities become provider-neutral actions.\n  \n  \n    How read-side sync becomes Business Context.\n  \n</CardGroup>\n"}