Canon

Founder Canon 6.1

Supreme architectural canon governing the Business Context Spine, 12 surfaces, and ownership boundaries.

Founder Canon-aligned documentation update

Version: 6.1.0 — Schema/SSOT expansion
Date: 3 September 2026
Status: Canonical downstream documentation update

One Workspace. All Connected Software. Business Context. Shared Work. Human + AI Working Together.

Humans govern. AI helps. Spine preserves continuity.

1. Authority

This update is downstream of the 31 August 2026 SpineWorkspace Founder Canon. It expands the logical Business Context Spine contract without changing the Founder Canon's product hierarchy, memory boundaries, authority model, execution model, or four-flow architecture.

The authoritative product boundaries remain:

SpineWorkspace = product and daily working experience.
Human Workbench = primary human operating surface.
AI Workbench = AI-side operating environment.
Business Context Spine / Organizational Memory = shared organization-owned business context.
Personal Contextual Memory = human-specific continuity.
AI Continuity Memory = Twin/agent working continuity.
Work = durable human-AI coordination and handoff unit.
Projection Engine = authorized context composer.
Capability Fabric = provider-neutral execution resolution.
Governance = authority boundary.
Hermes = approved execution coordinator.
Completion = outcome re-ingestion → verification → reconciliation → rehydration.

The important addition in this document is that the Spine contract explicitly models business fields, relationships, source mappings, KPIs, signals, work, capabilities, continuity, provenance and human/AI interaction metadata.

2. What the Spine Is

The Business Context Spine is not a single database and not a generic enterprise graph.

It is the logical canonical contract for organizational operating context.

BUSINESS CONTEXT SPINE
│
├── Business Truth
│   ├── organizations
│   ├── people
│   ├── accounts
│   ├── contacts
│   ├── opportunities
│   ├── products
│   ├── contracts
│   ├── orders
│   ├── invoices
│   ├── subscriptions
│   ├── tickets
│   ├── projects
│   ├── features
│   ├── releases
│   ├── campaigns
│   ├── employees
│   └── other domain entities
│
├── Relationships
│   ├── ownership
│   ├── reporting
│   ├── account/contact
│   ├── opportunity/account
│   ├── ticket/account
│   ├── project/feature
│   ├── feature/release
│   ├── contract/account
│   └── cross-domain relationships
│
├── Operational State
│   ├── lifecycle status
│   ├── stage
│   ├── health
│   ├── SLA
│   ├── priority
│   ├── risk
│   ├── forecast
│   └── current owner
│
├── KPI / Measurement
│   ├── metric definitions
│   ├── current values
│   ├── historical values
│   ├── targets
│   ├── thresholds
│   └── attribution
│
├── Work / Continuity
│   ├── Work
│   ├── decisions
│   ├── commitments
│   ├── handoffs
│   ├── signals
│   └── next work
│
├── Knowledge / Evidence
│   ├── documents
│   ├── conversations
│   ├── notes
│   ├── source references
│   ├── evidence
│   └── provenance
│
└── Derived Context
    └── authorized projections for humans and AI

Physical storage is an implementation detail. The logical contract must remain stable even when storage, connectors, models or execution providers change.

3. Universal Spine Record Envelope

Every canonical entity MUST carry a common envelope.

Field	Type	Purpose
`id`	UUID/string	Spine identity
`tenant_id`	UUID/string	Tenant boundary
`workspace_id`	UUID/string	Workspace boundary
`entity_type`	enum	Canonical entity type
`external_ids`	object	Provider/source identifiers
`source_systems`	array	Systems contributing data
`source_primary`	string	Current authoritative source where defined
`source_record_refs`	array	Exact provider record references
`source_links`	array	Human/AI traceable source links
`schema_version`	string	Canonical schema version
`source_version`	string	Provider/source version where available
`created_at`	timestamp	Creation time
`updated_at`	timestamp	Last canonical update
`first_seen_at`	timestamp	First ingestion
`last_seen_at`	timestamp	Last observed in source
`deleted_at`	timestamp/null	Soft deletion/tombstone
`record_state`	enum	active/inactive/deleted/unknown
`confidence`	decimal	Data confidence; never authority
`freshness_at`	timestamp	Freshness reference
`provenance`	object	Source, transformation and lineage
`evidence_refs`	array	Supporting evidence
`visibility_scope`	enum	tenant/team/private/restricted
`classification`	enum	sensitivity/data class
`owner_id`	UUID/string	Responsible human/role
`tags`	array	Controlled classification
`custom_fields`	object	Tenant extension without changing core semantics

