Unclassified

13 · Ecosystem & Integration View

Ecosystems, connectors, APIs, webhooks, MCP, MCP Pool, external systems, synchronization, ingestion, and actions — how One Auth scopes reach the outside world.

Ecosystems Are Where Business Reality Lives

The 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.

IW One Auth (scoped per ecosystem)
      │
      ├── Connectors (typed, versioned, tenant-scoped)
      ├── APIs / Webhooks / Events (provider contracts)
      ├── MCP + MCP Pool (model-context side, governed routing)
      └── External Systems (the actual SaaS / on-prem system)
            │
            ├── Synchronization (read) → Loader → Normalizer → Spine
            └── Actions (write) ← Hermes ← Governance ← Capability Fabric

Integration Surfaces

Surface	What it does	Governed by
Connectors	Typed, versioned bridge to a provider (Salesforce, M365, Slack, etc.) — handles auth, discovery, normalization hints	Tenant + One Auth scopes + activation
APIs / Webhooks	Provider contracts for read and event-driven ingest	Connector + pipeline contracts
MCP	Tool / context surface for AI — routes through MCP Pool with tenant and Work scoping	MCP Pool routing boundary — not an open public MCP
Sync / Ingestion	Continuous and event-driven loading of external state into the Spine	Four-flows pipeline

One Auth to Ecosystems

Connecting an ecosystem is a One Auth scope grant — not a separate OAuth bolt-on.

Scopes are tenant- and user- and Work-context aware.
Discovery enumerates capabilities per connected ecosystem; activation decides what becomes available to this runtime.
Reads hydrate the Spine via governed ingestion; writes never bypass governance and Hermes.

MCP Pool

MCP 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.

MCP exposes capabilities to AI under the Capability Fabric.
The Pool routes to executors, but Hermes remains the only path that actually executes authorized external mutations with evidence capture.

Where to Go Next

What exists vs what should become active for this tenant/runtime/context.


How discovered capabilities become provider-neutral actions.


How read-side sync becomes Business Context.

</CardGroup>