Canon

Business Context Spine 6.1

Universal tenant spine schema, multi-engine persistence, and operational truth model.

Complete Logical Schema, SSOT and Connector Mapping Contract

Status: Canonical downstream schema specification
Parent authority: SpineWorkspace Founder Canon, 31 August 2026

Purpose

This document is the logical contract for the Business Context Spine. It answers the previously ambiguous question:

How does connector data become canonical business context, and how does that context become human work, AI context, KPI/signal intelligence and governed capability execution?

Core chain

Connector
→ Provider Object
→ Provider Field
→ Mapping
→ Canonical Object
→ Canonical Field
→ Relationship
→ KPI / Signal
→ Projection
→ Human + AI Work
→ Capability
→ Governance
→ Execution
→ Outcome
→ Verify
→ Reconcile
→ Canonical State
→ Continuity

A. Logical Spine Layers

Layer	Meaning	Canonical examples
1. Identity & Authority	Who/where/under whose authority	tenant, workspace, principal, role, grants
2. Business Entities	What the organization operates	accounts, people, opportunities, contracts, tickets
3. Relationships	How entities connect	account-contact, account-opportunity, feature-release
4. Operational State	Current business state	status, stage, health, risk, SLA, owner
5. KPI & Signals	Measurement and detected change	ARR, pipeline, churn risk, SLA breach
6. Work & Continuity	Human/AI coordination	Work, decisions, commitments, handoffs
7. Knowledge & Evidence	Supporting information	documents, conversations, source links
8. Derived Context	Authorized runtime representation	Human projection, AI context, Work context

These are logical layers; physical storage can differ.

B. Universal Field Groups

Every business object is composed from these reusable field groups.

Identity

id, tenant_id, workspace_id, entity_type, external_ids, source_record_refs

Lifecycle

status, lifecycle_stage, created_at, updated_at, first_seen_at, last_seen_at, deleted_at

Ownership

owner_id, team_id, department, role, responsible_principal

Commercial

currency, amount, contract_value, arr, mrr, price, quantity, payment_status

Time

start_date, end_date, due_at, renewal_date, effective_date, period_start, period_end

Health / Risk

health_score, risk_score, priority, severity, confidence, trend, impact

Relationships

parent_id, account_id, contact_id, related_entity_ids, dependency_ids, blocker_ids

Evidence

source_links, source_record_refs, evidence_refs, provenance, freshness_at

Interaction

available_capabilities, approval_required, required_authority, next_action, next_best_work, watchable, shareable

Governance

visibility_scope, classification, policy_refs, authority_context, audit_ref

C. Canonical Object Inventory

The canonical business object set is:

Organization
Account
Person
Lead
Opportunity
Contract
Subscription
Product
Order
Invoice
Payment
Ticket
Incident
Interaction
Meeting
Task
Work
Project
Campaign
Employee
Team
Feature
EngineeringIssue
Repository
Release
Deployment
Goal
Decision
Commitment
KPI
Signal
KnowledgeRecord
EvidenceRecord
Policy
Approval
ExecutionPlan
OutcomeEvent
ContinuityRun
ConnectionBinding
Capability

Connector-specific provider objects remain provider objects until mapped into these canonical objects or retained as source evidence.

D. Business Domain Coverage

Executive

Objects: Organization, Goal, KPI, Risk, Decision, Work.

Fields:

mission, objective, strategic_priority, target, actual, variance, owner_id, deadline, risk, dependencies, decision, rationale.

Sales

Objects: Lead, Person, Account, Opportunity, Contract, Interaction.

Fields:

lead_source, qualification_status, stage, amount, probability, forecast_category, expected_close_date, sales_cycle_days, owner_id, next_step, competitor, use_case, win_probability, loss_reason.

RevOps

Objects: Funnel, Opportunity, KPI, Forecast, Account, Subscription.

Fields:

pipeline_value, pipeline_coverage, stage_conversion, velocity, win_rate, quota, quota_attainment, forecast, forecast_accuracy, cac, ltv, arr, mrr, expansion, contraction, churn.

Customer Success

Objects: Account, Subscription, Contract, Renewal/Work, Interaction, Ticket, KPI.

Fields:

health_score, adoption, usage, renewal_date, renewal_risk, success_plan, nrr, grr, time_to_value, open_risks, executive_sponsor_id, last_review_at, next_review_at.

Support

Objects: Ticket, Incident, SLA, Account, Interaction.

Fields:

severity, priority, category, sla_target, sla_due_at, sla_status, first_response_at, resolution_at, backlog_state, escalation_status, customer_impact, root_cause, sentiment.

Marketing

Objects: Campaign, Lead, Person, Attribution, KPI, Content.

Fields:

budget, spend, channel, audience, leads_generated, mql, sql, opportunities_generated, pipeline_generated, revenue_attributed, impressions, clicks, conversions, cpl, cac, roi, roas.

Finance

Objects: Invoice, Payment, Subscription, Contract, Order, KPI, Budget.

Fields:

invoice_date, due_date, balance_due, payment_status, aging_days, revenue, mrr, arr, gross_margin, cash, burn, runway, dso, budget, actual, variance.

Operations

Objects: Process, Task, Workflow, SLA, Project, KPI.

Fields:

process_name, owner_id, status, cycle_time, throughput, sla, exception_rate, backlog, automation_rate, dependencies, blockers.

Product

Objects: Product, Feature, Goal, Roadmap, Release, KPI.