confidence MUST NOT authorize mutation. Authority comes from Governance.

4. Canonical Business Entity Model

4.1 Organization

Organization
- legal_name
- display_name
- organization_type
- industry
- industry_subsegment
- website
- domain
- headquarters
- billing_address
- operating_regions
- employee_count
- annual_revenue
- currency
- lifecycle_stage
- account_status
- parent_organization_id
- owner_id
- strategic_tier
- health_score
- risk_score
- source_systems

4.2 Account / Customer

Account
- account_name
- account_type
- customer_status
- lifecycle_stage
- industry
- sub_industry
- website
- domain
- employee_count
- annual_revenue
- territory
- region
- segment
- owner_id
- csm_id
- account_manager_id
- executive_sponsor_id
- parent_account_id
- customer_since
- renewal_date
- contract_value
- arr
- mrr
- total_contract_value
- payment_status
- product_adoption
- usage_level
- health_score
- commercial_risk
- churn_risk
- expansion_score
- relationship_strength
- last_activity_at
- next_review_at

4.3 Person / Contact

Person
- first_name
- last_name
- full_name
- email
- phone
- mobile
- title
- department
- role
- seniority
- account_id
- manager_id
- decision_role
- influence_level
- contact_status
- lifecycle_stage
- timezone
- location
- preferred_channel
- consent_status
- last_contact_at
- next_contact_at

4.4 Lead

Lead
- lead_name
- first_name
- last_name
- company
- email
- phone
- source
- campaign_id
- status
- lifecycle_stage
- score
- qualification_status
- owner_id
- territory
- industry
- estimated_value
- converted_account_id
- converted_contact_id
- converted_opportunity_id
- last_activity_at
- next_action_at

4.5 Opportunity / Deal

Opportunity
- opportunity_name
- account_id
- primary_contact_id
- owner_id
- amount
- currency
- stage
- probability
- forecast_category
- expected_close_date
- created_date
- sales_cycle_days
- source
- pipeline
- territory
- product_ids
- competitor
- use_case
- next_step
- next_step_due_at
- decision_date
- contract_start
- risk_score
- health_score
- win_probability
- loss_reason

4.6 Contract

Contract
- contract_number
- account_id
- contract_type
- status
- effective_date
- start_date
- end_date
- renewal_date
- auto_renew
- notice_period
- contract_value
- arr
- mrr
- currency
- payment_terms
- governing_region
- owner_id
- legal_owner_id
- commercial_owner_id
- document_ref
- obligations
- renewal_risk
- compliance_status

4.7 Subscription

Subscription
- subscription_id
- account_id
- product_id
- plan
- status
- start_date
- end_date
- renewal_date
- quantity
- unit_price
- mrr
- arr
- currency
- billing_interval
- trial_status
- cancellation_date
- cancellation_reason
- payment_status
- usage

4.8 Product / Service

Product
- product_name
- product_code
- description
- product_type
- category
- lifecycle_status
- version
- owner_id
- product_manager_id
- engineering_owner_id
- pricing_model
- list_price
- currency
- active_customers
- adoption_rate
- usage_metrics
- roadmap_status

4.9 Order

Order
- order_number
- account_id
- order_date
- status
- order_type
- currency
- subtotal
- tax
- discount
- total
- payment_status
- fulfillment_status
- owner_id
- product_lines
- contract_id

4.10 Invoice

Invoice
- invoice_number
- account_id
- contract_id
- subscription_id
- invoice_date
- due_date
- currency
- subtotal
- tax
- discount
- total
- balance_due
- payment_status
- collection_status
- paid_at
- aging_days
- payment_method

4.11 Ticket / Case / Incident

Ticket
- ticket_number
- account_id
- contact_id
- subject
- description_ref
- type
- status
- priority
- severity
- category
- subcategory
- channel
- created_at
- first_response_at
- resolution_at
- sla_target
- sla_due_at
- sla_status
- assigned_to
- team
- escalation_status
- escalation_reason
- related_product_id
- related_feature_id
- root_cause
- customer_impact
- sentiment
- resolution

