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.
Spine Workspace
Spine Workspace is designed to separate a business operation from the provider endpoint that happens to implement it.
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.
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.
Spine Network MCP exposes selected context and capabilities to compatible hosts. Identity, tenant, scope, and authorization must be established before sensitive operations are available.
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.
Supported host and connection prerequisites.
One Auth and workspace binding concepts.
Intent, schemas, resource types, traits, and provider mappings.
Available tools, invocation patterns, and host compatibility.
Approval, denial, replay protection, and reconciliation states.
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