# Spine Innov Labs

- [SpineWorkspace](https://docs.spineworkspace.com/index.md): Spine Innov Labs builds SpineWorkspace, the product that connects human work and AI work through one contextual continuity layer.
- [The Problem: Fragmented Work Across Tools and Systems](https://docs.spineworkspace.com/product/the-problem.md): Modern businesses run on dozens of systems, but context fragments across them. Every handoff forces humans to reconstruct the full picture manually.
- [fragmented-ai](https://docs.spineworkspace.com/product/fragmented-ai.md): Why bolting AI onto scattered tools doubles the fragmentation problem instead of solving it.
- [Why Integration Alone Will Not Fix Fragmented Work](https://docs.spineworkspace.com/product/why-integration-is-not-enough.md): Integration moves bytes between systems. It does not move context, continuity, memory, or governance. Spine Fabric is the layer above integration.
- [Business Continuity vs AI Memory: The Pivotal Distinction](https://docs.spineworkspace.com/product/business-continuity-vs-ai-memory.md): AI continuity is not business continuity. The Spine Fabric exists for durable, governed business memory.
- [Shared Context Principle: One Truth for Humans and AI](https://docs.spineworkspace.com/product/shared-context-principle.md): Humans and AI operate on the same governed business context in SpineWorkspace. Same source, same decisions, no translation loss.
- [Human + AI Operating Model: Authority, Collaboration, Continuity](https://docs.spineworkspace.com/product/human-ai-operating-model.md): In SpineWorkspace, AI does the heavy lifting and humans stay on top with intent, judgment, and approval. Same goal, one journey.
- [Why Now: The Contextual Continuity Layer Is Urgent](https://docs.spineworkspace.com/product/why-now.md): APIs, operational agents, models needing context, and durable source systems have converged. The contextual continuity layer is now buildable and urgent.
- [Our Approach: A Business Continuity Workspace for Humans and AI](https://docs.spineworkspace.com/product/our-approach.md): A business continuity workspace where the Spine Fabric and SpineWorkspace connect humans and AI through governed shared context.
- [SpineWorkspace: Human and AI Work on One Governed Context](https://docs.spineworkspace.com/product/spine-workspace.md): SpineWorkspace is a business continuity workspace where humans and AI share governed business context through two workbenches, one continuity layer.
- [Canonical vs Operational: The Architecture of Safe Autonomy](https://docs.spineworkspace.com/product/canonical-vs-operational.md): Canonical state is the authoritative business record. Operational state is where AI proposes and experiments.
- [Twin: Your Personal AI Operator in SpineWorkspace](https://docs.spineworkspace.com/product/twin.md): Twin is your personal AI operator inside SpineWorkspace. It works on the same shared, governed context you do, and acts only with your authority.
- [Self-Organizing Workbench: A Surface That Adapts to You](https://docs.spineworkspace.com/product/self-organizing-workbench.md): SpineWorkspace organizes itself around the work you do, the domain you operate in, and the context Spine Fabric assembles for the moment.
- [Business Context: One Live Picture of Your Business](https://docs.spineworkspace.com/product/business-context.md): Business Context is the unified, live picture of your business that Spine Fabric assembles from every connected tool, so every person and agent works from the.
- [Business Continuity: Durable, Governed Memory of the Business](https://docs.spineworkspace.com/product/business-continuity.md): Business continuity is the durable, governed memory of the business. It survives sessions, people, agents, and time.
- [Connected Work: One Journey Across Tools, People, and AI](https://docs.spineworkspace.com/product/connected-work.md): Connected work means one continuous journey across every tool, every person, and every AI operator, backed by Spine Fabric and governed by SpineWorkspace.
- [Spine Fabric: The Shared Context Layer for Modern Operations](https://docs.spineworkspace.com/platform/spine-fabric.md): Spine Fabric is Spine Innov Labs's shared contextual operating layer.
- [One Auth: Unified Identity Across Every Connected System](https://docs.spineworkspace.com/platform/one-auth.md): One Auth is Spine Innov Labs's identity layer that lets a single sign-in reach every connected tool, capability, and agent under one governed identity.
- [Connectors: Bringing Source Systems into the Spine Fabric](https://docs.spineworkspace.com/platform/connectors.md): Connectors bring source-system data, events, and write-back into Spine Fabric, feeding unified business context to every workbench, view, and agent.
- [Capabilities: Governed Actions Twin and Agents Can Execute](https://docs.spineworkspace.com/platform/capabilities.md): Capabilities are the discrete governed actions Twin, agents, and humans can execute against source systems, each with scope, authorization, and receipts.
- [Integrations: The Fabric That Reaches Every Tool You Use](https://docs.spineworkspace.com/platform/integrations.md): Integrations combine connectors, MCP tools, and marketplace extensions to bring every business tool into SpineWorkspace as governed, contextualized work.
- [MCP Connectivity: Standards-Based Tool Access for Agents](https://docs.spineworkspace.com/platform/mcp-connectivity.md): MCP Connectivity lets Twin and agents call any Model Context Protocol server as a governed capability, exposing custom tools without bespoke integration.
- [Account Success on SpineWorkspace](https://docs.spineworkspace.com/solutions/account-success.md): The Account Success solution unifies CRM, support, usage, and billing into one workbench so CSMs can drive renewals, expansion, and account health.
- [Sales on SpineWorkspace: Pipeline in Live Context](https://docs.spineworkspace.com/solutions/sales.md): The Sales solution turns SpineWorkspace into a pipeline surface where sellers work deals with live account context, drafts, and governed CRM write-back.
- [Customer Support on SpineWorkspace](https://docs.spineworkspace.com/solutions/customer-support.md): The Customer Support solution unifies tickets, accounts, communications, and product signals into one workbench for faster, contextual resolution.
- [Marketing on SpineWorkspace](https://docs.spineworkspace.com/solutions/marketing.md): The Marketing solution unifies campaigns, audiences, content, and attribution into one contextual workbench for planning, launching, and measuring work.
- [Finance and RevOps on SpineWorkspace](https://docs.spineworkspace.com/solutions/finance.md): The Finance solution unifies billing, contracts, revenue, and forecasts into one workbench so RevOps and Finance teams work from live commercial context.
- [Business Operations on SpineWorkspace](https://docs.spineworkspace.com/solutions/business-operations.md): The Business Operations solution gives BizOps teams one workbench to run cross-functional workflows, approvals, and process work with live context.
- [Product and Engineering on SpineWorkspace](https://docs.spineworkspace.com/solutions/product-and-engineering.md): The Product and Engineering solution ties customer signal, roadmap, and delivery into one contextual workbench for PMs and engineering leaders.
- [Founder and Executive Operations on SpineWorkspace](https://docs.spineworkspace.com/solutions/founder-executive.md): The Founder and Executive solution gives leaders a live business picture across every domain, with Twin acting as a strategic operator alongside them.
- [connect-your-tools](https://docs.spineworkspace.com/how-it-works/connect-your-tools.md): Connect your existing business tools once and SpineWorkspace starts building unified business context.
- [Build Business Context: From Connection to Shared Understanding](https://docs.spineworkspace.com/how-it-works/build-business-context.md): Learn how Spine Innov Labs builds Business Context after you connect your tools: identity resolution, unification, contextualization, and projection into a live.
- [one-workbench](https://docs.spineworkspace.com/how-it-works/one-workbench.md): One connected workbench replaces scattered apps; every role works from the same assembled context.
- [contextual-twin](https://docs.spineworkspace.com/how-it-works/contextual-twin.md): The Twin works beside you with the same assembled context, proposing and drafting but never acting without approval.
- [governed-actions](https://docs.spineworkspace.com/how-it-works/governed-actions.md): Every consequential action follows one governed path: propose, approve, execute, verify, record.
- [continuity](https://docs.spineworkspace.com/how-it-works/continuity.md): How SpineWorkspace preserves context across time, systems, and people so work continues where it left off.
- [Spine Agent Network: A Cognitive ESB for Agents and Teams](https://docs.spineworkspace.com/agents/spine-agent-network.md): The Spine Agent Network is Spine Innov Labs's cognitive ESB: a shared substrate where Twin, core agents, domain agents, and tools discover each other, share.
- [core-agents](https://docs.spineworkspace.com/agents/core-agents.md): The core agent set that powers SpineWorkspace: Twin, discovery, schema, connection, and governance agents.
- [domain-agents](https://docs.spineworkspace.com/agents/domain-agents.md): Domain agents project SpineWorkspace capabilities into each business domain's workbench.
- [Network Effect: Why the Spine Agent Network Compounds](https://docs.spineworkspace.com/agents/network-effect.md): The Spine Agent Network compounds in value through shared context, shared capabilities, and shared memory.
- [Twin in the Agent Network](https://docs.spineworkspace.com/agents/twin.md): Twin is your personal node in the Spine Agent Network, coordinating with core and domain agents on your behalf under governed identity and policy.
- [Agent Workflows: How the Network Executes Work](https://docs.spineworkspace.com/agents/workflows.md): Agent workflows are the composable sequences by which Twin, core agents, and domain agents execute multi-step work under governance and continuity.
- [CRM Integrations: Salesforce, HubSpot, and Pipedrive](https://docs.spineworkspace.com/integrations/crm.md): CRM integrations bring accounts, contacts, opportunities, and activity from Salesforce, HubSpot, and Pipedrive into SpineWorkspace's unified context.
- [Communication Integrations: Email and Chat](https://docs.spineworkspace.com/integrations/communication.md): Communication integrations pull email and chat threads from Gmail, Outlook, Slack, and Teams into the shared context every domain workbench sees.
- [Project Management Integrations](https://docs.spineworkspace.com/integrations/project-management.md): Project management integrations bring Linear, Jira, Asana, and GitHub work items into SpineWorkspace as governed, contextualized tasks and roadmap data.
- [Documents and Knowledge Integrations](https://docs.spineworkspace.com/integrations/documents-and-knowledge.md): Document and knowledge integrations bring Drive, Notion, and Confluence content into SpineWorkspace as evidence attached to entities and workflows.
- [Finance and Billing Integrations](https://docs.spineworkspace.com/integrations/finance.md): Finance integrations pull contracts, invoices, and revenue from Stripe, QuickBooks, and Chargebee into SpineWorkspace's shared commercial context.
- [AI Platform Integrations](https://docs.spineworkspace.com/integrations/ai-platforms.md): AI platform integrations connect LLM providers and AI tools to SpineWorkspace, powering Twin, core agents, and domain agents behind governed capabilities.
- [Connector Marketplace](https://docs.spineworkspace.com/integrations/connector-marketplace.md): The Connector Marketplace is where teams discover, enable, and configure integrations for SpineWorkspace across CRM, communication, finance, and more.
- [Documentation Overview](https://docs.spineworkspace.com/resources/documentation.md): Where to find product docs, platform docs, solution guides, and internal architecture references for Spine Innov Labs and SpineWorkspace.
- [Guides for Setting Up and Operating SpineWorkspace](https://docs.spineworkspace.com/resources/guides.md): Guides walk through common Spine Innov Labs setups: connecting tools, building context, configuring domains, and running agents under governance.
- [Architecture Overview](https://docs.spineworkspace.com/resources/architecture.md): An entry point into Spine Innov Labs's architecture: Spine Fabric, projections, agent network, capabilities, workflows, integrations, and execution flow.
- [Spine Innov Labs Blog and Long-Form Writing](https://docs.spineworkspace.com/resources/blog.md): The Spine Innov Labs blog covers SpineWorkspace, connected work, the Spine Agent Network, and how teams operate with unified business context.
- [Changelog: What Ships in SpineWorkspace](https://docs.spineworkspace.com/resources/changelog.md): The Spine Innov Labs changelog tracks new capabilities, connectors, domain workbenches, and platform improvements as they ship in SpineWorkspace.
- [Customer Case Studies](https://docs.spineworkspace.com/resources/case-studies.md): Case studies show how teams use SpineWorkspace and Spine Innov Labs to unify context, run domains, and operate connected work at scale.
- [API Reference for SpineWorkspace](https://docs.spineworkspace.com/resources/api-reference.md): The SpineWorkspace API exposes context, capabilities, and workflows for programmatic integration, extension, and agent development.
- [Security in SpineWorkspace](https://docs.spineworkspace.com/security-and-governance/security.md): SpineWorkspace is built for enterprise security: identity through One Auth, scoped connections, capability-level authorization, and full audit trails.
- [Privacy in SpineWorkspace](https://docs.spineworkspace.com/security-and-governance/privacy.md): SpineWorkspace treats customer data with strict privacy controls: scoped access, minimum-necessary retrieval, and configurable retention and residency.
- [Permissions and Access in SpineWorkspace](https://docs.spineworkspace.com/security-and-governance/permissions.md): Permissions in SpineWorkspace combine roles, scopes, and capability-level authorization so people, Twin, and agents only reach what policy allows.
- [Governance for Human and AI Work in Spine](https://docs.spineworkspace.com/security-and-governance/governance.md): Governance in SpineWorkspace applies uniformly to human and AI actors, gating every capability call with policy and producing durable receipts.
- [Compliance Posture for SpineWorkspace](https://docs.spineworkspace.com/security-and-governance/compliance.md): SpineWorkspace is designed to meet enterprise compliance requirements with tenant isolation, audit trails, residency options, and configurable retention.
- [About Spine Innov Labs](https://docs.spineworkspace.com/company/about-integratewise.md): Spine Innov Labs builds SpineWorkspace, the contextual operating layer where humans, Twin, and agents work connected across every business tool.
- [Contact Spine Innov Labs](https://docs.spineworkspace.com/company/contact.md): Contact Spine Innov Labs for a SpineWorkspace demo, partnership, security questions, or press inquiries. Details on how to reach the right team.
- [Careers at Spine Innov Labs](https://docs.spineworkspace.com/company/careers.md): Spine Innov Labs is hiring across engineering, product, design, and go-to-market to build SpineWorkspace and the operating layer for connected work.
- [Spine Innov Labs Doctrine](https://docs.spineworkspace.com/internal-docs/doctrine/integratewise-doctrine.md): Spine Innov Labs doctrine sets the invariants and non-goals that everything the company builds must respect: connected work, context, governance, continuity.
- [SpineWorkspace Doctrine](https://docs.spineworkspace.com/internal-docs/doctrine/spine-workspace-doctrine.md): SpineWorkspace doctrine defines the interaction model, projection model, and boundaries of the product: one workbench, four flows, shared context.
- [Product Definition: SpineWorkspace](https://docs.spineworkspace.com/internal-docs/product/product-definition.md): SpineWorkspace is the one contextual workbench for every business domain, projecting shared Spine Fabric into domain-tailored views and workflows.
- [SpineWorkspace Product Topology: Five Layers](https://docs.spineworkspace.com/internal-docs/product/product-topology.md): The topology of SpineWorkspace as an Spine Innov Labs product: five layers from human and AI workbench surfaces down through the Spine Agent Network, Spine.
- [The User Path Through SpineWorkspace](https://docs.spineworkspace.com/internal-docs/two-paths/user-path.md): The User Path is how a person moves through SpineWorkspace: enter, discover, understand, contextualize, decide, act, review, and continue.
- [The System Path: From Event Intake to State Update](https://docs.spineworkspace.com/internal-docs/two-paths/system-path.md): Walk the System Path end to end: how SpineWorkspace processes intake, resolves identity, assembles context, routes decisions, executes capabilities, and.
- [Spine Fabric: The Shared Contextual Substrate](https://docs.spineworkspace.com/internal-docs/spine-fabric/overview.md): Internal orientation to Spine Fabric, the contextual layer where entities, events, evidence, and memory form a live business picture shared by humans, Twin.
- [Context Assembly: How Spine Fabric Builds Working Pictures](https://docs.spineworkspace.com/internal-docs/spine-fabric/contextual-layer.md): Deep dive into Spine Fabric's context assembly surface. Learn how working pictures are composed on demand from entities, events, evidence, and memory to power.
- [Twin: Internal Architecture](https://docs.spineworkspace.com/internal-docs/agents/twin.md): Internal notes on how Twin is composed: identity binding, context intake, reasoning loop, capability invocation, and continuity across sessions.
- [Core Agents: Internal Architecture](https://docs.spineworkspace.com/internal-docs/agents/core-agents.md): Internal notes on Discovery, Triage, and Schema core agents: their scope, when they run, what they produce, and how Twin and domain agents call them.
- [Domain Agents: Internal Architecture](https://docs.spineworkspace.com/internal-docs/agents/domain-agents.md): Internal notes on how domain agents are scoped: per-domain projections, domain skills, domain capabilities, and coordination with Twin and core agents.
- [Spine Agent Network: Internal Architecture](https://docs.spineworkspace.com/internal-docs/agents/spine-agent-network.md): Internal notes on the Spine Agent Network topology: personal Twins, core agents, domain agents, and the coordination and continuity guarantees between them.
- [Network Effect: Internal Architecture Note](https://docs.spineworkspace.com/internal-docs/agents/network-effect.md): Internal note on why the Spine Agent Network compounds in value: shared context, capabilities, memory, and handoff patterns across every new participant.
- [Agent Workflows: Internal Architecture](https://docs.spineworkspace.com/internal-docs/agents/workflows.md): Internal notes on how agent workflows are composed from triggers, capability steps, handoffs, and approvals, with receipts at every step for continuity.
- [Triage System — Complete Documentation](https://docs.spineworkspace.com/triage/README.md): Index for the triage system documentation: the governed intake and classification boundary for organizational memory.
- [01 — Overview](https://docs.spineworkspace.com/triage/01-OVERVIEW.md): What the triage system is: the classifier, linker, stager, and gatekeeper between incoming evidence and governed promotion.
- [02 — Execution Flow](https://docs.spineworkspace.com/triage/02-EXECUTION_FLOW.md): The end-to-end triage execution flow from intake trigger through classification, staging, and governed promotion.
- [03 — Triage Agents](https://docs.spineworkspace.com/triage/03-TRIAGE_AGENTS.md): The triage agents: their roles, scopes, and boundaries inside the governed classification path.
- [04 — Intake Triggers](https://docs.spineworkspace.com/triage/04-INTAKE_TRIGGERS.md): The events and sources that feed the triage system, from connector syncs to AI session outputs.
- [05 — Data Model](https://docs.spineworkspace.com/triage/05-DATA_MODEL.md): The triage data model: candidates, classifications, links, quality scores, and audit records.
- [06 — Classification](https://docs.spineworkspace.com/triage/06-CLASSIFICATION.md): How material is classified by type, domain, sensitivity, and confidence before review.
- [07 — Governance Boundary](https://docs.spineworkspace.com/triage/07-GOVERNANCE_BOUNDARY.md): The hard boundary between triage classification and governance approval: triage never promotes.
- [08 — Promotion Path](https://docs.spineworkspace.com/triage/08-PROMOTION_PATH.md): The governed promotion path from staged candidate to approved organizational memory.
- [09 — Memory Consolidation](https://docs.spineworkspace.com/triage/09-MEMORY_CONSOLIDATION.md): How approved material consolidates into organizational memory scopes with provenance.
- [10 — Activation Contract](https://docs.spineworkspace.com/triage/10-ACTIVATION_CONTRACT.md): The activation contract that governs when and how triage becomes active for a tenant.
- [11 — Code Map](https://docs.spineworkspace.com/triage/11-CODE_MAP.md): Map of triage source files, services, and entry points in the repository.
- [12 — Acceptance Tests](https://docs.spineworkspace.com/triage/12-ACCEPTANCE_TESTS.md): Acceptance tests that prove triage classification, governance boundaries, and promotion behavior.
- [13 — API Reference](https://docs.spineworkspace.com/triage/13-API_REFERENCE.md): API reference for the triage system's intake, classification, and staging endpoints.
- [Domain Workbenches: Overview](https://docs.spineworkspace.com/internal-docs/domains/overview.md): The domain workbenches document how each business domain is worked in SpineWorkspace: humans, Twin, agents, Spine context, and execution.
- [Account Success: Customer Lifecycle Management Workbench](https://docs.spineworkspace.com/internal-docs/domains/account-success/index.md): SpineWorkspace projection for Account Success teams managing customer health, renewals, expansion, and QBRs with unified context from CRM and support systems.
- [Account Success Domain: Business Needs and Operating Model](https://docs.spineworkspace.com/internal-docs/domains/account-success/domain.md): Operating model, team responsibilities, success metrics, and explicit non-goals for the Account Success function within SpineWorkspace.
- [Account Success Human Workbench: CSM Daily Interface](https://docs.spineworkspace.com/internal-docs/domains/account-success/human-workbench.md): The primary surfaces, tabs, and daily workflow for CSMs using the Account Success projection in SpineWorkspace.
- [Account Success Views: Data Projections and Specifications](https://docs.spineworkspace.com/internal-docs/domains/account-success/domain-views.md): Specifications for all Account Success views including data sources, projection rules, and the entities surfaced in each interface.
- [Account Success User Path: CSM Journey Through Spine](https://docs.spineworkspace.com/internal-docs/domains/account-success/user-flow.md): The eight-step user journey for CSMs working in the Account Success domain, from entry through action to continuity.
- [Account Success Business Context: Entities and Relationships](https://docs.spineworkspace.com/internal-docs/domains/account-success/business-context.md): The core business entities, relationships, events, and evidence types that power Account Success context assembly within Spine Fabric.
- [Account Success Spine Fabric: Context Assembly and Projection](https://docs.spineworkspace.com/internal-docs/domains/account-success/spine-fabric.md): How Spine Fabric ingests, unifies, and projects context for the Account Success domain from CRM, billing, support, and engagement systems.
- [Account Success AI Workbench: Twin for Customer Success](https://docs.spineworkspace.com/internal-docs/domains/account-success/ai-workbench.md): How Twin assembles account context, drafts QBR materials, proposes renewal strategies, and manages delegations in the Account Success domain.
- [Account Success AI Flow: How Twin Thinks and Acts](https://docs.spineworkspace.com/internal-docs/domains/account-success/ai-flow.md): The OODA-style AI reasoning flow for Account Success: observe, orient, assemble context, reason, delegate, collaborate, decide, and act with continuity.
- [Account Success Agents: Twin and Domain Specialists](https://docs.spineworkspace.com/internal-docs/domains/account-success/agents.md): The AI agent ecosystem for Account Success including Twin, core shared agents, and specialized domain agents for renewals, escalation, and success planning.
- [Account Success Communication Patterns and Channels](https://docs.spineworkspace.com/internal-docs/domains/account-success/communication.md): How humans, Twin, domain agents, and tools communicate in the Account Success domain to coordinate actions and share context.
- [Account Success Skills: AI Capabilities by Function](https://docs.spineworkspace.com/internal-docs/domains/account-success/skills.md): The specialized skills available to Twin and domain agents in Account Success including analysis, drafting, forecasting, and relationship management.
- [Account Success Capabilities: Governed Actions and Permissions](https://docs.spineworkspace.com/internal-docs/domains/account-success/capabilities.md): The read, write, communication, and workflow capabilities available in Account Success with concrete examples and authorization scopes.
- [Account Success Workflows: Triggers, Steps, and Handoffs](https://docs.spineworkspace.com/internal-docs/domains/account-success/workflows.md): Primary Account Success workflows including renewal, escalation, QBR, onboarding, and expansion with detailed triggers, steps, and approval paths.
- [Account Success Integrations: Source Systems and Connectors](https://docs.spineworkspace.com/internal-docs/domains/account-success/integrations.md): The source systems feeding the Account Success domain and what each provides for unified customer lifecycle management.
- [Account Success System Flow: Data Through Spine Fabric](https://docs.spineworkspace.com/internal-docs/domains/account-success/system-flow.md): The System Path for Account Success: how data is ingested, normalized, mapped, assembled, projected, and governed for customer lifecycle management.
- [Account Success Execution Flow: From Intent to Source Write](https://docs.spineworkspace.com/internal-docs/domains/account-success/execution-flow.md): The complete Execution Path for Account Success actions from intent through capability resolution to source system write-back and continuity.
- [Account Success Architecture: Domain Projection Design](https://docs.spineworkspace.com/internal-docs/domains/account-success/architecture.md): How the Account Success domain is architected as a Spine Fabric projection including the domain contract and reference to platform architectures.
- [Technical Account Success: Technical Customer Management Workbench](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/index.md): SpineWorkspace projection for TAMs and solutions engineers managing technical implementations, integration health, architecture guidance, and technical debt.
- [Technical Account Success Domain: Model and Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/domain.md): Operating model, team responsibilities, success metrics, and explicit non-goals for Technical Account Success within SpineWorkspace.
- [Technical Account Success Human Workbench: TAM Daily Interface](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/human-workbench.md): The primary surfaces, tabs, and daily workflow for TAMs using the Technical Account Success projection in SpineWorkspace.
- [Technical Account Success Views: Projections and Specifications](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/domain-views.md): Specifications for all Technical Account Success views including data sources, projection rules, and the technical entities surfaced in each interface.
- [Technical Account Success User Path: TAM Journey Through Spine](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/user-flow.md): The eight-step user journey for TAMs working in the Technical Account Success domain from entry to contextual action and continuity.
- [Technical Account Success Business Context: Entities and Events](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/business-context.md): The core business entities, relationships, events, and evidence types powering Technical Account Success context assembly within Spine Fabric.
- [Technical Account Success Spine Fabric: Context Assembly](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/spine-fabric.md): How Spine Fabric ingests, unifies, and projects context for the Technical Account Success domain from monitoring, ticketing, and code systems.
- [Technical Account Success AI Workbench: Twin for TAMs](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/ai-workbench.md): How Twin assembles technical context, drafts architecture guidance, monitors integration health, and manages delegations in Technical Account Success.
- [Technical Account Success AI Flow: Twin Technical Reasoning](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/ai-flow.md): The OODA-style AI reasoning flow for Technical Account Success covering observation, orientation, context assembly, and governed action.
- [Technical Account Success Agents: Twin and Technical Specialists](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/agents.md): The AI agent ecosystem for Technical Account Success including Twin, core shared agents, and specialized technical domain agents.
- [Technical Account Success Communication Patterns](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/communication.md): How humans, Twin, domain agents, and tools communicate in the Technical Account Success domain for coordinated technical management.
- [Technical Account Success Skills: AI Capabilities by Function](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/skills.md): The specialized skills available to Twin and domain agents in Technical Account Success including analysis, architecture, diagnostics, and forecasting.
- [Technical Account Success Capabilities: Governed Actions](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/capabilities.md): The read, write, communication, and workflow capabilities in Technical Account Success with concrete examples and authorization scopes.
- [Technical Account Success Workflows: Steps and Handoffs](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/workflows.md): Primary Technical Account Success workflows including implementation, escalation, architecture review, onboarding, and health audit with triggers and approvals.
- [Technical Account Success Integrations: Source Systems](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/integrations.md): The source systems feeding monitoring, ticketing, code, and project data into the Technical Account Success domain.
- [Technical Account Success System Flow: Data Through Spine](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/system-flow.md): The System Path for Technical Account Success covering intake, normalization, context assembly, projection, and governance for technical operations.
- [Technical Account Success Execution Path: Intent to Resolution](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/execution-flow.md): The complete Execution Path for Technical Account Success from intent through capability resolution to source system write-back and continuity.
- [Technical Account Success Architecture: Projection Design](https://docs.spineworkspace.com/internal-docs/domains/technical-account-success/architecture.md): How the Technical Account Success domain is architected as a Spine Fabric projection including the domain contract and reference to platform architectures.
- [Business Operations: Cross-Functional Process Optimization](https://docs.spineworkspace.com/internal-docs/domains/business-ops/index.md): Business Operations in SpineWorkspace unifies process management, approvals, and vendor oversight across teams using shared context from the Spine Fabric.
- [Business Operations Domain: Operating Model and Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/business-ops/domain.md): Defines how Business Operations runs inside SpineWorkspace: the operating model, team responsibilities, KPIs, and explicit non-goals.
- [Business Operations Human Workbench: Daily Practitioner Surfaces](https://docs.spineworkspace.com/internal-docs/domains/business-ops/human-workbench.md): What BizOps practitioners see in SpineWorkspace day to day: primary surfaces, tabs, tasks, and the operational loop they follow.
- [Business Operations Views: Data Sources and Projection Rules](https://docs.spineworkspace.com/internal-docs/domains/business-ops/domain-views.md): Reference table of Business Operations views, their purposes, source systems, and how Spine Fabric projects each into the domain.
- [Business Operations User Path: Practitioner Journey in Spine](https://docs.spineworkspace.com/internal-docs/domains/business-ops/user-flow.md): The end-to-end practitioner journey through Business Operations in SpineWorkspace, from entering the domain to taking action and continuing context.
- [Business Operations Business Context: Entities and Relationships](https://docs.spineworkspace.com/internal-docs/domains/business-ops/business-context.md): The entities, relationships, events, and evidence that define the Business Operations domain within Spine Fabric's unified context model.
- [Business Operations Spine Fabric: Context Assembly and Projection](https://docs.spineworkspace.com/internal-docs/domains/business-ops/spine-fabric.md): How Spine Fabric ingests, unifies, and projects context for Business Operations from Google Workspace, Asana, Notion, Linear, HRIS, and ERP.
- [Business Operations AI Workbench: Twin and Domain Proposals](https://docs.spineworkspace.com/internal-docs/domains/business-ops/ai-workbench.md): How Twin operates inside Business Operations: assembling dossiers, proposing approvals, drafting policy updates, and delegating operational tasks.
- [Business Operations AI Flow: Twin Decision Loop](https://docs.spineworkspace.com/internal-docs/domains/business-ops/ai-flow.md): The AI decision loop for Business Operations: how Twin moves from observation to governed action through context assembly and delegation.
- [Business Operations Agents: Twin Plus Domain Agents](https://docs.spineworkspace.com/internal-docs/domains/business-ops/agents.md): The agent network serving Business Operations: Twin, shared Core Agents, and specialized Domain Agents for approvals, vendors, and policies.
- [Business Operations Communication: Interaction Patterns](https://docs.spineworkspace.com/internal-docs/domains/business-ops/communication.md): How humans, Twin, and agents communicate in Business Operations: patterns for handoffs, approvals, and multi-agent collaboration.
- [Business Operations Skills: Domain Capabilities Twin Uses](https://docs.spineworkspace.com/internal-docs/domains/business-ops/skills.md): The analysis, drafting, review, and forecasting skills Twin and agents use to operate effectively in Business Operations.
- [Business Operations Capabilities: Governed Read, Write, and Workflow Actions](https://docs.spineworkspace.com/internal-docs/domains/business-ops/capabilities.md): The governed capabilities available in Business Operations: read, write, communication, and workflow actions with concrete examples.
- [Business Operations Workflows: Triggers, Steps, Handoffs, and Receipts](https://docs.spineworkspace.com/internal-docs/domains/business-ops/workflows.md): Primary Business Operations workflows in detail: Approval, Vendor Onboarding, Policy Review, OKR Cycle, and Process Improvement.
- [Business Operations Integrations: Source Systems and Feeds](https://docs.spineworkspace.com/internal-docs/domains/business-ops/integrations.md): The source systems feeding Business Operations and what each connector provides: Google Workspace, Asana, Notion, Linear, HRIS, and ERP.
- [Business Operations System Path: From Intake to Projection](https://docs.spineworkspace.com/internal-docs/domains/business-ops/system-flow.md): The system path for Business Operations data: how Spine Fabric intakes, normalizes, maps, and projects operational context into the workbench.
- [Business Operations Execution Path: Intent to Source-System Write](https://docs.spineworkspace.com/internal-docs/domains/business-ops/execution-flow.md): The governed execution path for Business Operations: from intent and context assembly through human approval to source-system write and continuity.
- [Business Operations Architecture: Domain Projection Contract](https://docs.spineworkspace.com/internal-docs/domains/business-ops/architecture.md): How Business Operations is architected as a Spine Fabric projection, including the domain contract and references to shared platform architecture.
- [Finance & RevOps: Revenue Management and Forecasting](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/index.md): Finance and RevOps in SpineWorkspace unifies revenue operations, financial forecasting, and reconciliation into a single contextual workbench.
- [Finance & RevOps Domain: Operating Model and Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/domain.md): Defines how Finance and RevOps operates inside SpineWorkspace: the operating model, team responsibilities, KPIs, and explicit non-goals.
- [Finance & RevOps Human Workbench: Daily Practitioner Surfaces](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/human-workbench.md): What Finance and RevOps practitioners see in SpineWorkspace day to day: primary surfaces, tabs, tasks, and the operational loop they follow.
- [Finance & RevOps Views: Data Sources and Projection Rules](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/domain-views.md): Reference table of Finance and RevOps views, their purposes, source systems, and how Spine Fabric projects each into the domain.
- [Finance & RevOps User Path: Practitioner Journey in Spine](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/user-flow.md): The end-to-end practitioner journey through Finance and RevOps in SpineWorkspace, from entering the domain to taking action and continuing context.
- [Finance & RevOps Business Context: Entities and Relationships](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/business-context.md): The entities, relationships, events, and evidence that define the Finance and RevOps domain within Spine Fabric's unified context model.
- [Finance & RevOps Spine Fabric: Context Assembly and Projection](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/spine-fabric.md): How Spine Fabric ingests, unifies, and projects context for Finance and RevOps from Stripe, QuickBooks, Chargebee, NetSuite, Salesforce, and HubSpot.
- [Finance & RevOps AI Workbench: Twin and Domain Proposals](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/ai-workbench.md): How Twin operates inside Finance and RevOps: assembling financial dossiers, proposing bookings, drafting forecasts, and delegating revenue tasks.
- [Finance & RevOps AI Flow: Twin Decision Loop](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/ai-flow.md): The AI decision loop for Finance and RevOps: how Twin moves from observation to governed action through context assembly and delegation.
- [Finance & RevOps Agents: Twin Plus Domain Agents](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/agents.md): The agent network serving Finance and RevOps: Twin, shared Core Agents, and specialized Domain Agents for revenue, reconciliation, and forecasting.
- [Finance & RevOps Communication: Interaction Patterns](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/communication.md): How humans, Twin, and agents communicate in Finance and RevOps: patterns for handoffs, approvals, and multi-agent collaboration.
- [Finance & RevOps Skills: Domain Capabilities Twin Uses](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/skills.md): The analysis, drafting, review, and forecasting skills Twin and agents use to operate effectively in Finance and RevOps.
- [Finance & RevOps Capabilities: Governed Read, Write, and Workflow Actions](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/capabilities.md): The governed capabilities available in Finance and RevOps: read, write, communication, and workflow actions with concrete examples.
- [Finance & RevOps Workflows: Triggers, Steps, Handoffs, and Receipts](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/workflows.md): Primary Finance and RevOps workflows in detail: Monthly Close, Renewal Booking, Reconciliation, Forecast Update, and Revenue Recognition.
- [Finance & RevOps Integrations: Source Systems and Feeds](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/integrations.md): The source systems feeding Finance and RevOps and what each connector provides: Stripe, QuickBooks, Chargebee, NetSuite, Salesforce, and HubSpot.
- [Finance & RevOps System Path: From Intake to Projection](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/system-flow.md): The system path for Finance and RevOps data: how Spine Fabric intakes, normalizes, maps, and projects financial context into the workbench.
- [Finance & RevOps Execution Path: Intent to Source-System Write](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/execution-flow.md): The governed execution path for Finance and RevOps: from intent and context assembly through human approval to source-system write and continuity.
- [Finance & RevOps Architecture: Domain Projection Contract](https://docs.spineworkspace.com/internal-docs/domains/finance-revops/architecture.md): How Finance and RevOps is architected as a Spine Fabric projection, including the domain contract and references to shared platform architecture.
- [Sales Workspace: Pipeline Management and Acquisition](https://docs.spineworkspace.com/internal-docs/domains/sales/index.md): The Sales domain in SpineWorkspace gives AEs, SDRs, and managers a shared view of pipelines, deals, and forecasts, all projected from Spine Fabric.
- [Sales Domain: Operating Model and Revenue Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/sales/domain.md): The Sales operating model defines who owns pipeline stages, forecast commitments, and deal governance, plus the KPIs that measure revenue execution.
- [Sales Human Workbench: Daily Surfaces and Tabs](https://docs.spineworkspace.com/internal-docs/domains/sales/human-workbench.md): The surfaces AEs and SDRs use daily in SpineWorkspace: pipeline tabs, deal review panels, activity feeds, and the action bar for governed next steps.
- [Sales Domain Views: Pipeline and Forecast Projections](https://docs.spineworkspace.com/internal-docs/domains/sales/domain-views.md): Reference table of all Sales views in SpineWorkspace, including data sources, projection rules, and the personas each view serves.
- [Sales User Flow: From Prospect Discovery to Closed Deal](https://docs.spineworkspace.com/internal-docs/domains/sales/user-flow.md): The eight-step user path in the Sales domain: how AEs and SDRs enter Spine, discover leads, understand context, and drive deals to close.
- [Sales Business Context: Entities, Events, and Evidence](https://docs.spineworkspace.com/internal-docs/domains/sales/business-context.md): The core business entities, relationships, events, and evidence types that define the Sales domain projection in Spine Fabric.
- [Sales Spine Fabric: Context Assembly for Revenue Teams](https://docs.spineworkspace.com/internal-docs/domains/sales/spine-fabric.md): How Spine Fabric ingests CRM, conversation, and engagement data to assemble unified sales context on demand for pipeline and forecast views.
- [Sales AI Workbench: Twin for Pipeline and Deals](https://docs.spineworkspace.com/internal-docs/domains/sales/ai-workbench.md): How Twin, your personal AI operator, works inside the Sales domain to assemble deal context, draft proposals, and delegate tasks to domain agents.
- [Sales AI Flow: How Twin Thinks Through Every Deal](https://docs.spineworkspace.com/internal-docs/domains/sales/ai-flow.md): The ten-step AI path in Sales: how Twin observes pipeline changes, assembles deal context, reasons, discovers risks, and proposes governed actions.
- [Sales Agents: Twin and Domain Specialists](https://docs.spineworkspace.com/internal-docs/domains/sales/agents.md): The AI agents operating in the Sales domain: Twin, shared Core Agents, and domain-specific specialists for discovery, quotes, and forecasting.
- [Sales Communication: Patterns Across People and Agents](https://docs.spineworkspace.com/internal-docs/domains/sales/communication.md): Communication patterns in the Sales domain: how humans, Twin, agents, and tools exchange context and actions across pipeline workflows.
- [Sales Skills: Domain Capabilities for Revenue Execution](https://docs.spineworkspace.com/internal-docs/domains/sales/skills.md): The analytical, creative, and operational skills Spine agents apply in the Sales domain, from deal scoring to proposal drafting and loss analysis.
- [Sales Capabilities: Governed Actions for Revenue Teams](https://docs.spineworkspace.com/internal-docs/domains/sales/capabilities.md): The governed capabilities available in the Sales domain, including read, write, communication, and workflow actions with authorization scopes and examples.
- [Sales Workflows: Lead to Close and Beyond](https://docs.spineworkspace.com/internal-docs/domains/sales/workflows.md): The primary Sales workflows in SpineWorkspace: triggers, steps, handoffs, approvals, and receipts for lead qualification, deal progression, and forecasting.
- [Sales Integrations: Source Systems for Pipeline Context](https://docs.spineworkspace.com/internal-docs/domains/sales/integrations.md): The source systems connected to the Sales domain in SpineWorkspace and what each provides for pipeline, activity, and conversation context.
- [Sales System Flow: Data Journey from Source to Workbench](https://docs.spineworkspace.com/internal-docs/domains/sales/system-flow.md): The ten-step system path for Sales: how Spine ingests CRM and engagement data, normalizes it, and projects it into pipeline and forecast views.
- [Sales Execution Flow: From Intent to Source-System Write](https://docs.spineworkspace.com/internal-docs/domains/sales/execution-flow.md): The fifteen-step execution path for Sales actions: how an intent like stage advance becomes a governed, receipted write to Salesforce with full audit trail.
- [Sales Architecture: Domain Projection and Contracts](https://docs.spineworkspace.com/internal-docs/domains/sales/architecture.md): How the Sales domain is architected as a Spine projection, including its domain contract and references to context, agent, and integration architectures.
- [Marketing Workspace: Campaign and Lead Generation Hub](https://docs.spineworkspace.com/internal-docs/domains/marketing/index.md): The Marketing domain in SpineWorkspace unifies campaign performance, content pipelines, and lead flow for demand gen, content, and marketing ops teams.
- [Marketing Domain: Operating Model and Growth Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/marketing/domain.md): The Marketing operating model defines campaign ownership, lead flow governance, content operations, and the KPIs that measure pipeline contribution.
- [Marketing Human Workbench: Daily Surfaces and Tabs](https://docs.spineworkspace.com/internal-docs/domains/marketing/human-workbench.md): The surfaces marketers use daily in SpineWorkspace: campaign dashboards, content pipelines, lead flow trackers, and program calendars.
- [Marketing Domain Views: Campaign and Funnel Projections](https://docs.spineworkspace.com/internal-docs/domains/marketing/domain-views.md): Reference table of all Marketing views in SpineWorkspace, including data sources, projection rules, and the personas each view serves.
- [Marketing User Flow: From Campaign Planning to Optimization](https://docs.spineworkspace.com/internal-docs/domains/marketing/user-flow.md): The eight-step user path in the Marketing domain: how teams enter Spine, discover campaigns, understand funnel context, and optimize for pipeline.
- [Marketing Business Context: Entities, Events, and Evidence](https://docs.spineworkspace.com/internal-docs/domains/marketing/business-context.md): The core business entities, relationships, events, and evidence types that define the Marketing domain projection in Spine Fabric.
- [Marketing Spine Fabric: Context Assembly for Growth Teams](https://docs.spineworkspace.com/internal-docs/domains/marketing/spine-fabric.md): How Spine Fabric ingests marketing automation, analytics, and CRM data to assemble unified campaign and funnel context on demand.
- [Marketing AI Workbench: Twin for Campaigns and Content](https://docs.spineworkspace.com/internal-docs/domains/marketing/ai-workbench.md): How Twin, your personal AI operator, works inside the Marketing domain to assemble campaign context, draft content, and delegate to domain agents.
- [Marketing AI Flow: How Twin Thinks Through Campaigns](https://docs.spineworkspace.com/internal-docs/domains/marketing/ai-flow.md): The ten-step AI path in Marketing: how Twin observes performance changes, assembles campaign context, reasons, discovers gaps, and proposes governed actions.
- [Marketing Agents: Twin and Domain Specialists](https://docs.spineworkspace.com/internal-docs/domains/marketing/agents.md): The AI agents operating in the Marketing domain: Twin, shared Core Agents, and domain-specific specialists for campaigns, content, and attribution.
- [Marketing Communication: Patterns Across People and Agents](https://docs.spineworkspace.com/internal-docs/domains/marketing/communication.md): Communication patterns in the Marketing domain: how humans, Twin, agents, and tools exchange context and actions across campaign and content workflows.
- [Marketing Skills: Domain Capabilities for Growth Execution](https://docs.spineworkspace.com/internal-docs/domains/marketing/skills.md): The analytical, creative, and operational skills Spine agents apply in the Marketing domain, from attribution modeling to content drafting and spend.
- [Marketing Capabilities: Governed Actions for Growth Teams](https://docs.spineworkspace.com/internal-docs/domains/marketing/capabilities.md): The governed capabilities available in the Marketing domain, including read, write, communication, and workflow actions with authorization scopes and examples.
- [Marketing Workflows: Campaign Launch to Content and Events](https://docs.spineworkspace.com/internal-docs/domains/marketing/workflows.md): The primary Marketing workflows in SpineWorkspace: triggers, steps, handoffs, approvals, and receipts for campaign launch, content publishing, and lead.
- [Marketing Integrations: Source Systems for Growth Context](https://docs.spineworkspace.com/internal-docs/domains/marketing/integrations.md): The source systems connected to the Marketing domain in SpineWorkspace and what each provides for campaign, content, lead, and attribution context.
- [Marketing System Flow: Data Journey from Source to Workbench](https://docs.spineworkspace.com/internal-docs/domains/marketing/system-flow.md): The ten-step system path for Marketing: how Spine ingests automation, analytics, and CRM data, normalizes it, and projects it into campaign and funnel views.
- [Marketing Execution Flow: From Intent to Source-System Write](https://docs.spineworkspace.com/internal-docs/domains/marketing/execution-flow.md): The fifteen-step execution path for Marketing actions: how an intent like budget adjustment becomes a governed, receipted write to HubSpot with full audit.
- [Marketing Architecture: Domain Projection and Contracts](https://docs.spineworkspace.com/internal-docs/domains/marketing/architecture.md): How the Marketing domain is architected as a Spine projection, including its domain contract and references to context, agent, and integration architectures.
- [Content Domain: Create, Publish, and Manage Knowledge](https://docs.spineworkspace.com/internal-docs/domains/content/index.md): Explore the Content domain in SpineWorkspace. Learn how editorial teams manage articles, campaigns, assets, and knowledge through the Human Workbench, AI.
- [Content Domain Needs, Model, and Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/content/domain.md): Learn how the Content domain operates: its operating model, team responsibilities, KPIs, and non-goals within SpineWorkspace.
- [Content Human Workbench Surfaces and Daily Loop](https://docs.spineworkspace.com/internal-docs/domains/content/human-workbench.md): Navigate the Content Human Workbench: primary surfaces, tabs, and the daily editorial loop for writers, editors, and content managers.
- [Content Domain Views, Sources, and Projection Rules](https://docs.spineworkspace.com/internal-docs/domains/content/domain-views.md): Reference table of Content domain views, their purposes, source systems, and how Spine Fabric projects them into the workbench.
- [Content User Path: Enter to Continue Across Editorial Work](https://docs.spineworkspace.com/internal-docs/domains/content/user-flow.md): Follow the Content User Path from entering the workbench through discovery, contextualization, decision, action, and continuity in editorial workflows.
- [Content Business Context: Entities, Events, and Evidence](https://docs.spineworkspace.com/internal-docs/domains/content/business-context.md): Understand the Content domain's business model: entities, relationships, events, and evidence that power editorial and knowledge workflows in Spine.
- [Content Domain: How Spine Fabric Assembles Context](https://docs.spineworkspace.com/internal-docs/domains/content/spine-fabric.md): Learn how Spine Fabric ingests content sources, unifies entities and events, assembles context, and projects into the Content domain views.
- [Content AI Workbench: Twin for Drafts, Assembly, and Review](https://docs.spineworkspace.com/internal-docs/domains/content/ai-workbench.md): Discover how Twin, the personal AI operator, helps Content practitioners draft, assemble context, and propose next steps across the editorial lifecycle.
- [Content AI Flow: How Twin Thinks Through Editorial Work](https://docs.spineworkspace.com/internal-docs/domains/content/ai-flow.md): Follow Twin's AI Flow in the Content domain: Observe, Orient, Assemble, Reason, Discover, Delegate, Collaborate, Decide, Act, and Continue.
- [Content Domain Agents: Twin and Specialized Assistants](https://docs.spineworkspace.com/internal-docs/domains/content/agents.md): Meet the AI agents serving the Content domain: Twin, Core Agents for discovery and triage, and Domain Agents for editorial and publishing tasks.
- [Content Communication Patterns Between Humans and Agents](https://docs.spineworkspace.com/internal-docs/domains/content/communication.md): Learn how communication flows between humans, Twin, Core Agents, and tools within the Content domain of SpineWorkspace.
- [Content Domain Skills: Analysis, Drafting, and Review](https://docs.spineworkspace.com/internal-docs/domains/content/skills.md): Browse the skills available in the Content domain, from content analysis and drafting to review, forecasting, and knowledge curation in SpineWorkspace.
- [Content Domain Capabilities: Read, Write, Communication, Workflow](https://docs.spineworkspace.com/internal-docs/domains/content/capabilities.md): Reference the governed capabilities available in the Content domain, with real examples like article creation, review routing, and publishing actions.
- [Content Domain Workflows: Creation, Review, Publication, and More](https://docs.spineworkspace.com/internal-docs/domains/content/workflows.md): Deep dive into Content domain workflows: triggers, steps, handoffs, approvals, and receipts for creation, review, publication, and knowledge updates.
- [Content Integrations: Source Systems and Data Feeds](https://docs.spineworkspace.com/internal-docs/domains/content/integrations.md): Reference table of source systems feeding the Content domain and what each provides, from Notion and WordPress to HubSpot and Contentful.
- [Content System Flow: Ingestion to Projection Pipeline](https://docs.spineworkspace.com/internal-docs/domains/content/system-flow.md): Follow the Content System Flow from intake through normalization, context assembly, projection, governance, and execution in Spine Fabric.
- [Content Execution Flow: Intent to Published Output and Receipt](https://docs.spineworkspace.com/internal-docs/domains/content/execution-flow.md): Learn how the Content Execution Flow transforms practitioner intent into governed actions, source-system writes, receipts, and continuity.
- [Content Domain Architecture: Projection and Contract Design](https://docs.spineworkspace.com/internal-docs/domains/content/architecture.md): Understand how the Content domain is architected as a Spine Fabric projection, including its domain contract and component relationships.
- [Service Domain: Deliver Customer Support at Scale](https://docs.spineworkspace.com/internal-docs/domains/service/index.md): Explore the Service domain in SpineWorkspace. Learn how service teams manage cases, SLAs, escalations, and resolutions through the Four Flows.
- [Service Domain Needs, Model, and Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/service/domain.md): Learn how the Service domain operates: its operating model, team responsibilities, KPIs, and non-goals within SpineWorkspace.
- [Service Human Workbench Surfaces and Daily Loop](https://docs.spineworkspace.com/internal-docs/domains/service/human-workbench.md): Navigate the Service Human Workbench: primary surfaces, tabs, and the daily support loop for reps, managers, and field service engineers.
- [Service Domain Views, Sources, and Projection Rules](https://docs.spineworkspace.com/internal-docs/domains/service/domain-views.md): Reference table of Service domain views, their purposes, source systems, and how Spine Fabric projects them into the workbench.
- [Service User Path: Enter to Continue Across Support Work](https://docs.spineworkspace.com/internal-docs/domains/service/user-flow.md): Follow the Service User Path from entering the workbench through discovery, contextualization, decision, action, and continuity in support workflows.
- [Service Business Context: Entities, Events, and Evidence](https://docs.spineworkspace.com/internal-docs/domains/service/business-context.md): Understand the Service domain's business model: entities, relationships, events, and evidence that power case management and resolution workflows in Spine.
- [Service Domain: How Spine Fabric Assembles Context](https://docs.spineworkspace.com/internal-docs/domains/service/spine-fabric.md): Learn how Spine Fabric ingests support sources, unifies entities and events, assembles context, and projects into the Service domain views.
- [Service AI Workbench: Twin for Triage, Resolution, and Context](https://docs.spineworkspace.com/internal-docs/domains/service/ai-workbench.md): Discover how Twin, the personal AI operator, helps Service reps triage cases, assemble context, and propose resolutions across the support lifecycle.
- [Service AI Flow: How Twin Thinks Through Support Work](https://docs.spineworkspace.com/internal-docs/domains/service/ai-flow.md): Follow Twin's AI Flow in the Service domain: Observe, Orient, Assemble, Reason, Discover, Delegate, Collaborate, Decide, Act, and Continue.
- [Service Domain Agents: Twin and Specialized Assistants](https://docs.spineworkspace.com/internal-docs/domains/service/agents.md): Meet the AI agents serving the Service domain: Twin, Core Agents for discovery and triage, and Domain Agents for case and SLA management.
- [Service Communication Patterns Between Humans and Agents](https://docs.spineworkspace.com/internal-docs/domains/service/communication.md): Learn how communication flows between humans, Twin, Core Agents, and tools within the Service domain of SpineWorkspace.
- [Service Domain Skills: Analysis, Triage, and Resolution](https://docs.spineworkspace.com/internal-docs/domains/service/skills.md): Browse the skills available in the Service domain, from case analysis and triage to drafting, SLA forecasting, and feedback management in SpineWorkspace.
- [Service Domain Capabilities: Read, Write, Communication, Workflow](https://docs.spineworkspace.com/internal-docs/domains/service/capabilities.md): Reference the governed capabilities available in the Service domain, with real examples like case updates, escalation creation, and SLA monitoring.
- [Service Domain Workflows: Triage, Resolution, Escalation, and More](https://docs.spineworkspace.com/internal-docs/domains/service/workflows.md): Deep dive into Service domain workflows: triggers, steps, handoffs, approvals, and receipts for triage, resolution, escalation, and SLA enforcement.
- [Service Integrations: Source Systems and Data Feeds](https://docs.spineworkspace.com/internal-docs/domains/service/integrations.md): Reference table of source systems feeding the Service domain and what each provides, from Zendesk and Salesforce to Freshdesk, Intercom, and Twilio.
- [Service System Flow: Ingestion to Projection Pipeline](https://docs.spineworkspace.com/internal-docs/domains/service/system-flow.md): Follow the Service System Flow from intake through normalization, context assembly, projection, governance, and execution in Spine Fabric.
- [Service Execution Flow: Intent to Resolution and Receipt](https://docs.spineworkspace.com/internal-docs/domains/service/execution-flow.md): Learn how the Service Execution Flow transforms practitioner intent into governed actions, source-system writes, receipts, and continuity across support work.
- [Service Domain Architecture: Projection and Contract Design](https://docs.spineworkspace.com/internal-docs/domains/service/architecture.md): Understand how the Service domain is architected as a Spine Fabric projection, including its domain contract and component relationships.
- [Product Engineering: Build and Ship with Spine Context](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/index.md): SpineWorkspace for Product Engineering unifies tickets, code, and incidents into one contextual workbench for planning, building, and operating software.
- [Product Engineering Domain: Operating Model and Needs](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/domain.md): How product and engineering teams run planning, delivery, and incident response in SpineWorkspace.
- [Product Engineering Human Workbench: Surfaces and Daily Flow](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/human-workbench.md): The surfaces and daily loop for PMs and engineers in the Product Engineering workbench.
- [Product Engineering Views: Projections and Data Sources](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/domain-views.md): Table of views in the Product Engineering domain with purpose, source data, and projection rules.
- [Product Engineering User Path: From Discovery to Ship](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/user-flow.md): How product and engineering practitioners enter Spine, discover context, and move from understanding to action and follow-through.
- [Product Engineering Business Context: Entities and Relationships](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/business-context.md): Entities, events, and evidence that shape the Product Engineering domain and how they relate across the delivery lifecycle.
- [Spine Fabric for Product Engineering: Context Assembly](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/spine-fabric.md): How Spine Fabric ingests engineering data, unifies entities, and projects the Product Engineering domain on demand.
- [Product Engineering AI Workbench: Twin for Build and Ship](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/ai-workbench.md): How Twin assembles context, drafts proposals, and delegates in the Product Engineering domain.
- [Product Engineering AI Flow: Observe to Operate](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/ai-flow.md): How Twin and domain agents observe engineering work, assemble context, reason, and act across the Product Engineering domain.
- [Product Engineering Agents: Twin and Domain Specialists](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/agents.md): Twin and the specialized agents that operate in the Product Engineering domain, from triage to schema reasoning.
- [Product Engineering Communication Patterns and Channels](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/communication.md): How humans, Twin, and agents communicate across tickets, incidents, and releases in the Product Engineering domain.
- [Product Engineering Skills: What Twin and Agents Can Do](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/skills.md): Skills available in the Product Engineering domain for analysis, drafting, review, and forecasting.
- [Product Engineering Capabilities: Governed Actions](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/capabilities.md): Capabilities in the Product Engineering domain with authorization, scope, and concrete examples of read, write, communication, and workflow actions.
- [Product Engineering Workflows: From Triage to Release](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/workflows.md): Primary workflows in the Product Engineering domain: triggers, steps, handoffs, approvals, and receipts.
- [Product Engineering Integrations: Connected Source Systems](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/integrations.md): Source systems that feed the Product Engineering domain and what each provides through Spine connectors.
- [Product Engineering System Flow: Data Path to Context](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/system-flow.md): How engineering data moves from source systems through Spine Fabric to the Product Engineering domain projection.
- [Product Engineering Execution Flow: Action to Result](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/execution-flow.md): How governed actions resolve in the Product Engineering domain, from intent through tool execution and receipt.
- [Product Engineering Architecture: Domain Projection](https://docs.spineworkspace.com/internal-docs/domains/product-engineering/architecture.md): How the Product Engineering domain is architected as a projection of the Spine Fabric with its contract and subsystems.
- [Personal Domain: Your Contextual Productivity Workbench](https://docs.spineworkspace.com/internal-docs/domains/personal/index.md): SpineWorkspace for the Personal domain unifies tasks, meetings, and notes into a private workbench so individual contributors plan and act with full context.
- [Personal Domain: Operating Model for Individual Contributors](https://docs.spineworkspace.com/internal-docs/domains/personal/domain.md): How individual contributors manage tasks, time, and commitments in the Personal domain within SpineWorkspace.
- [Personal Human Workbench: Surfaces and Daily Routine](https://docs.spineworkspace.com/internal-docs/domains/personal/human-workbench.md): The surfaces and daily loop for individual contributors in the Personal workbench.
- [Personal Domain Views: Projections and Data Sources](https://docs.spineworkspace.com/internal-docs/domains/personal/domain-views.md): Table of views in the Personal domain with purpose, source data, and projection rules for individual productivity.
- [Personal User Path: From Arrival to Action](https://docs.spineworkspace.com/internal-docs/domains/personal/user-flow.md): How individual contributors enter Spine, discover their work, and move from understanding to action and follow-through in the Personal domain.
- [Personal Business Context: Entities and Relationships](https://docs.spineworkspace.com/internal-docs/domains/personal/business-context.md): Entities, events, and evidence that shape the Personal domain and how they connect your tasks, meetings, and commitments.
- [Spine Fabric for Personal: Context Assembly for You](https://docs.spineworkspace.com/internal-docs/domains/personal/spine-fabric.md): How Spine Fabric ingests your personal data, unifies entities, and projects the Personal domain on demand.
- [Personal AI Workbench: Twin for Your Daily Flow](https://docs.spineworkspace.com/internal-docs/domains/personal/ai-workbench.md): How Twin assembles context, drafts proposals, and delegates in the Personal domain to keep you focused and on track.
- [Personal AI Flow: Observe to Continue](https://docs.spineworkspace.com/internal-docs/domains/personal/ai-flow.md): How Twin and domain agents observe your work, assemble context, reason, and act across the Personal domain.
- [Personal Domain Agents: Twin and Individual Assistants](https://docs.spineworkspace.com/internal-docs/domains/personal/agents.md): Twin and the specialized agents that operate in the Personal domain for scheduling, habits, and task management.
- [Personal Communication Patterns and Channels](https://docs.spineworkspace.com/internal-docs/domains/personal/communication.md): How you, Twin, and agents communicate across tasks, messages, and calendar events in the Personal domain.
- [Personal Domain Skills: What Twin and Agents Can Do](https://docs.spineworkspace.com/internal-docs/domains/personal/skills.md): Skills available in the Personal domain for analysis, drafting, review, and forecasting.
- [Personal Domain Capabilities: Governed Actions](https://docs.spineworkspace.com/internal-docs/domains/personal/capabilities.md): Capabilities in the Personal domain with authorization, scope, and concrete examples of read, write, communication, and workflow actions.
- [Personal Workflows: Daily Routines and Reviews](https://docs.spineworkspace.com/internal-docs/domains/personal/workflows.md): Primary workflows in the Personal domain: triggers, steps, handoffs, approvals, and receipts.
- [Personal Integrations: Connected Source Systems](https://docs.spineworkspace.com/internal-docs/domains/personal/integrations.md): Source systems that feed the Personal domain and what each provides through Spine connectors.
- [Personal System Flow: Data Path to Your Workbench](https://docs.spineworkspace.com/internal-docs/domains/personal/system-flow.md): How your personal data moves from source systems through Spine Fabric to the Personal domain projection.
- [Personal Execution Flow: Action to Result](https://docs.spineworkspace.com/internal-docs/domains/personal/execution-flow.md): How governed actions resolve in the Personal domain, from intent through tool execution and receipt.
- [Personal Domain Architecture: Projection for Individual Work](https://docs.spineworkspace.com/internal-docs/domains/personal/architecture.md): How the Personal domain is architected as a projection of the Spine Fabric with its contract and subsystems.
- [Human Resources: People Operations and Talent Management](https://docs.spineworkspace.com/internal-docs/domains/human-resources/index.md): Explore how SpineWorkspace projects the Human Resources domain, enabling recruiters, HRBPs, and People Ops to manage talent, reviews, and onboarding in one.
- [HR Domain: Operating Model and Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/human-resources/domain.md): Understand how the Human Resources domain operates within SpineWorkspace, including its operating model, team responsibilities, KPIs, and explicit non-goals.
- [HR Human Workbench: Surfaces and Daily Tasks](https://docs.spineworkspace.com/internal-docs/domains/human-resources/human-workbench.md): Discover the primary surfaces, tabs, and daily work loop for recruiters, HRBPs, and People Ops inside the Spine HR workbench.
- [HR Domain Views: Projected Data and Projection Rules](https://docs.spineworkspace.com/internal-docs/domains/human-resources/domain-views.md): Reference table of SpineWorkspace HR views, their purposes, source systems, and how Spine Fabric projects each from unified context.
- [HR User Flow: Practitioner Path Through the Workbench](https://docs.spineworkspace.com/internal-docs/domains/human-resources/user-flow.md): Follow the Human Resources practitioner journey from entry to continuation across the Spine Workbench, adapted for recruiters and HRBPs.
- [HR Business Context: Entities, Events, and Evidence](https://docs.spineworkspace.com/internal-docs/domains/human-resources/business-context.md): Learn how the Human Resources domain defines its business context through entities, relationships, events, and evidence tracked inside SpineWorkspace.
- [HR Spine Fabric: Context Assembly and Projection](https://docs.spineworkspace.com/internal-docs/domains/human-resources/spine-fabric.md): See how Spine Fabric ingests HR source systems, assembles entity context, and projects the Human Resources domain into the workbench.
- [HR AI Workbench: Twin and Intelligent Assistance](https://docs.spineworkspace.com/internal-docs/domains/human-resources/ai-workbench.md): Learn how Twin, the personal AI operator, assists HR practitioners by assembling context, drafting offers, and delegating tasks across the Spine Workbench.
- [HR AI Flow: How Twin Processes People Tasks](https://docs.spineworkspace.com/internal-docs/domains/human-resources/ai-flow.md): Follow Twin's OODA loop adapted for HR, from observation and context assembly to collaboration, decision, and continuous continuation.
- [HR Agents: Twin and Domain Specialists](https://docs.spineworkspace.com/internal-docs/domains/human-resources/agents.md): Meet the AI agents operating in the Human Resources domain, including Twin and specialized domain agents for scheduling, compliance, and communications.
- [HR Communication Patterns: Collaboration and Handoffs](https://docs.spineworkspace.com/internal-docs/domains/human-resources/communication.md): Understand how humans, Twin, and domain agents communicate and hand off context in the Human Resources domain.
- [HR Skills: Capabilities That Agents and Practitioners Share](https://docs.spineworkspace.com/internal-docs/domains/human-resources/skills.md): Browse the skills available in the Human Resources domain, from candidate analysis and offer drafting to review calibration and forecasting.
- [HR Capabilities: Governed Actions and Authorizations](https://docs.spineworkspace.com/internal-docs/domains/human-resources/capabilities.md): Reference the governed capabilities available in the Human Resources domain, including read, write, communication, and workflow actions with concrete examples.
- [HR Workflows: End-to-End People Processes](https://docs.spineworkspace.com/internal-docs/domains/human-resources/workflows.md): Learn how the primary Human Resources workflows run inside SpineWorkspace, from triggers and steps to handoffs, approvals, and receipts.
- [HR Integrations: Source Systems and Data Feeds](https://docs.spineworkspace.com/internal-docs/domains/human-resources/integrations.md): Reference the source systems that feed the Human Resources domain, what each provides, and how Spine Fabric ingests and uses that data.
- [HR System Flow: Data From Intake to Projection](https://docs.spineworkspace.com/internal-docs/domains/human-resources/system-flow.md): Follow the System Path for the Human Resources domain, from intake and normalization through context assembly, projection, and governance.
- [HR Execution Flow: Intent to Receipt and Continuation](https://docs.spineworkspace.com/internal-docs/domains/human-resources/execution-flow.md): Trace the Execution Path for HR actions, from intent and decision through capability resolution, approval, source-system write, and receipt.
- [HR Architecture: Domain Projection and Contracts](https://docs.spineworkspace.com/internal-docs/domains/human-resources/architecture.md): Understand how the Human Resources domain is architected as a projection of Spine Fabric, including its domain contract and reference architecture.
- [Legal Domain: Counsel and Compliance Management](https://docs.spineworkspace.com/internal-docs/domains/legal/index.md): Explore how SpineWorkspace projects the Legal domain, enabling general counsel, legal ops, and contracts managers to manage contracts, matters, and compliance.
- [Legal Domain: Operating Model and Responsibilities](https://docs.spineworkspace.com/internal-docs/domains/legal/domain.md): Understand how the Legal domain operates within SpineWorkspace, including its operating model, team responsibilities, KPIs, and explicit non-goals.
- [Legal Human Workbench: Surfaces and Daily Tasks](https://docs.spineworkspace.com/internal-docs/domains/legal/human-workbench.md): Discover the primary surfaces, tabs, and daily work loop for general counsel, legal ops, and contracts managers inside the Spine Legal workbench.
- [Legal Domain Views: Projected Data and Projection Rules](https://docs.spineworkspace.com/internal-docs/domains/legal/domain-views.md): Reference table of SpineWorkspace Legal views, their purposes, source systems, and how Spine Fabric projects each from unified context.
- [Legal User Flow: Practitioner Path Through the Workbench](https://docs.spineworkspace.com/internal-docs/domains/legal/user-flow.md): Follow the Legal practitioner journey from entry to continuation across the Spine Workbench, adapted for counsel and contracts managers.
- [Legal Business Context: Entities, Events, and Evidence](https://docs.spineworkspace.com/internal-docs/domains/legal/business-context.md): Learn how the Legal domain defines its business context through entities, relationships, events, and evidence tracked inside SpineWorkspace.
- [Legal Spine Fabric: Context Assembly and Projection](https://docs.spineworkspace.com/internal-docs/domains/legal/spine-fabric.md): See how Spine Fabric ingests Legal source systems, assembles entity context, and projects the Legal domain into the workbench.
- [Legal AI Workbench: Twin and Intelligent Assistance](https://docs.spineworkspace.com/internal-docs/domains/legal/ai-workbench.md): Learn how Twin, the personal AI operator, assists legal practitioners by assembling context, drafting clauses, flagging risks, and delegating tasks across the.
- [Legal AI Flow: How Twin Processes Legal Tasks](https://docs.spineworkspace.com/internal-docs/domains/legal/ai-flow.md): Follow Twin's OODA loop adapted for Legal, from observation and context assembly to collaboration, decision, and continuous continuation.
- [Legal Agents: Twin and Domain Specialists](https://docs.spineworkspace.com/internal-docs/domains/legal/agents.md): Meet the AI agents operating in the Legal domain, including Twin and specialized domain agents for contracts, compliance, and risk.
- [Legal Communication Patterns: Collaboration and Handoffs](https://docs.spineworkspace.com/internal-docs/domains/legal/communication.md): Understand how humans, Twin, and domain agents communicate and hand off context in the Legal domain.
- [Legal Skills: Capabilities That Agents and Practitioners Share](https://docs.spineworkspace.com/internal-docs/domains/legal/skills.md): Browse the skills available in the Legal domain, from contract analysis and clause drafting to compliance review and risk forecasting.
- [Legal Capabilities: Governed Actions and Authorizations](https://docs.spineworkspace.com/internal-docs/domains/legal/capabilities.md): Reference the governed capabilities available in the Legal domain, including read, write, communication, and workflow actions with concrete examples.
- [Legal Workflows: End-to-End Legal Processes](https://docs.spineworkspace.com/internal-docs/domains/legal/workflows.md): Learn how the primary Legal workflows run inside SpineWorkspace, from triggers and steps to handoffs, approvals, and receipts.
- [Legal Integrations: Source Systems and Data Feeds](https://docs.spineworkspace.com/internal-docs/domains/legal/integrations.md): Reference the source systems that feed the Legal domain, what each provides, and how Spine Fabric ingests and uses that data.
- [Legal System Flow: Data From Intake to Projection](https://docs.spineworkspace.com/internal-docs/domains/legal/system-flow.md): Follow the System Path for the Legal domain, from intake and normalization through context assembly, projection, and governance.
- [Legal Execution Flow: Intent to Receipt and Continuation](https://docs.spineworkspace.com/internal-docs/domains/legal/execution-flow.md): Trace the Execution Path for Legal actions, from intent and decision through capability resolution, approval, source-system write, and receipt.
- [Legal Architecture: Domain Projection and Contracts](https://docs.spineworkspace.com/internal-docs/domains/legal/architecture.md): Understand how the Legal domain is architected as a projection of Spine Fabric, including its domain contract and reference architecture.
- [Support Domain: Real-Time Technical Issue Resolution](https://docs.spineworkspace.com/internal-docs/domains/support/index.md): Support domain overview in SpineWorkspace: fast resolution, unified ticket context, and seamless teamwork between humans, Twin, and agents.
- [Support Domain: Operating Model and KPIs](https://docs.spineworkspace.com/internal-docs/domains/support/domain.md): Support operating model, team responsibilities, key KPIs, and explicit non-goals for the SpineWorkspace Support domain.
- [Support Human Workbench: Surfaces and Daily Flow](https://docs.spineworkspace.com/internal-docs/domains/support/human-workbench.md): The daily Support workbench view: queues, tools, tabs, and the triage-to-resolution loop within SpineWorkspace.
- [Support Domain Views: Data Projections and Sources](https://docs.spineworkspace.com/internal-docs/domains/support/domain-views.md): Support domain views mapped to source tools, projection rules, and how each view drives triage, incidents, and SLA management.
- [Support User Path: Journey Through Context and Action](https://docs.spineworkspace.com/internal-docs/domains/support/user-flow.md): The end-to-end support practitioner journey in SpineWorkspace, from entering the platform to resolving tickets and continuing the next session.
- [Support Business Context: Entities, Relationships, Events](https://docs.spineworkspace.com/internal-docs/domains/support/business-context.md): Support domain entity model with relationships, key events, and evidence types for precise context assembly in SpineWorkspace.
- [Support Spine Fabric: Context Assembly and Projections](https://docs.spineworkspace.com/internal-docs/domains/support/spine-fabric.md): How Spine Fabric ingests support sources, unifies entities and events, and projects live context into the Support domain.
- [Support AI Workbench: How Twin Assists Resolution](https://docs.spineworkspace.com/internal-docs/domains/support/ai-workbench.md): Twin acts as a support co-pilot: drafting replies, suggesting escalations, assembling incident context, and delegating to agents in the Support domain.
- [Support AI Flow: How Twin Reasoning Transforms Tickets](https://docs.spineworkspace.com/internal-docs/domains/support/ai-flow.md): The full AI reasoning flow in Support: observe, orient, assemble context, reason, discover, delegate, collaborate, decide, act, and continue.
- [Support Agents: Twin and Specialized Domain Agents](https://docs.spineworkspace.com/internal-docs/domains/support/agents.md): Twin plus Support-specific domain agents: Incident Response, Triage, and Knowledge, plus Core agents shared across Spine.
- [Support Communication: Patterns Across Humans, Twin, and Tools](https://docs.spineworkspace.com/internal-docs/domains/support/communication.md): Human-to-human, human-to-Twin, and agent-to-agent communication patterns that power fast, transparent support resolution.
- [Support Skills: Capabilities of the Support Agent Layer](https://docs.spineworkspace.com/internal-docs/domains/support/skills.md): Core skills in the Support domain: triage analysis, draft generation, incident review, SLA forecasting, and knowledge gap analysis.
- [Support Capabilities: Governed Read, Write, and Workflow Actions](https://docs.spineworkspace.com/internal-docs/domains/support/capabilities.md): Specific Support domain capabilities with authorization, scope, and receipts. Examples include ticket updates, escalations, and knowledge publication.
- [Support Workflows: Triage, Escalation, Incident, and Knowledge](https://docs.spineworkspace.com/internal-docs/domains/support/workflows.md): Primary Support workflows: triggers, steps, handoffs, approvals, and receipts for triage, incident response, escalation, and knowledge.
- [Support Integrations: Connected Source Systems](https://docs.spineworkspace.com/internal-docs/domains/support/integrations.md): Source systems feeding the Support domain and what each provides: tickets, incidents, errors, messaging, and escalation data.
- [Support System Flow: Data Journey from Intake to Projection](https://docs.spineworkspace.com/internal-docs/domains/support/system-flow.md): How Support data flows through intake, normalization, schema mapping, context assembly, projection, OODA, governance, and execution in Spine.
- [Support Execution Flow: From Intent to Source System Update](https://docs.spineworkspace.com/internal-docs/domains/support/execution-flow.md): The full governed execution path for a Support action: intent, decision, proposal, capability resolution, authorization, and receipt.
- [Support Architecture: Domain Projection and Contracts](https://docs.spineworkspace.com/internal-docs/domains/support/architecture.md): Support domain projection architecture: domain contract, context assembly, agent orchestration, capability enforcement, and event flow.
- [Founder Ops Domain: Executive Context and Decision Velocity](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/index.md): Founder Ops domain overview in SpineWorkspace: fast decisions, transparent commitments, unified executive communications, and seamless AI assistance.
- [Founder Ops Domain: Operating Model and KPIs](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/domain.md): Founder Ops operating model, executive responsibilities, key decision KPIs, and explicit non-goals for SpineWorkspace.
- [Founder Ops Human Workbench: Executive Surfaces and Daily Flow](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/human-workbench.md): The executive daily workbench: dashboard, decisions log, commitments tracker, meeting prep, and the leadership review loop in Spine.
- [Founder Ops Domain Views: Data Projections and Sources](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/domain-views.md): Founder Ops views mapped to Gmail, Calendar, Notion, Slack, and Salesforce: projection rules and how each view supports executive decision velocity.
- [Founder Ops User Path: Executive Journey Through Context](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/user-flow.md): The end-to-end Founder Ops user journey in SpineWorkspace: enter, discover decisions, understand context, and act with full continuity.
- [Founder Ops Business Context: Decisions, Commitments, and Events](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/business-context.md): Founder Ops entity model with relationships, key events, and evidence sources that power executive context assembly in Spine.
- [Founder Ops Spine Fabric: Executive Context Assembly](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/spine-fabric.md): How Spine Fabric ingests executive sources, unifies decisions and communications, and projects live Founder Ops views on demand.
- [Founder Ops AI Workbench: Twin for Executive Context](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/ai-workbench.md): Twin acts as an executive operations partner: drafting updates, assembling meeting prep, tracking commitments, and surfacing decisions in Founder Ops.
- [Founder Ops AI Flow: Twin Reasoning for Leadership Work](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/ai-flow.md): The full AI reasoning flow in Founder Ops: observe, assemble executive context, reason, discover, delegate, collaborate, decide, act, and continue.
- [Founder Ops Agents: Twin and Leadership Specialist Agents](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/agents.md): Twin plus Founder Ops domain agents: Commitment, Meeting Prep, Board Prep, and Metrics agents, along with Core agents shared across Spine.
- [Founder Ops Communication: Patterns for Executive Teams](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/communication.md): Human-to-human, human-to-Twin, and agent-to-agent communication patterns that power fast, transparent founder operations.
- [Founder Ops Skills: Executive Capabilities of the Agent Layer](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/skills.md): Core skills in Founder Ops: decision analysis, meeting preparation, commitment tracking, metric summarization, and update drafting.
- [Founder Ops Capabilities: Governed Executive Actions](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/capabilities.md): Specific Founder Ops capabilities with authorization and receipts: decision logging, commitment updates, meeting prep, and update publishing.
- [Founder Ops Workflows: Board Prep, Weekly Review, and Follow-Up](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/workflows.md): Primary Founder Ops workflows: triggers, steps, handoffs, approvals, and receipts for board prep, weekly review, decisions, and follow-up.
- [Founder Ops Integrations: Executive Source Systems](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/integrations.md): Source systems feeding the Founder Ops domain: Gmail, Calendar, Notion, Slack, Salesforce dashboards, and board portals.
- [Founder Ops System Flow: Data Journey from Intake to Projection](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/system-flow.md): How Founder Ops data flows through intake, normalization, schema mapping, context assembly, projection, OODA, governance, and execution in Spine.
- [Founder Ops Execution Flow: Intent to Source Update](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/execution-flow.md): The full governed execution path in Founder Ops: intent, context assembly, decision, capability resolution, authorization, and receipt.
- [Founder Ops Architecture: Executive Projection and Contracts](https://docs.spineworkspace.com/internal-docs/domains/founder-ops/architecture.md): Founder Ops domain projection architecture: domain contract, context assembly, agent orchestration, capability enforcement, and event flow.
- [Operations: Unified Company Administration and Coordination](https://docs.spineworkspace.com/internal-docs/domains/operations/index.md): Operations in SpineWorkspace centralizes requests, assets, vendors, and approvals into one contextual workbench for ops teams and administrators.
- [Operations Domain: Operating Model and Scope](https://docs.spineworkspace.com/internal-docs/domains/operations/domain.md): How the Operations domain is organized, what it owns, how success is measured, and what sits outside its responsibilities in SpineWorkspace.
- [Operations Human Workbench: Surfaces and Daily Workflow](https://docs.spineworkspace.com/internal-docs/domains/operations/human-workbench.md): The surfaces, tabs, and daily loop for operations managers and admins working inside the SpineWorkspace Operations domain.
- [Operations Views: Data Sources and Projection Rules](https://docs.spineworkspace.com/internal-docs/domains/operations/domain-views.md): Reference table of Operations domain views with their purpose, source data, and how Spine Fabric projects each into the workbench.
- [Operations User Path: From Request to Resolution](https://docs.spineworkspace.com/internal-docs/domains/operations/user-flow.md): The end-to-end practitioner journey through the Operations domain, from entering the workspace to reviewing outcomes and handing off context.
- [Operations Business Context: Entities, Events, and Evidence](https://docs.spineworkspace.com/internal-docs/domains/operations/business-context.md): The core entities, relationships, events, and evidence types that define the operational model inside SpineWorkspace.
- [Spine Fabric in Operations: Context Assembly and Projection](https://docs.spineworkspace.com/internal-docs/domains/operations/spine-fabric.md): How Spine Fabric ingests source systems, unifies operational entities, and projects contextual views into the Operations domain.
- [Operations AI Workbench: Twin and Automated Ops](https://docs.spineworkspace.com/internal-docs/domains/operations/ai-workbench.md): How Twin assembles context, proposes actions, drafts responses, and delegates tasks inside the Operations domain.
- [Operations AI Flow: How Twin Processes Work](https://docs.spineworkspace.com/internal-docs/domains/operations/ai-flow.md): The AI decision loop inside the Operations domain: observe, orient, assemble context, reason, discover, delegate, collaborate, decide, act, and continue.
- [Operations Agents: Twin and Specialized Domain Agents](https://docs.spineworkspace.com/internal-docs/domains/operations/agents.md): The agent roster for Operations: Twin as your personal operator plus shared and domain-specific agents that handle triage, discovery, and fulfillment.
- [Operations Communication: Patterns and Channels](https://docs.spineworkspace.com/internal-docs/domains/operations/communication.md): How humans, Twin, agents, and tools communicate within the Operations domain across every pattern and channel.
- [Operations Skills: Analysis, Drafting, and Review](https://docs.spineworkspace.com/internal-docs/domains/operations/skills.md): The skills available to practitioners and agents in the Operations domain, covering analysis, drafting, forecasting, and compliance review.
- [Operations Capabilities: Governed Actions and Permissions](https://docs.spineworkspace.com/internal-docs/domains/operations/capabilities.md): The read, write, communication, and workflow capabilities available in Operations, with concrete examples and authorization scopes.
- [Operations Workflows: Triggers, Steps, and Handoffs](https://docs.spineworkspace.com/internal-docs/domains/operations/workflows.md): Detailed breakdown of the primary Operations workflows: triggers, participant roles, approval gates, handoffs, and receipts.
- [Operations Integrations: Source Systems and Data Feeds](https://docs.spineworkspace.com/internal-docs/domains/operations/integrations.md): The source systems that feed the Operations domain and what each provides to Spine Fabric for unified context assembly.
- [Operations System Flow: From Intake to Projection](https://docs.spineworkspace.com/internal-docs/domains/operations/system-flow.md): The System Path in Operations: how external events are ingested, normalized, mapped, assembled, and projected into domain views.
- [Operations Execution Flow: Governed Action to Source Write](https://docs.spineworkspace.com/internal-docs/domains/operations/execution-flow.md): How an operational intent becomes a governed, audited action that writes back to source systems and preserves continuity across sessions.
- [Operations Architecture: Domain Projection and Contracts](https://docs.spineworkspace.com/internal-docs/domains/operations/architecture.md): How the Operations domain is architected as a projection of Spine Fabric, including its domain contract and references to shared platform architectures.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.