4.12 Meeting / Interaction

Interaction
- interaction_type
- subject
- start_at
- end_at
- duration
- participants
- account_id
- opportunity_id
- ticket_id
- project_id
- owner_id
- channel
- summary_ref
- decisions
- commitments
- action_items
- sentiment
- follow_up_due_at
- source_reference

4.13 Task / Work Item

Task
- title
- description
- status
- priority
- owner_id
- assignee_id
- creator_id
- due_at
- completed_at
- parent_work_id
- related_entity_type
- related_entity_id
- dependency_ids
- blocker_ids
- effort
- estimate
- actual_effort
- next_action

4.14 Project

Project
- project_name
- project_code
- status
- lifecycle_stage
- owner_id
- sponsor_id
- team_id
- start_date
- target_date
- completed_date
- budget
- currency
- actual_cost
- progress_percent
- health_score
- risk_score
- objectives
- dependencies
- blockers

4.15 Campaign

Campaign
- campaign_name
- campaign_type
- status
- start_date
- end_date
- owner_id
- budget
- spend
- currency
- audience
- channel
- source
- leads_generated
- opportunities_generated
- pipeline_generated
- revenue_attributed
- impressions
- clicks
- conversions
- cac
- roi

4.16 Employee

Employee
- employee_id
- person_id
- employment_status
- employment_type
- title
- department
- manager_id
- location
- timezone
- start_date
- end_date
- cost_center
- role
- permissions_ref
- skills
- capacity

4.17 Feature / Product Work

Feature
- feature_name
- description
- product_id
- status
- priority
- product_owner_id
- engineering_owner_id
- target_release_id
- target_date
- business_value
- customer_value
- effort_estimate
- dependency_ids
- risk_score
- adoption_target

4.18 Bug / Engineering Issue

EngineeringIssue
- issue_key
- title
- type
- status
- priority
- severity
- repository
- project_id
- feature_id
- assignee_id
- reporter_id
- created_at
- resolved_at
- release_id
- customer_impact
- root_cause
- environment

4.19 Release / Deployment

Release
- release_id
- version
- product_id
- status
- planned_at
- deployed_at
- environment
- owner_id
- change_summary
- feature_ids
- issue_ids
- deployment_id
- rollback_available
- deployment_health
- incident_count

4.20 Knowledge / Document

KnowledgeRecord
- title
- document_type
- source_system
- source_record_id
- author_id
- owner_id
- created_at
- modified_at
- effective_date
- expiry_date
- classification
- content_ref
- chunk_refs
- embedding_ref
- linked_entity_ids
- linked_work_ids
- evidence_status
- promotion_status

5. Domain Coverage

The Spine is domain-neutral, but projections are domain-aware.

Domain	Primary entities	Representative business fields
Executive	Organization, Goal, KPI, Risk, Decision	mission, objectives, targets, actuals, variance, strategic priority, owner
Sales	Lead, Contact, Account, Opportunity, Quote, Contract	stage, amount, probability, close date, owner, next step, forecast
RevOps	Funnel, Pipeline, Forecast, KPI	conversion rates, velocity, coverage, win rate, CAC, ARR, MRR
Customer Success	Account, Subscription, Renewal, Health	health, adoption, renewal date, NRR, risk, success plan
Support	Ticket, Incident, SLA, Account	severity, priority, SLA, backlog, resolution time, escalation
Marketing	Campaign, Lead, Attribution, Content	spend, leads, pipeline, conversion, CAC, ROI, channel
Finance	Invoice, Payment, Subscription, Budget	revenue, MRR, ARR, AR, DSO, cash, burn, runway, variance
Operations	Process, Task, SLA, Workflow	owner, state, cycle time, SLA, throughput, exceptions
Product	Product, Feature, Roadmap, Release	status, value, adoption, roadmap, dependencies, target date
Engineering	Repository, Issue, PR, Release, Deployment	velocity, cycle time, deployment frequency, change failure
People	Employee, Team, Position	headcount, role, manager, capacity, location, employment status
Legal	Contract, Obligation, Policy, Matter	term, renewal, obligation, status, risk, owner
Platform/Admin	Tenant, Connection, Capability, Policy, Audit	health, scopes, grants, schema, policy, audit, lifecycle

This domain matrix is a projection map, not separate disconnected schemas.

