Workbench is where people do the work. Spine Fabric holds governed business context. Spine Runtime handles authorized execution. Spine Platform is where the environment behind that work is configured, observed, and controlled.
Establish operating boundaries, organization context, environments, roles, and membership-related configuration.
Connection management
Inspect discovered providers and connection projections; review connectivity, health, ownership, and activation state.
MCP Network
Manage the relevant MCP server and tool estate, client access, routes, and supported network capabilities.
Capability catalog
Understand which business intents, resource types, and operations are available, enabled, restricted, or awaiting configuration.
Governance
Configure policy boundaries and inspect decisions, requested approvals, and execution constraints.
Environment operations
Review service readiness, runtime profiles, operational signals, and available telemetry. A missing signal stays unknown.
02
Platform controls and Platform Console are different
Spine Platform is the control surface for configuration and operational actions. Spine Platform Console is the privileged estate view for authorized founders and platform operators—organizations, users, service health, alerts, approvals, and change records. The console consumes actual authority APIs where available; it must not manufacture counts or claim infrastructure health without telemetry.
03
Built for shared control, not permission shortcuts
Administrative access is a responsibility, not a way around tenant isolation or source-system permissions. A projected connector does not make Spine the owner of the host's credential or authority.