Fields:

business_value, customer_value, priority, target_date, adoption_target, adoption_actual, status, dependency_ids, risk_score, roadmap_status.

Engineering

Objects: Repository, EngineeringIssue, Project, Release, Deployment, Incident, KPI.

Fields:

repository, issue_type, severity, priority, assignee_id, created_at, resolved_at, release_id, environment, deployment_health, cycle_time, lead_time, deployment_frequency, change_failure_rate, mttr.

People

Objects: Employee, Team, Position, Goal, Work.

Fields:

employment_status, employment_type, title, department, manager_id, location, capacity, skills, cost_center, start_date, end_date, open_role.

Legal

Objects: Contract, Obligation, Policy, Matter, Approval.

Fields:

contract_type, effective_date, end_date, renewal_date, notice_period, obligation, compliance_status, risk_level, legal_owner_id, approval_state.

Platform / Administration

Objects: Tenant, ConnectionBinding, Capability, Policy, Approval, Audit, KPI.

Fields:

provider, connection_status, scopes, consent, policy_grants, capability_grants, primary_route, health, freshness, sync_state, reconciliation_state, revocation, schema_version.

E. Connector-to-Object Mapping

CRM

Salesforce / HubSpot / Dynamics
Account       → Account
Contact       → Person
Lead          → Lead
Opportunity   → Opportunity
Case          → Ticket
Task/Event    → Interaction / Task

ERP / Finance

Customer       → Account
Vendor         → Organization / Person
Item/Product   → Product
Sales Order    → Order
Invoice        → Invoice
Payment        → Payment
Subscription   → Subscription

Support

Ticket/Case    → Ticket
Incident       → Incident
SLA            → SLA
Requester      → Person
Organization   → Account

Communication

Email          → Interaction / EvidenceRecord
Calendar Event → Meeting / Interaction
Slack Message  → Interaction / EvidenceRecord
Teams Message  → Interaction / EvidenceRecord
Zoom Meeting   → Meeting / Interaction

Productivity / Knowledge

Document       → KnowledgeRecord
Page           → KnowledgeRecord
Comment        → EvidenceRecord
Folder/space   → Knowledge relationship

Product / Engineering

Jira Issue     → EngineeringIssue / Feature / Task
Linear Issue   → EngineeringIssue / Feature / Task
GitHub Issue   → EngineeringIssue
Pull Request   → Engineering evidence / Task
Repository     → Repository
Release        → Release
Deployment     → Deployment

Marketing

Campaign       → Campaign
Contact        → Person
Lead           → Lead
Analytics      → KPI / EvidenceRecord
Attribution    → KPI attribution

HR

Worker         → Employee
Position       → Position
Department     → Team / Organization unit
Manager        → Employee relationship

Infrastructure

Service        → Platform Service
Deployment     → Deployment
Incident       → Incident
Metric         → KPI
Log/Event      → EvidenceRecord / Signal

F. Field Mapping Example

provider: salesforce
object: Account
field: AnnualRevenue

canonical:
  entity: Account
  field: annual_revenue
  type: money

transformation:
  - numeric_normalization
  - currency_resolution

identity:
  key: Salesforce.Account.Id

provenance:
  retain_source_record: true
  retain_source_timestamp: true

write:
  mode: governed_canonical
  conflict_policy: tenant_precedence

The mapping layer is versioned and testable.

G. SSOT Rule

The Spine becomes SSOT for normalized, governed organizational business context.

It is not SSOT for:

raw provider payloads;
provider-specific UI behavior;
transient caches;
model-generated guesses;
unverified execution outcomes;
private personal memory;
AI working memory.

Those remain in their respective state planes.

H. KPI → Signal → Work

KPI
 ↓
Threshold / trend / comparison
 ↓
Signal
 ↓
Business impact
 ↓
Work
 ↓
Capability
 ↓
Governance
 ↓
Execution
 ↓
Outcome
 ↓
Verification
 ↓
Reconciliation

Example:

Renewal KPI
ARR at risk ↑
       ↓
renewal_risk signal
       ↓
Account Work created
       ↓
prepare_renewal capability
       ↓
Governance
       ↓
Twin prepares renewal brief
       ↓
Human reviews
       ↓
send_followup capability
       ↓
Hermes
       ↓
CRM / Gmail
       ↓
Outcome
       ↓
Re-ingest
       ↓
Verified activity
       ↓
Account timeline / health refreshed

I. Human and AI Projection Fields

The Projection Engine should be able to derive:

display_fields
filter_fields
sort_fields
group_fields
summary_fields
kpi_fields
signal_fields
relationship_fields
evidence_fields
work_fields
action_fields
approval_fields
continuity_fields

For AI:

context_entity
semantic_type
business_role
current_state
history
relationships
evidence
freshness
goals
constraints
authority
capabilities
risk
policy
work_id
continuity_refs

J. Completeness Test

For each connector and object:

[ ] discovered
[ ] consented
[ ] connection bound
[ ] source object classified
[ ] fields mapped
[ ] identity resolved
[ ] relationships resolved
[ ] provenance retained
[ ] initial hydration complete
[ ] KPI contribution known
[ ] signal contribution known
[ ] projection contribution known
[ ] capability contribution known
[ ] governance requirements known
[ ] execution route known
[ ] outcome re-ingestion tested
[ ] verification tested
[ ] reconciliation tested
[ ] revocation tested

OAuth-only integration is therefore not an integration-complete state.