Unclassified
Domain Documentation
Overview
The Domain Documentation layer provides comprehensive, domain-specific documentation for how Spine Workspace operates within each business domain. Unlike internal documentation (which explains how Spine is built) or public documentation (which explains the product), domain documentation explains how a business domain is worked by humans, assisted by Twin and its workers, contextualized by Spine, processed by the system, and executed across connected source systems.
The Three Documentation Layers
Spine Workspace Docs
│
┌────────────────────┼────────────────────┐
│ │ │
PUBLIC DOCS INTERNAL DOCS DOMAIN DOCS
│ │ │
Product / Dev Architecture / Ops Business Work
│ │
│ ┌──────┴──────┐
│ │ │
│ Human AI/System
│ Workbench Working
│ │ │
└──────────── Spine ────────┘
Domain Documentation Structure
Each domain follows the Canonical Domain Sidebar template:
DOMAIN
│
├── Home
├── Domain
│ ├── Overview
│ ├── Business Needs
│ ├── Operating Model
│ ├── Responsibilities
│ ├── Roles
│ ├── Entities
│ ├── Processes
│ └── Domain Vocabulary
│
├── Human Workbench
│ ├── Overview
│ ├── Home
│ ├── My Work
│ ├── Inbox
│ ├── Tasks
│ ├── My Queue
│ ├── Approvals
│ ├── Notifications
│ ├── Recent Work
│ ├── Favorites
│ ├── Communications
│ └── Personal
│
├── Domain Views
│ ├── View 1
│ ├── View 2
│ ├── View N
│ ├── Grid Views
│ ├── Board Views
│ ├── Canvas Views
│ ├── Timeline Views
│ └── Entity 360 Views
│
├── User Flow
│ ├── Enter
│ ├── Discover
│ ├── Understand
│ ├── Contextualize
│ ├── Decide
│ ├── Act
│ ├── Review
│ └── Continue
│
├── Business Context
│ ├── Context Model
│ ├── Entities
│ ├── Relationships
│ ├── Events
│ ├── Transactions
│ ├── KPIs
│ ├── Communications
│ ├── Documents
│ ├── Decisions
│ ├── Evidence
│ └── History
│
├── Spine Fabric
│ ├── Domain Projection
│ ├── Context Sources
│ ├── Context Scopes
│ ├── Entity Context
│ ├── Event Sequence
│ ├── Organizational Memory
│ ├── Knowledge
│ ├── Multimodal Data
│ ├── Memory
│ └── Continuity
│
├── AI Workbench
│ ├── Twin
│ ├── AI Working
│ ├── Context Assembly
│ ├── Agent Runs
│ ├── Suggestions
│ ├── Recommendations
│ ├── Proposals
│ ├── Delegation
│ └── Handoffs
│
├── AI Flow
│ ├── Observe
│ ├── Orient
│ ├── Context Assembly
│ ├── Reason
│ ├── Discover
│ ├── Delegate
│ ├── Collaborate
│ ├── Decide
│ ├── Act
│ └── Continue
│
├── Agents
│ ├── Twin
│ ├── Coworker
│ ├── Discovery Agent
│ ├── Triage Agent
│ ├── Schema Agent
│ ├── Domain Agents
│ └── Sub-Agents
│
├── Communication & Handoff
│ ├── Human ↔ Human
│ ├── Human ↔ Twin
│ ├── Twin ↔ Agent
│ ├── Agent ↔ Agent
│ ├── Agent ↔ Tool
│ ├── Tool ↔ Spine
│ ├── Context Handoff
│ ├── Work Handoff
│ └── Continuity
│
├── Skills
│ ├── Domain Skills
│ ├── User Skills
│ ├── Twin Skills
│ ├── Agent Skills
│ ├── Workflow Skills
│ └── Skill Configuration
│
├── Capabilities
│ ├── Domain Capabilities
│ ├── Tool Capabilities
│ ├── Read Capabilities
│ ├── Write Capabilities
│ ├── Communication
│ ├── Search
│ └── Governed Actions
│
├── Workflows
│ ├── Domain Workflows
│ ├── Human Workflows
│ ├── AI Workflows
│ ├── Handoff Workflows
│ ├── Approval Workflows
│ ├── Automation
│ └── Workflow Templates
│
├── Integrations
│ ├── Connected Systems
│ ├── Integrations Hub
│ ├── Connectors
│ ├── Connector Mappings
│ ├── MCP Tools
│ ├── Source Systems
│ └── Write-back
│
├── System Flow
│ ├── Interaction Intake
│ ├── Event Intake
│ ├── Flow A — Structured
│ ├── Flow B — Unstructured
│ ├── Flow C — AI
│ ├── Flow D — Identity
│ ├── Loader
│ ├── Normalizer
│ ├── Schema Mapping
│ ├── Event Processing
│ ├── Context Extraction
│ ├── Context Assembly
│ ├── Projection
│ ├── OODA
│ ├── Agent Routing
│ ├── Governance
│ └── State Update
│
├── Execution Flow
│ ├── Intent
│ ├── Context
│ ├── Decision
│ ├── Proposal
│ ├── Capability Resolution
│ ├── Agent Handoff
│ ├── Tool Selection
│ ├── MCP / Connector
│ ├── Authorization
│ ├── Human Approval
│ ├── Workflow Execution
│ ├── Source-System Write
│ ├── Receipt
│ ├── Event
│ └── Spine Continuation
│
└── Architecture
├── Domain Architecture
├── Projection Architecture
├── Context Architecture
├── Spine Architecture
├── Agent Architecture
├── Capability Architecture
├── Workflow Architecture
├── Integration Architecture
└── Event Architecture
The Four Flows
1. Human Workbench
What the human sees and does. Views, work, context, actions.
2. AI Workbench
What Twin/AI operators do. Twin, skills, agents, handoffs, proposals.
3. System Flow
How the system processes context. Ingestion, OODA, pipelines, context extraction.
4. Execution Flow
How work is actually executed. Capabilities, MCP/Connectors, workflows, write-back, receipts.
Available Domains
| Domain | Description | Status |
|---|---|---|
| Account Success | Customer lifecycle management | ✅ Active |
| Technical Account Success | Technical customer management | ✅ Active |
| Business Ops | Business operations management | ✅ Active |
| Finance / RevOps | Financial and revenue operations | ✅ Active |
| Sales | Sales pipeline and customer acquisition | ✅ Active |
| Marketing | Marketing campaigns and lead generation | ✅ Active |
| Content | Content creation and management | ✅ Active |
| Service | Customer service and support | ✅ Active |
| Product Engineering | Product development and engineering | ✅ Active |
| Personal | Personal productivity and work management | ✅ Active |
| Human Resources | HR and people operations | ✅ Active |
| Legal | Legal and compliance | ✅ Active |
| Support | Technical and customer support | ✅ Active |
| Founder Ops | Founder and executive operations | ✅ Active |
| Operations | General operations and administration | ✅ Active |
Architecture Relationship
DOMAIN
│
┌────────────┼────────────┐
│ │ │
▼ ▼ ▼
HUMAN AI SYSTEM
WORKBENCH WORKBENCH FLOW
│ │ │
│ │ │
└────────────┼────────────┘
│
SPINE FABRIC
│
Context + Memory
Events + Evidence
Communication
Handoffs
Continuity
│
▼
EXECUTION FLOW
│
Capabilities
MCP / Connectors
Workflows
Governance
│
▼
SOURCE SYSTEMS
│
▼
RECEIPTS
│
▼
SPINE
Key Principle
Domain documentation does not document a collection of screens. It documents how a business domain is worked by humans, assisted by Twin and its workers, contextualized by Spine, processed by the system, and executed across connected source systems.
This directly mirrors the product architecture rather than creating a separate documentation abstraction.