Skip to content

Spine Workspace

Build capabilities around business intent, not vendor lock-in.

Spine Workspace is designed to separate a business operation from the provider endpoint that happens to implement it.

Describe the intent

An operation such as crm.account.update expresses a business capability. A provider adapter maps that capability to a supported resource and operation through explicit configuration, resource types, and traits.

Respect what the connection can do

Discovery identifies supported schemas, objects, events, and operations. Capability availability comes from actual bindings and permissions, not a hard-coded assumption that all CRMs behave alike.

Make host integration governed

Spine Network MCP exposes selected context and capabilities to compatible hosts. Identity, tenant, scope, and authorization must be established before sensitive operations are available.

Preserve the action trail

Request a capability, receive an authorization decision, execute through the approved path, observe the provider, and reconcile the result. Treat a provider response separately from a verified business-state change.

02

Developer resources

Getting started

Supported host and connection prerequisites.

Authentication

One Auth and workspace binding concepts.

Capabilities

Intent, schemas, resource types, traits, and provider mappings.

MCP

Available tools, invocation patterns, and host compatibility.

Governance

Approval, denial, replay protection, and reconciliation states.

Examples

Account context retrieval and an approved update with readback.

API examples, endpoint URLs, packages, and SDK installation commands are published only after the released contract is verified.

Continue with context

Move from understanding to the right next step.