6. KPI Contract

KPI is a first-class Spine object.

6.1 KPI fields

KPI
- kpi_id
- tenant_id
- domain
- metric_name
- metric_key
- description
- entity_type
- entity_id
- dimension_set
- value
- normalized_value
- unit
- currency
- aggregation
- formula
- numerator
- denominator
- period
- period_start
- period_end
- comparison_period
- target
- target_type
- threshold
- lower_threshold
- upper_threshold
- variance
- variance_percent
- trend
- direction
- status
- confidence
- freshness_at
- source_systems
- source_record_refs
- attribution
- owner_id
- audience
- visibility_scope
- alert_policy
- evidence_refs

6.2 Enterprise KPI families

Executive

ARR, MRR, NRR, GRR, Revenue, Gross Margin, Burn, Runway, Cash, Pipeline, Forecast, Customer Count, Churn, Strategic Goal Attainment.

Sales

Pipeline Value, Pipeline Coverage, Win Rate, Conversion Rate, Average Deal Size, Sales Cycle, Quota Attainment, Forecast Accuracy, Stage Aging.

RevOps

Lead-to-Opportunity, Opportunity-to-Win, Funnel Velocity, Pipeline Coverage, CAC, LTV, ARR Growth, Expansion, Contraction, Churn.

Customer Success

Health Score, Renewal Rate, NRR, GRR, Adoption, Usage, Time-to-Value, Open Risks, Renewal Coverage, NPS, CSAT.

Support

Ticket Volume, Backlog, First Response Time, Resolution Time, SLA Compliance, Escalation Rate, Reopen Rate, CSAT, Incident Frequency.

Marketing

Spend, Leads, MQL, SQL, Pipeline, Revenue, CAC, Conversion Rate, CTR, CPL, ROI, ROAS.

Finance

Revenue, MRR, ARR, AR, DSO, Cash, Burn, Runway, Gross Margin, Budget Variance, Invoice Aging, Collections.

Operations

Throughput, Cycle Time, SLA, Exception Rate, Backlog, Automation Rate, Workflow Success.

Product

Feature Adoption, Activation, Retention, Usage, Roadmap Attainment, Release Frequency, Customer Impact.

Engineering

Deployment Frequency, Lead Time, Change Failure Rate, MTTR, Cycle Time, PR Throughput, Issue Aging, Incident Rate.

People

Headcount, Hiring Plan, Time-to-Hire, Attrition, Capacity, Utilization, Open Roles.

Legal

Open Matters, Contract Cycle Time, Renewals, Obligation Status, Compliance Exceptions, Risk.

Platform

Connector Health, Sync Success, Freshness, Queue Depth, Pipeline Failures, Capability Availability, Execution Success, Verification Success, Reconciliation Exceptions, Governance Approval Time.

7. Human + AI Interaction Contract

The Spine must expose enough metadata for a human or AI worker to understand not only what a record is, but what can be done with it.

Every projected entity should therefore support:

InteractionMetadata
- readable
- searchable
- explainable
- actionable
- editable
- approvable
- delegable
- shareable
- subscribable
- watchable
- related_entities
- available_capabilities
- required_authority
- approval_required
- risk_level
- evidence_required
- freshness
- provenance
- next_best_work

7.1 Human-facing fields

display_name
summary
status
owner
priority
deadline
health
risk
next_action
related_work
recent_activity
evidence
source_links
available_actions
approval_state

7.2 AI-facing fields

entity_identity
semantic_type
business_role
relationships
current_state
historical_state
signals
goals
constraints
authority
available_capabilities
required_evidence
freshness
provenance
confidence
work_context
continuity_context
policy_context

AI-facing metadata is context, not permission. Governance remains authoritative.

8. Work as the Human-AI Coordination Object

Work is not merely a task.

Work
- work_id
- tenant_id
- work_type
- title
- objective
- status
- priority
- owner_id
- initiator
- human_participants
- ai_participants
- assigned_agent_ids
- related_entity_ids
- related_kpi_ids
- context_contract
- authority_context
- evidence_refs
- decision_refs
- commitment_refs
- dependency_ids
- blocker_ids
- next_action
- due_at
- handoff_state
- current_holder
- previous_holder
- continuity_thread_id
- proposal_refs
- execution_plan_refs
- outcome_refs
- verification_state
- reconciliation_state
- last_context_at
- updated_at

