Clear answers
Questions worth answering clearly.
Start with the product, then go deeper into connections, authority, operations, and access.
Product and context
What is Spine Workspace?
Spine Workspace is the business-context workspace where humans and AI work together. It relates authorized information and capabilities from existing tools, presents role-relevant context, and supports governed action and continuity.
Is Spine Workspace another CRM, project manager, or integration platform?
No. It works alongside authoritative source systems, helping users understand relationships and work across them. It does not require replacing their business applications.
What is Spine Fabric?
Spine Fabric is the governed layer for business context, source relationships, signals, provenance, decisions, and continuity used by Spine surfaces and authorized host integrations.
What is the difference between Spine Workbench and Spine Twin?
Workbench is the human workspace for viewing, deciding, collaborating, and acting. Twin is the AI counterpart that helps assemble and reason over permitted context and prepare governed work.
What is Spine Network MCP?
It is the governed MCP interface that lets compatible AI hosts access selected Spine context and capabilities after authentication and authorization.
Connections and continuity
Does Spine automatically see every app connected to my AI host?
No. Visibility depends on what the host exposes, the connection method, granted permissions, and supported discovery capabilities.
Does Spine store or own my host's connections?
Spine favors host-native connectors where supported and manages governed use and continuity. Some integrations may require a separately authorized workspace connection. The connection model should be explicit for each provider.
Can it work across multiple AI hosts?
The architecture supports continuity across authorized surfaces, including compatible hosts. Actual interoperability depends on each host's integration support and the scope of what it allows Spine to access.
Will all my data be copied into Spine Fabric?
No blanket copying is implied. Data acquisition and retention depend on the authorized source, use case, policy, and configured ingestion or retrieval path. Source systems remain authoritative.
What happens when two sources disagree?
The system should expose source provenance and conflicts instead of silently presenting a fabricated single truth. Resolution follows the applicable authorization and promotion process.
Can Spine Twin use an AI model I already have?
Available model and host paths depend on current integration support and workspace policy. Do not assume all models or providers are universally available.
Does Spine Workspace work without a host connection?
Some workspace functionality may be available without a connected AI host, but connected business context and host-specific capabilities require their relevant authorization and data paths. The interface should show what is and is not active.
Authority and access
Can AI make changes without my approval?
Permissions and policies determine the execution path. Actions designated as requiring human approval must pass that review. Some authorized low-risk operations may follow different policies; discovery alone never grants unlimited execution rights.
How do I know an action actually happened?
An action can have an execution record, provider observation, and supported readback or reconciliation. The interface should distinguish verified completion from accepted, pending, failed, or unresolved work.
Can a team member see every department?
No. Role, membership, workspace, and organizational policy determine visibility. Broad domain access is a deliberately authorized responsibility.
Is Spine Workspace ready for my enterprise identity provider?
Identity and federation support varies by deployment and current One Auth configuration. Contact the team to confirm requirements such as SSO, lifecycle management, and administrative controls.
Where is my data hosted and how long is it retained?
Hosting and retention should be answered from the actual deployment configuration and published legal/security documentation, not a generic promise. Contact the team for deployment-specific detail.
Platform and getting started
What is Spine Platform?
Spine Platform is the administrative control plane for tenants, workspaces, connections, MCP networks, capabilities, policy, approvals, and environment operations. Workbench is where most people do their daily work; Platform is for authorized configuration and oversight.
What is the Platform Console?
The Platform Console is the estate-operating view for authorized founders and platform operators. It organizes organization/user administration, service health, alerts, approvals, and change context. Actual data availability depends on the connected control services.
What is One Access Console?
It is the operator-facing view for host discovery, identity grants, capability matrices, access states, and publication controls. It complements One Auth rather than replacing the identity provider.
What happens during Activation?
You confirm identity, organization, role, initial goals, and workspace context, then discover available hosts and sources and review connection readiness. Some optional setup can happen after the first Workbench entry.
How do I begin?
Create a workspace through the product website, or connect Spine Network MCP through a compatible AI host and complete One Auth.
Historical recall does not grant authority. Scoped access and explicit approval still apply.
Capability availability varies by tenant, host, and profile. Marketing describes design intent unless a page states verified evidence.