Unclassified

17 · Domain Projections

How each business domain receives its projection of the organizational Spine — Sales, Finance, Support, etc.

Domains receive projections, not separate Spines.

Each business domain — Sales, Finance, Support, Operations — does not own a separate Spine. It receives a projection of the organizational Spine appropriate to its domain and the user's authorization.

Domain Projection Model

Organizational Spine
      ↓
Projection Engine
      ↓
Domain Filter
      ↓
Role Filter
      ↓
Authorization Filter
      ↓
Domain Projection
      ↓
Domain Workbench

Domain Structure

Every domain follows the same ontology:

DOMAIN
 │
 ├── Business Context
 ├── Goals
 ├── Entities
 ├── Work Graph
 ├── Roles
 ├── Responsibilities
 ├── KPIs
 ├── Human Workbench
 ├── Twin Workbench
 ├── Agents
 ├── Capabilities
 ├── Skills
 ├── Workflows
 ├── Communications
 ├── Integrations
 ├── Execution
 ├── Reconciliation
 └── Memory

Supported Domains

DomainFocus
SalesPipeline, opportunities, forecasts
Account SuccessCustomer health, renewals, expansion
FinanceRevenue, billing, collections
SupportTickets, SLAs, escalations
OperationsProjects, tasks, workflows
MarketingCampaigns, leads, content
LegalContracts, compliance, risk
HREmployees, hiring, performance
Product EngineeringDevelopment, releases, incidents
Founder OpsStrategy, fundraising, board

Domain Projection Rules

RuleDescription
Single SpineOne organizational Spine, many projections
Role-scopedEach projection is scoped to the user's role
Authorization-gatedProjections respect RBAC
Cross-domainDomains can see related cross-domain data
Governance appliesSame governance rules across all domains

Domain Projections Connect to

LayerRelationship
Spine FabricReads canonical data
ProjectionsUses the Projection Engine
Human WorkbenchPresents domain-specific views
Twin WorkbenchProvides domain context to Twin
Work AllocationDomain-specific work assignment