The governing rule is:

No participating worker begins meaningful work without a Spine-derived authorized context and Work identity.

This is the bridge between Human Workbench and AI Workbench.

9. Signal Contract

Signals are derived operational observations.

Signal
- signal_id
- signal_type
- domain
- entity_type
- entity_id
- severity
- priority
- observed_at
- detected_at
- metric_refs
- source_refs
- evidence_refs
- baseline
- current_value
- delta
- delta_percent
- threshold
- direction
- confidence
- impact
- recommended_work
- capability_refs
- owner_id
- status
- acknowledged_by
- resolved_at

Examples:

renewal_risk
pipeline_drop
support_spike
sla_breach
cash_runway_change
usage_decline
deployment_regression
campaign_underperformance
contract_renewal_due
security_or_compliance_exception

A signal is not truth by itself. It points to evidence and may initiate Work.

10. Decision and Commitment Continuity

Decision

Decision
- decision_id
- title
- question
- decision
- rationale
- alternatives
- decided_by
- authority_basis
- decided_at
- effective_at
- affected_entity_ids
- evidence_refs
- work_id
- supersedes_decision_id
- status

Commitment

Commitment
- commitment_id
- statement
- committed_by
- committed_to
- due_at
- status
- related_entity_ids
- source_interaction_id
- evidence_refs
- owner_id
- fulfillment_at
- verification_state

These become organizational continuity only through the applicable promotion/governance boundary.

11. Connector → Spine Mapping Contract

This is the missing logical layer between connectors and the canonical schema.

SOURCE PROVIDER
      ↓
SOURCE OBJECT
      ↓
SOURCE FIELD
      ↓
MAPPING RULE
      ↓
CANONICAL ENTITY
      ↓
CANONICAL FIELD
      ↓
TRANSFORMATION
      ↓
IDENTITY / RELATIONSHIP RESOLUTION
      ↓
PROVENANCE + EVIDENCE
      ↓
PROMOTION / GOVERNANCE
      ↓
CANONICAL WRITE
      ↓
EVENT / INVALIDATION
      ↓
PROJECTION

11.1 Mapping record

FieldMapping
- mapping_id
- connector_id
- provider
- provider_object
- provider_field
- source_path
- canonical_entity
- canonical_field
- data_type
- transformation
- normalization_rule
- identity_key
- relationship_rule
- null_policy
- conflict_policy
- source_precedence
- sensitivity
- write_mode
- sync_direction
- version
- effective_at
- status
- test_status
- provenance_rule
- evidence_rule

11.2 Example

Salesforce.Account.Name
        ↓
Account.account_name

Salesforce.Account.Industry
        ↓
Account.industry

Salesforce.Account.AnnualRevenue
        ↓
Account.annual_revenue

Salesforce.Opportunity.Amount
        ↓
Opportunity.amount

Zendesk.Ticket.Status
        ↓
Ticket.status

Stripe.Customer.id
        ↓
Account.external_ids.stripe_customer_id

GitHub.Issue.number
        ↓
EngineeringIssue.external_ids.github_issue_number

Google Calendar event
        ↓
Interaction

A provider never defines the Spine schema. The provider contributes data to the Spine contract.

12. Connector Category → Canonical Domain Coverage

Connector category	Typical systems	Primary Spine contributions
CRM	Salesforce, HubSpot, Dynamics	Account, Person, Lead, Opportunity, Activity
ERP	NetSuite, SAP, Dynamics	Customer, Vendor, Product, Order, Invoice, Inventory
Finance/Billing	Stripe, QuickBooks, Xero, Chargebee	Customer, Subscription, Invoice, Payment, Revenue
Support	Zendesk, Freshdesk, Intercom	Ticket, SLA, Incident, Interaction, Customer Health
Communication	Gmail, Outlook, Slack, Teams, Zoom	Interaction, Commitment, Decision, Evidence
Calendar	Google Calendar, Microsoft Calendar	Meeting, Interaction, Task, Commitment
Productivity	Notion, Confluence, Drive, OneDrive, Dropbox	Knowledge, Document, Project, Evidence
Project/Product	Jira, Linear, GitHub	Project, Feature, EngineeringIssue, Release
Marketing	HubSpot, Mailchimp, GA4, LinkedIn Ads, Meta	Campaign, Lead, Attribution, KPI
HRIS	Workday, BambooHR, Greenhouse, Deel, Gusto	Employee, Team, Position, Capacity
Legal	DocuSign, Ironclad, Drive, Notion	Contract, Obligation, Policy, Matter
Infrastructure	Cloudflare, Vercel, AWS, Azure, GCP	Service, Deployment, Incident, Platform KPI
AI	OpenAI, Anthropic, Gemini, other providers	Model execution, AI runtime metrics, proposals, AI continuity metadata
Identity	Descope, Entra ID, Google, GitHub	Identity, principal, grants, consent, authority

