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.Integration Surfaces
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
Discovery & Activation
What exists vs what should become active for this tenant/runtime/context.
Capability Fabric
How discovered capabilities become provider-neutral actions.
Ingestion & Normalization
How read-side sync becomes Business Context.