13. Source Precedence and Conflict Resolution

When multiple connectors contribute the same canonical field:

1. Explicit tenant source-of-authority rule
2. Entity-specific source precedence
3. Freshness / effective-date policy
4. Verified provider state
5. Reconciliation result
6. Conflict → unresolved state + evidence

Never silently overwrite conflicting business truth.

The Spine should preserve:

current canonical value
+
source contributors
+
source timestamps
+
conflict state
+
resolution decision

14. Four Flows

Flow A — Structured operational data

Provider
→ Gateway / Loader
→ Normalizer
→ Identity + relationship resolution
→ Mapping
→ Promotion
→ Governed Spine Writer
→ Canonical Business Context
→ Event / invalidation
→ Projection

Flow B — Unstructured business context

Email / document / message / artifact
→ Loader
→ Normalizer
→ reference/chunk/evidence
→ mapping
→ promotion
→ Knowledge / Evidence / Spine

Flow C — AI continuity

authorized AI/chat reference
→ Brainstorming / AI context
→ Triage
→ compare / dedupe / consolidate
→ candidate
→ governance
→ bounded context / AI continuity

Flow C does not become canonical organizational truth merely because an AI generated it.

Flow D — platform binding

Identity
→ tenant
→ consent
→ connection
→ policy
→ capability grants
→ activation
→ compiled runtime binding

15. Canonical Write Rule

Source
→ Ingest
→ Normalize / Triage
→ Provenance
→ Promotion decision
→ Governed Writer
→ Canonical commit
→ Outbox/event
→ Projection invalidation
→ Rehydrate

No direct agent canonical writes.

No provider success treated as final truth.

No cache treated as truth.

16. Capability Contract

A capability is the semantic bridge from business intent to execution.

Capability
- capability_id
- name
- version
- category
- description
- input_schema
- output_schema
- target_entity_types
- supported_domains
- route_types
- provider_routes
- connector_dependencies
- authority_scope
- risk_level
- execution_mode
- approval_required
- idempotency_policy
- evidence_requirements
- timeout
- retry_policy
- compensation_policy
- verification_policy
- health
- availability
- owner
- audit_policy

Capability categories:

READ
SEARCH
ANALYZE
CREATE
UPDATE
COMMUNICATE
SCHEDULE
ASSIGN
APPROVE
EXECUTE
SYNC
VERIFY
RECONCILE
REPORT

Route types can include API connector, MCP, agent-to-agent, workflow, browser, local execution, AI execution or human execution where authorized.

17. Governance Contract

Every consequential capability invocation carries:

principal
tenant
workspace
role
delegation
capability
target
risk
data_classification
policy
approval_requirement
approval_token
authority_expiry
audit_ref

Possible outcomes:

ALLOW
DENY
REQUIRE_APPROVAL
BOUNDED_DELEGATION

Confidence never grants authority.

18. Execution and Closure

Intent
→ Capability resolution
→ Governance
→ Approval if required
→ Hermes
→ Provider/API/MCP/Agent/Workflow
→ Outcome
→ Re-ingestion
→ Verification
→ Reconciliation
→ Canonical update
→ Memory/knowledge/continuity update
→ Projection refresh
→ Human + AI rehydration
→ Next Work

An Outcome Event is observed provider output, not automatically verified business truth.

19. Continuity Run

A Continuity Run is the traceable lifecycle of work.

ContinuityRun
- run_id
- work_id
- initiating_principal
- context_snapshot_ref
- intent
- capability_id
- governance_decision
- approval_ref
- execution_plan_ref
- provider_route
- execution_id
- outcome_ref
- verification_ref
- reconciliation_ref
- resulting_entity_refs
- memory_refs
- projection_refs
- started_at
- completed_at
- status
- failure_reason

This allows the organization to reconstruct:

what was intended → what context was used → who/what acted → what authority existed → what happened → what was verified → what changed → what the human and AI now see.

20. Customer Zero Schema Coverage

Customer Zero should exercise the full logical model across:

Executive
Sales
RevOps
Customer Success
Support
Marketing
Finance
Operations
Product
Engineering
People
Legal
Platform/Admin

Representative connected applications from the project model include CRM, finance, product/engineering, marketing, support, communication, documentation and infrastructure systems.

The Customer Zero gate is not “all connectors installed.”

It is:

connector
→ mapping
→ hydration
→ canonical field population
→ relationship resolution
→ KPI activation
→ signal activation
→ Work projection
→ human interaction
→ AI context
→ governed capability
→ execution
→ outcome
→ verification
→ reconciliation
→ continuity
→ rehydration

21. Completeness Invariant

A connector is not considered integrated merely because OAuth succeeds.

For every activated connector/object, the system must be able to answer:

What business domain does it contribute to?
What canonical entity does each important object map to?
What canonical fields are populated?
What relationships are created?
What KPIs become available?
What signals become detectable?
What evidence is retained?
What capabilities become executable?
What authority is required?
What human actions are exposed?
What AI context becomes available?
What continuity is retained?
How is the provider outcome verified and reconciled?
What happens when the connector is revoked or unavailable?

This is the Connector → Schema → Context → Capability → Continuity contract.

22. Canonical Repository Placement

This document should be represented by the canonical repository structure:

docs/canonical/
  00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md
  01-PRODUCT-AND-EXPERIENCE.md
  02-BUSINESS-CONTEXT-SPINE.md
  03-HUMAN-WORKBENCH-AND-PERSONAL-MEMORY.md
  04-AI-WORKBENCH-TWIN-AGENTS-AND-AI-MEMORY.md
  05-WORK-CONTINUITY-AND-HANDOFF.md
  06-IDENTITY-CONFIG-INTEGRATION-DISCOVERY-ACTIVATION.md
  07-INGESTION-FOUR-FLOWS-AND-GOVERNED-WRITES.md
  08-PROJECTION-UI-AND-CONTEXT-COMPOSITION.md
  09-CAPABILITY-FABRIC-AND-ADK.md
  10-GOVERNANCE-AUTHORITY-AND-APPROVAL.md
  11-HERMES-EXECUTION-AND-PROVIDERS.md
  12-SYNC-VERIFICATION-RECONCILIATION.md
  13-MEMORY-KNOWLEDGE-EVIDENCE-AND-PRIVACY.md
  14-MCP-CONTINUITY-BRIDGE-MARKETPLACE-SDK.md
  15-SECURITY-TENANCY-AUDIT-OBSERVABILITY.md
  16-ONBOARDING-CUSTOMER-ZERO-AND-GO-LIVE.md
  17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md
  18-CANONICAL-GLOSSARY.md
  contracts/
  adr/
  archive/

02-BUSINESS-CONTEXT-SPINE.md owns the logical schema. Connector-specific documents may extend mappings but may not redefine canonical business entities.

23. Final Mental Model

                    BUSINESS GOALS
               Mission · Objectives · KPIs
                         │
                         ▼
              BUSINESS CONTEXT SPINE
                         │
       ┌─────────────────┼──────────────────┐
       │                 │                  │
       ▼                 ▼                  ▼
   HUMAN WORK        AI WORK             KNOWLEDGE
       │                 │                  │
       └────────────── WORK ────────────────┘
                         │
                 CAPABILITY FABRIC
                         │
                    GOVERNANCE
                         │
                      HERMES
                         │
                 EXTERNAL SYSTEMS
                         │
              OUTCOME / EVIDENCE
                         │
            VERIFY → RECONCILE
                         │
                         ▼
               SPINE CANONICAL STATE
                         │
                         ▼
                 REHYDRATE BOTH
                         │
                    NEXT WORK

The missing logical piece is therefore explicitly closed:

Connectors do not map directly to the UI. They contribute source fields to canonical business objects through versioned mappings; canonical objects generate relationships, KPIs, signals, context and capabilities; those are projected to humans and AI; governed execution produces outcomes that are re-ingested, verified, reconciled and preserved as continuity.