{"slug":"canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON-6.1","title":"Founder Canon 6.1","section":"canonical","sectionLabel":"Canon","status":"canon","type":"document","path":"canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON-6.1.md","bytes":31683,"description":"Supreme architectural canon governing the Business Context Spine, 12 surfaces, and ownership boundaries.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## Founder Canon-aligned documentation update\n**Version:** 6.1.0 — Schema/SSOT expansion  \n**Date:** 3 September 2026  \n**Status:** Canonical downstream documentation update\n\n> **One Workspace. All Connected Software. Business Context. Shared Work. Human + AI Working Together.**\n>\n> **Humans govern. AI helps. Spine preserves continuity.**\n\n## 1. Authority\n\nThis 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.\n\nThe authoritative product boundaries remain:\n\n- SpineWorkspace = product and daily working experience.\n- Human Workbench = primary human operating surface.\n- AI Workbench = AI-side operating environment.\n- Business Context Spine / Organizational Memory = shared organization-owned business context.\n- Personal Contextual Memory = human-specific continuity.\n- AI Continuity Memory = Twin/agent working continuity.\n- Work = durable human-AI coordination and handoff unit.\n- Projection Engine = authorized context composer.\n- Capability Fabric = provider-neutral execution resolution.\n- Governance = authority boundary.\n- Hermes = approved execution coordinator.\n- Completion = outcome re-ingestion → verification → reconciliation → rehydration.\n\nThe 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**.\n\n---\n\n# 2. What the Spine Is\n\nThe Business Context Spine is not a single database and not a generic enterprise graph.\n\nIt is the **logical canonical contract** for organizational operating context.\n\n```text\nBUSINESS CONTEXT SPINE\n│\n├── Business Truth\n│   ├── organizations\n│   ├── people\n│   ├── accounts\n│   ├── contacts\n│   ├── opportunities\n│   ├── products\n│   ├── contracts\n│   ├── orders\n│   ├── invoices\n│   ├── subscriptions\n│   ├── tickets\n│   ├── projects\n│   ├── features\n│   ├── releases\n│   ├── campaigns\n│   ├── employees\n│   └── other domain entities\n│\n├── Relationships\n│   ├── ownership\n│   ├── reporting\n│   ├── account/contact\n│   ├── opportunity/account\n│   ├── ticket/account\n│   ├── project/feature\n│   ├── feature/release\n│   ├── contract/account\n│   └── cross-domain relationships\n│\n├── Operational State\n│   ├── lifecycle status\n│   ├── stage\n│   ├── health\n│   ├── SLA\n│   ├── priority\n│   ├── risk\n│   ├── forecast\n│   └── current owner\n│\n├── KPI / Measurement\n│   ├── metric definitions\n│   ├── current values\n│   ├── historical values\n│   ├── targets\n│   ├── thresholds\n│   └── attribution\n│\n├── Work / Continuity\n│   ├── Work\n│   ├── decisions\n│   ├── commitments\n│   ├── handoffs\n│   ├── signals\n│   └── next work\n│\n├── Knowledge / Evidence\n│   ├── documents\n│   ├── conversations\n│   ├── notes\n│   ├── source references\n│   ├── evidence\n│   └── provenance\n│\n└── Derived Context\n    └── authorized projections for humans and AI\n```\n\nPhysical storage is an implementation detail. The logical contract must remain stable even when storage, connectors, models or execution providers change.\n\n---\n\n# 3. Universal Spine Record Envelope\n\nEvery canonical entity MUST carry a common envelope.\n\n| Field | Type | Purpose |\n|---|---|---|\n| `id` | UUID/string | Spine identity |\n| `tenant_id` | UUID/string | Tenant boundary |\n| `workspace_id` | UUID/string | Workspace boundary |\n| `entity_type` | enum | Canonical entity type |\n| `external_ids` | object | Provider/source identifiers |\n| `source_systems` | array | Systems contributing data |\n| `source_primary` | string | Current authoritative source where defined |\n| `source_record_refs` | array | Exact provider record references |\n| `source_links` | array | Human/AI traceable source links |\n| `schema_version` | string | Canonical schema version |\n| `source_version` | string | Provider/source version where available |\n| `created_at` | timestamp | Creation time |\n| `updated_at` | timestamp | Last canonical update |\n| `first_seen_at` | timestamp | First ingestion |\n| `last_seen_at` | timestamp | Last observed in source |\n| `deleted_at` | timestamp/null | Soft deletion/tombstone |\n| `record_state` | enum | active/inactive/deleted/unknown |\n| `confidence` | decimal | Data confidence; never authority |\n| `freshness_at` | timestamp | Freshness reference |\n| `provenance` | object | Source, transformation and lineage |\n| `evidence_refs` | array | Supporting evidence |\n| `visibility_scope` | enum | tenant/team/private/restricted |\n| `classification` | enum | sensitivity/data class |\n| `owner_id` | UUID/string | Responsible human/role |\n| `tags` | array | Controlled classification |\n| `custom_fields` | object | Tenant extension without changing core semantics |\n\n`confidence` MUST NOT authorize mutation. Authority comes from Governance.\n\n---\n\n# 4. Canonical Business Entity Model\n\n## 4.1 Organization\n\n```text\nOrganization\n- legal_name\n- display_name\n- organization_type\n- industry\n- industry_subsegment\n- website\n- domain\n- headquarters\n- billing_address\n- operating_regions\n- employee_count\n- annual_revenue\n- currency\n- lifecycle_stage\n- account_status\n- parent_organization_id\n- owner_id\n- strategic_tier\n- health_score\n- risk_score\n- source_systems\n```\n\n## 4.2 Account / Customer\n\n```text\nAccount\n- account_name\n- account_type\n- customer_status\n- lifecycle_stage\n- industry\n- sub_industry\n- website\n- domain\n- employee_count\n- annual_revenue\n- territory\n- region\n- segment\n- owner_id\n- csm_id\n- account_manager_id\n- executive_sponsor_id\n- parent_account_id\n- customer_since\n- renewal_date\n- contract_value\n- arr\n- mrr\n- total_contract_value\n- payment_status\n- product_adoption\n- usage_level\n- health_score\n- commercial_risk\n- churn_risk\n- expansion_score\n- relationship_strength\n- last_activity_at\n- next_review_at\n```\n\n## 4.3 Person / Contact\n\n```text\nPerson\n- first_name\n- last_name\n- full_name\n- email\n- phone\n- mobile\n- title\n- department\n- role\n- seniority\n- account_id\n- manager_id\n- decision_role\n- influence_level\n- contact_status\n- lifecycle_stage\n- timezone\n- location\n- preferred_channel\n- consent_status\n- last_contact_at\n- next_contact_at\n```\n\n## 4.4 Lead\n\n```text\nLead\n- lead_name\n- first_name\n- last_name\n- company\n- email\n- phone\n- source\n- campaign_id\n- status\n- lifecycle_stage\n- score\n- qualification_status\n- owner_id\n- territory\n- industry\n- estimated_value\n- converted_account_id\n- converted_contact_id\n- converted_opportunity_id\n- last_activity_at\n- next_action_at\n```\n\n## 4.5 Opportunity / Deal\n\n```text\nOpportunity\n- opportunity_name\n- account_id\n- primary_contact_id\n- owner_id\n- amount\n- currency\n- stage\n- probability\n- forecast_category\n- expected_close_date\n- created_date\n- sales_cycle_days\n- source\n- pipeline\n- territory\n- product_ids\n- competitor\n- use_case\n- next_step\n- next_step_due_at\n- decision_date\n- contract_start\n- risk_score\n- health_score\n- win_probability\n- loss_reason\n```\n\n## 4.6 Contract\n\n```text\nContract\n- contract_number\n- account_id\n- contract_type\n- status\n- effective_date\n- start_date\n- end_date\n- renewal_date\n- auto_renew\n- notice_period\n- contract_value\n- arr\n- mrr\n- currency\n- payment_terms\n- governing_region\n- owner_id\n- legal_owner_id\n- commercial_owner_id\n- document_ref\n- obligations\n- renewal_risk\n- compliance_status\n```\n\n## 4.7 Subscription\n\n```text\nSubscription\n- subscription_id\n- account_id\n- product_id\n- plan\n- status\n- start_date\n- end_date\n- renewal_date\n- quantity\n- unit_price\n- mrr\n- arr\n- currency\n- billing_interval\n- trial_status\n- cancellation_date\n- cancellation_reason\n- payment_status\n- usage\n```\n\n## 4.8 Product / Service\n\n```text\nProduct\n- product_name\n- product_code\n- description\n- product_type\n- category\n- lifecycle_status\n- version\n- owner_id\n- product_manager_id\n- engineering_owner_id\n- pricing_model\n- list_price\n- currency\n- active_customers\n- adoption_rate\n- usage_metrics\n- roadmap_status\n```\n\n## 4.9 Order\n\n```text\nOrder\n- order_number\n- account_id\n- order_date\n- status\n- order_type\n- currency\n- subtotal\n- tax\n- discount\n- total\n- payment_status\n- fulfillment_status\n- owner_id\n- product_lines\n- contract_id\n```\n\n## 4.10 Invoice\n\n```text\nInvoice\n- invoice_number\n- account_id\n- contract_id\n- subscription_id\n- invoice_date\n- due_date\n- currency\n- subtotal\n- tax\n- discount\n- total\n- balance_due\n- payment_status\n- collection_status\n- paid_at\n- aging_days\n- payment_method\n```\n\n## 4.11 Ticket / Case / Incident\n\n```text\nTicket\n- ticket_number\n- account_id\n- contact_id\n- subject\n- description_ref\n- type\n- status\n- priority\n- severity\n- category\n- subcategory\n- channel\n- created_at\n- first_response_at\n- resolution_at\n- sla_target\n- sla_due_at\n- sla_status\n- assigned_to\n- team\n- escalation_status\n- escalation_reason\n- related_product_id\n- related_feature_id\n- root_cause\n- customer_impact\n- sentiment\n- resolution\n```\n\n## 4.12 Meeting / Interaction\n\n```text\nInteraction\n- interaction_type\n- subject\n- start_at\n- end_at\n- duration\n- participants\n- account_id\n- opportunity_id\n- ticket_id\n- project_id\n- owner_id\n- channel\n- summary_ref\n- decisions\n- commitments\n- action_items\n- sentiment\n- follow_up_due_at\n- source_reference\n```\n\n## 4.13 Task / Work Item\n\n```text\nTask\n- title\n- description\n- status\n- priority\n- owner_id\n- assignee_id\n- creator_id\n- due_at\n- completed_at\n- parent_work_id\n- related_entity_type\n- related_entity_id\n- dependency_ids\n- blocker_ids\n- effort\n- estimate\n- actual_effort\n- next_action\n```\n\n## 4.14 Project\n\n```text\nProject\n- project_name\n- project_code\n- status\n- lifecycle_stage\n- owner_id\n- sponsor_id\n- team_id\n- start_date\n- target_date\n- completed_date\n- budget\n- currency\n- actual_cost\n- progress_percent\n- health_score\n- risk_score\n- objectives\n- dependencies\n- blockers\n```\n\n## 4.15 Campaign\n\n```text\nCampaign\n- campaign_name\n- campaign_type\n- status\n- start_date\n- end_date\n- owner_id\n- budget\n- spend\n- currency\n- audience\n- channel\n- source\n- leads_generated\n- opportunities_generated\n- pipeline_generated\n- revenue_attributed\n- impressions\n- clicks\n- conversions\n- cac\n- roi\n```\n\n## 4.16 Employee\n\n```text\nEmployee\n- employee_id\n- person_id\n- employment_status\n- employment_type\n- title\n- department\n- manager_id\n- location\n- timezone\n- start_date\n- end_date\n- cost_center\n- role\n- permissions_ref\n- skills\n- capacity\n```\n\n## 4.17 Feature / Product Work\n\n```text\nFeature\n- feature_name\n- description\n- product_id\n- status\n- priority\n- product_owner_id\n- engineering_owner_id\n- target_release_id\n- target_date\n- business_value\n- customer_value\n- effort_estimate\n- dependency_ids\n- risk_score\n- adoption_target\n```\n\n## 4.18 Bug / Engineering Issue\n\n```text\nEngineeringIssue\n- issue_key\n- title\n- type\n- status\n- priority\n- severity\n- repository\n- project_id\n- feature_id\n- assignee_id\n- reporter_id\n- created_at\n- resolved_at\n- release_id\n- customer_impact\n- root_cause\n- environment\n```\n\n## 4.19 Release / Deployment\n\n```text\nRelease\n- release_id\n- version\n- product_id\n- status\n- planned_at\n- deployed_at\n- environment\n- owner_id\n- change_summary\n- feature_ids\n- issue_ids\n- deployment_id\n- rollback_available\n- deployment_health\n- incident_count\n```\n\n## 4.20 Knowledge / Document\n\n```text\nKnowledgeRecord\n- title\n- document_type\n- source_system\n- source_record_id\n- author_id\n- owner_id\n- created_at\n- modified_at\n- effective_date\n- expiry_date\n- classification\n- content_ref\n- chunk_refs\n- embedding_ref\n- linked_entity_ids\n- linked_work_ids\n- evidence_status\n- promotion_status\n```\n\n---\n\n# 5. Domain Coverage\n\nThe Spine is domain-neutral, but projections are domain-aware.\n\n| Domain | Primary entities | Representative business fields |\n|---|---|---|\n| Executive | Organization, Goal, KPI, Risk, Decision | mission, objectives, targets, actuals, variance, strategic priority, owner |\n| Sales | Lead, Contact, Account, Opportunity, Quote, Contract | stage, amount, probability, close date, owner, next step, forecast |\n| RevOps | Funnel, Pipeline, Forecast, KPI | conversion rates, velocity, coverage, win rate, CAC, ARR, MRR |\n| Customer Success | Account, Subscription, Renewal, Health | health, adoption, renewal date, NRR, risk, success plan |\n| Support | Ticket, Incident, SLA, Account | severity, priority, SLA, backlog, resolution time, escalation |\n| Marketing | Campaign, Lead, Attribution, Content | spend, leads, pipeline, conversion, CAC, ROI, channel |\n| Finance | Invoice, Payment, Subscription, Budget | revenue, MRR, ARR, AR, DSO, cash, burn, runway, variance |\n| Operations | Process, Task, SLA, Workflow | owner, state, cycle time, SLA, throughput, exceptions |\n| Product | Product, Feature, Roadmap, Release | status, value, adoption, roadmap, dependencies, target date |\n| Engineering | Repository, Issue, PR, Release, Deployment | velocity, cycle time, deployment frequency, change failure |\n| People | Employee, Team, Position | headcount, role, manager, capacity, location, employment status |\n| Legal | Contract, Obligation, Policy, Matter | term, renewal, obligation, status, risk, owner |\n| Platform/Admin | Tenant, Connection, Capability, Policy, Audit | health, scopes, grants, schema, policy, audit, lifecycle |\n\nThis domain matrix is a **projection map**, not separate disconnected schemas.\n\n---\n\n# 6. KPI Contract\n\nKPI is a first-class Spine object.\n\n## 6.1 KPI fields\n\n```text\nKPI\n- kpi_id\n- tenant_id\n- domain\n- metric_name\n- metric_key\n- description\n- entity_type\n- entity_id\n- dimension_set\n- value\n- normalized_value\n- unit\n- currency\n- aggregation\n- formula\n- numerator\n- denominator\n- period\n- period_start\n- period_end\n- comparison_period\n- target\n- target_type\n- threshold\n- lower_threshold\n- upper_threshold\n- variance\n- variance_percent\n- trend\n- direction\n- status\n- confidence\n- freshness_at\n- source_systems\n- source_record_refs\n- attribution\n- owner_id\n- audience\n- visibility_scope\n- alert_policy\n- evidence_refs\n```\n\n## 6.2 Enterprise KPI families\n\n### Executive\n`ARR`, `MRR`, `NRR`, `GRR`, `Revenue`, `Gross Margin`, `Burn`, `Runway`, `Cash`, `Pipeline`, `Forecast`, `Customer Count`, `Churn`, `Strategic Goal Attainment`.\n\n### Sales\n`Pipeline Value`, `Pipeline Coverage`, `Win Rate`, `Conversion Rate`, `Average Deal Size`, `Sales Cycle`, `Quota Attainment`, `Forecast Accuracy`, `Stage Aging`.\n\n### RevOps\n`Lead-to-Opportunity`, `Opportunity-to-Win`, `Funnel Velocity`, `Pipeline Coverage`, `CAC`, `LTV`, `ARR Growth`, `Expansion`, `Contraction`, `Churn`.\n\n### Customer Success\n`Health Score`, `Renewal Rate`, `NRR`, `GRR`, `Adoption`, `Usage`, `Time-to-Value`, `Open Risks`, `Renewal Coverage`, `NPS`, `CSAT`.\n\n### Support\n`Ticket Volume`, `Backlog`, `First Response Time`, `Resolution Time`, `SLA Compliance`, `Escalation Rate`, `Reopen Rate`, `CSAT`, `Incident Frequency`.\n\n### Marketing\n`Spend`, `Leads`, `MQL`, `SQL`, `Pipeline`, `Revenue`, `CAC`, `Conversion Rate`, `CTR`, `CPL`, `ROI`, `ROAS`.\n\n### Finance\n`Revenue`, `MRR`, `ARR`, `AR`, `DSO`, `Cash`, `Burn`, `Runway`, `Gross Margin`, `Budget Variance`, `Invoice Aging`, `Collections`.\n\n### Operations\n`Throughput`, `Cycle Time`, `SLA`, `Exception Rate`, `Backlog`, `Automation Rate`, `Workflow Success`.\n\n### Product\n`Feature Adoption`, `Activation`, `Retention`, `Usage`, `Roadmap Attainment`, `Release Frequency`, `Customer Impact`.\n\n### Engineering\n`Deployment Frequency`, `Lead Time`, `Change Failure Rate`, `MTTR`, `Cycle Time`, `PR Throughput`, `Issue Aging`, `Incident Rate`.\n\n### People\n`Headcount`, `Hiring Plan`, `Time-to-Hire`, `Attrition`, `Capacity`, `Utilization`, `Open Roles`.\n\n### Legal\n`Open Matters`, `Contract Cycle Time`, `Renewals`, `Obligation Status`, `Compliance Exceptions`, `Risk`.\n\n### Platform\n`Connector Health`, `Sync Success`, `Freshness`, `Queue Depth`, `Pipeline Failures`, `Capability Availability`, `Execution Success`, `Verification Success`, `Reconciliation Exceptions`, `Governance Approval Time`.\n\n---\n\n# 7. Human + AI Interaction Contract\n\nThe 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**.\n\nEvery projected entity should therefore support:\n\n```text\nInteractionMetadata\n- readable\n- searchable\n- explainable\n- actionable\n- editable\n- approvable\n- delegable\n- shareable\n- subscribable\n- watchable\n- related_entities\n- available_capabilities\n- required_authority\n- approval_required\n- risk_level\n- evidence_required\n- freshness\n- provenance\n- next_best_work\n```\n\n## 7.1 Human-facing fields\n\n```text\ndisplay_name\nsummary\nstatus\nowner\npriority\ndeadline\nhealth\nrisk\nnext_action\nrelated_work\nrecent_activity\nevidence\nsource_links\navailable_actions\napproval_state\n```\n\n## 7.2 AI-facing fields\n\n```text\nentity_identity\nsemantic_type\nbusiness_role\nrelationships\ncurrent_state\nhistorical_state\nsignals\ngoals\nconstraints\nauthority\navailable_capabilities\nrequired_evidence\nfreshness\nprovenance\nconfidence\nwork_context\ncontinuity_context\npolicy_context\n```\n\nAI-facing metadata is context, not permission. Governance remains authoritative.\n\n---\n\n# 8. Work as the Human-AI Coordination Object\n\n`Work` is not merely a task.\n\n```text\nWork\n- work_id\n- tenant_id\n- work_type\n- title\n- objective\n- status\n- priority\n- owner_id\n- initiator\n- human_participants\n- ai_participants\n- assigned_agent_ids\n- related_entity_ids\n- related_kpi_ids\n- context_contract\n- authority_context\n- evidence_refs\n- decision_refs\n- commitment_refs\n- dependency_ids\n- blocker_ids\n- next_action\n- due_at\n- handoff_state\n- current_holder\n- previous_holder\n- continuity_thread_id\n- proposal_refs\n- execution_plan_refs\n- outcome_refs\n- verification_state\n- reconciliation_state\n- last_context_at\n- updated_at\n```\n\nThe governing rule is:\n\n> **No participating worker begins meaningful work without a Spine-derived authorized context and Work identity.**\n\nThis is the bridge between Human Workbench and AI Workbench.\n\n---\n\n# 9. Signal Contract\n\nSignals are derived operational observations.\n\n```text\nSignal\n- signal_id\n- signal_type\n- domain\n- entity_type\n- entity_id\n- severity\n- priority\n- observed_at\n- detected_at\n- metric_refs\n- source_refs\n- evidence_refs\n- baseline\n- current_value\n- delta\n- delta_percent\n- threshold\n- direction\n- confidence\n- impact\n- recommended_work\n- capability_refs\n- owner_id\n- status\n- acknowledged_by\n- resolved_at\n```\n\nExamples:\n\n```text\nrenewal_risk\npipeline_drop\nsupport_spike\nsla_breach\ncash_runway_change\nusage_decline\ndeployment_regression\ncampaign_underperformance\ncontract_renewal_due\nsecurity_or_compliance_exception\n```\n\nA signal is not truth by itself. It points to evidence and may initiate Work.\n\n---\n\n# 10. Decision and Commitment Continuity\n\n## Decision\n\n```text\nDecision\n- decision_id\n- title\n- question\n- decision\n- rationale\n- alternatives\n- decided_by\n- authority_basis\n- decided_at\n- effective_at\n- affected_entity_ids\n- evidence_refs\n- work_id\n- supersedes_decision_id\n- status\n```\n\n## Commitment\n\n```text\nCommitment\n- commitment_id\n- statement\n- committed_by\n- committed_to\n- due_at\n- status\n- related_entity_ids\n- source_interaction_id\n- evidence_refs\n- owner_id\n- fulfillment_at\n- verification_state\n```\n\nThese become organizational continuity only through the applicable promotion/governance boundary.\n\n---\n\n# 11. Connector → Spine Mapping Contract\n\nThis is the missing logical layer between connectors and the canonical schema.\n\n```text\nSOURCE PROVIDER\n      ↓\nSOURCE OBJECT\n      ↓\nSOURCE FIELD\n      ↓\nMAPPING RULE\n      ↓\nCANONICAL ENTITY\n      ↓\nCANONICAL FIELD\n      ↓\nTRANSFORMATION\n      ↓\nIDENTITY / RELATIONSHIP RESOLUTION\n      ↓\nPROVENANCE + EVIDENCE\n      ↓\nPROMOTION / GOVERNANCE\n      ↓\nCANONICAL WRITE\n      ↓\nEVENT / INVALIDATION\n      ↓\nPROJECTION\n```\n\n## 11.1 Mapping record\n\n```text\nFieldMapping\n- mapping_id\n- connector_id\n- provider\n- provider_object\n- provider_field\n- source_path\n- canonical_entity\n- canonical_field\n- data_type\n- transformation\n- normalization_rule\n- identity_key\n- relationship_rule\n- null_policy\n- conflict_policy\n- source_precedence\n- sensitivity\n- write_mode\n- sync_direction\n- version\n- effective_at\n- status\n- test_status\n- provenance_rule\n- evidence_rule\n```\n\n## 11.2 Example\n\n```text\nSalesforce.Account.Name\n        ↓\nAccount.account_name\n\nSalesforce.Account.Industry\n        ↓\nAccount.industry\n\nSalesforce.Account.AnnualRevenue\n        ↓\nAccount.annual_revenue\n\nSalesforce.Opportunity.Amount\n        ↓\nOpportunity.amount\n\nZendesk.Ticket.Status\n        ↓\nTicket.status\n\nStripe.Customer.id\n        ↓\nAccount.external_ids.stripe_customer_id\n\nGitHub.Issue.number\n        ↓\nEngineeringIssue.external_ids.github_issue_number\n\nGoogle Calendar event\n        ↓\nInteraction\n```\n\nA provider never defines the Spine schema. The provider contributes data to the Spine contract.\n\n---\n\n# 12. Connector Category → Canonical Domain Coverage\n\n| Connector category | Typical systems | Primary Spine contributions |\n|---|---|---|\n| CRM | Salesforce, HubSpot, Dynamics | Account, Person, Lead, Opportunity, Activity |\n| ERP | NetSuite, SAP, Dynamics | Customer, Vendor, Product, Order, Invoice, Inventory |\n| Finance/Billing | Stripe, QuickBooks, Xero, Chargebee | Customer, Subscription, Invoice, Payment, Revenue |\n| Support | Zendesk, Freshdesk, Intercom | Ticket, SLA, Incident, Interaction, Customer Health |\n| Communication | Gmail, Outlook, Slack, Teams, Zoom | Interaction, Commitment, Decision, Evidence |\n| Calendar | Google Calendar, Microsoft Calendar | Meeting, Interaction, Task, Commitment |\n| Productivity | Notion, Confluence, Drive, OneDrive, Dropbox | Knowledge, Document, Project, Evidence |\n| Project/Product | Jira, Linear, GitHub | Project, Feature, EngineeringIssue, Release |\n| Marketing | HubSpot, Mailchimp, GA4, LinkedIn Ads, Meta | Campaign, Lead, Attribution, KPI |\n| HRIS | Workday, BambooHR, Greenhouse, Deel, Gusto | Employee, Team, Position, Capacity |\n| Legal | DocuSign, Ironclad, Drive, Notion | Contract, Obligation, Policy, Matter |\n| Infrastructure | Cloudflare, Vercel, AWS, Azure, GCP | Service, Deployment, Incident, Platform KPI |\n| AI | OpenAI, Anthropic, Gemini, other providers | Model execution, AI runtime metrics, proposals, AI continuity metadata |\n| Identity | Descope, Entra ID, Google, GitHub | Identity, principal, grants, consent, authority |\n\n---\n\n# 13. Source Precedence and Conflict Resolution\n\nWhen multiple connectors contribute the same canonical field:\n\n```text\n1. Explicit tenant source-of-authority rule\n2. Entity-specific source precedence\n3. Freshness / effective-date policy\n4. Verified provider state\n5. Reconciliation result\n6. Conflict → unresolved state + evidence\n```\n\nNever silently overwrite conflicting business truth.\n\nThe Spine should preserve:\n\n```text\ncurrent canonical value\n+\nsource contributors\n+\nsource timestamps\n+\nconflict state\n+\nresolution decision\n```\n\n---\n\n# 14. Four Flows\n\n## Flow A — Structured operational data\n\n```text\nProvider\n→ Gateway / Loader\n→ Normalizer\n→ Identity + relationship resolution\n→ Mapping\n→ Promotion\n→ Governed Spine Writer\n→ Canonical Business Context\n→ Event / invalidation\n→ Projection\n```\n\n## Flow B — Unstructured business context\n\n```text\nEmail / document / message / artifact\n→ Loader\n→ Normalizer\n→ reference/chunk/evidence\n→ mapping\n→ promotion\n→ Knowledge / Evidence / Spine\n```\n\n## Flow C — AI continuity\n\n```text\nauthorized AI/chat reference\n→ Brainstorming / AI context\n→ Triage\n→ compare / dedupe / consolidate\n→ candidate\n→ governance\n→ bounded context / AI continuity\n```\n\nFlow C does not become canonical organizational truth merely because an AI generated it.\n\n## Flow D — platform binding\n\n```text\nIdentity\n→ tenant\n→ consent\n→ connection\n→ policy\n→ capability grants\n→ activation\n→ compiled runtime binding\n```\n\n---\n\n# 15. Canonical Write Rule\n\n```text\nSource\n→ Ingest\n→ Normalize / Triage\n→ Provenance\n→ Promotion decision\n→ Governed Writer\n→ Canonical commit\n→ Outbox/event\n→ Projection invalidation\n→ Rehydrate\n```\n\nNo direct agent canonical writes.\n\nNo provider success treated as final truth.\n\nNo cache treated as truth.\n\n---\n\n# 16. Capability Contract\n\nA capability is the semantic bridge from business intent to execution.\n\n```text\nCapability\n- capability_id\n- name\n- version\n- category\n- description\n- input_schema\n- output_schema\n- target_entity_types\n- supported_domains\n- route_types\n- provider_routes\n- connector_dependencies\n- authority_scope\n- risk_level\n- execution_mode\n- approval_required\n- idempotency_policy\n- evidence_requirements\n- timeout\n- retry_policy\n- compensation_policy\n- verification_policy\n- health\n- availability\n- owner\n- audit_policy\n```\n\nCapability categories:\n\n```text\nREAD\nSEARCH\nANALYZE\nCREATE\nUPDATE\nCOMMUNICATE\nSCHEDULE\nASSIGN\nAPPROVE\nEXECUTE\nSYNC\nVERIFY\nRECONCILE\nREPORT\n```\n\nRoute types can include API connector, MCP, agent-to-agent, workflow, browser, local execution, AI execution or human execution where authorized.\n\n---\n\n# 17. Governance Contract\n\nEvery consequential capability invocation carries:\n\n```text\nprincipal\ntenant\nworkspace\nrole\ndelegation\ncapability\ntarget\nrisk\ndata_classification\npolicy\napproval_requirement\napproval_token\nauthority_expiry\naudit_ref\n```\n\nPossible outcomes:\n\n```text\nALLOW\nDENY\nREQUIRE_APPROVAL\nBOUNDED_DELEGATION\n```\n\n> **Confidence never grants authority.**\n\n---\n\n# 18. Execution and Closure\n\n```text\nIntent\n→ Capability resolution\n→ Governance\n→ Approval if required\n→ Hermes\n→ Provider/API/MCP/Agent/Workflow\n→ Outcome\n→ Re-ingestion\n→ Verification\n→ Reconciliation\n→ Canonical update\n→ Memory/knowledge/continuity update\n→ Projection refresh\n→ Human + AI rehydration\n→ Next Work\n```\n\nAn `Outcome Event` is observed provider output, not automatically verified business truth.\n\n---\n\n# 19. Continuity Run\n\nA Continuity Run is the traceable lifecycle of work.\n\n```text\nContinuityRun\n- run_id\n- work_id\n- initiating_principal\n- context_snapshot_ref\n- intent\n- capability_id\n- governance_decision\n- approval_ref\n- execution_plan_ref\n- provider_route\n- execution_id\n- outcome_ref\n- verification_ref\n- reconciliation_ref\n- resulting_entity_refs\n- memory_refs\n- projection_refs\n- started_at\n- completed_at\n- status\n- failure_reason\n```\n\nThis allows the organization to reconstruct:\n\n> 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.\n\n---\n\n# 20. Customer Zero Schema Coverage\n\nCustomer Zero should exercise the full logical model across:\n\n```text\nExecutive\nSales\nRevOps\nCustomer Success\nSupport\nMarketing\nFinance\nOperations\nProduct\nEngineering\nPeople\nLegal\nPlatform/Admin\n```\n\nRepresentative connected applications from the project model include CRM, finance, product/engineering, marketing, support, communication, documentation and infrastructure systems.\n\nThe Customer Zero gate is not “all connectors installed.”\n\nIt is:\n\n```text\nconnector\n→ mapping\n→ hydration\n→ canonical field population\n→ relationship resolution\n→ KPI activation\n→ signal activation\n→ Work projection\n→ human interaction\n→ AI context\n→ governed capability\n→ execution\n→ outcome\n→ verification\n→ reconciliation\n→ continuity\n→ rehydration\n```\n\n---\n\n# 21. Completeness Invariant\n\nA connector is not considered integrated merely because OAuth succeeds.\n\nFor every activated connector/object, the system must be able to answer:\n\n1. What business domain does it contribute to?\n2. What canonical entity does each important object map to?\n3. What canonical fields are populated?\n4. What relationships are created?\n5. What KPIs become available?\n6. What signals become detectable?\n7. What evidence is retained?\n8. What capabilities become executable?\n9. What authority is required?\n10. What human actions are exposed?\n11. What AI context becomes available?\n12. What continuity is retained?\n13. How is the provider outcome verified and reconciled?\n14. What happens when the connector is revoked or unavailable?\n\nThis is the **Connector → Schema → Context → Capability → Continuity** contract.\n\n---\n\n# 22. Canonical Repository Placement\n\nThis document should be represented by the canonical repository structure:\n\n```text\ndocs/canonical/\n  00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md\n  01-PRODUCT-AND-EXPERIENCE.md\n  02-BUSINESS-CONTEXT-SPINE.md\n  03-HUMAN-WORKBENCH-AND-PERSONAL-MEMORY.md\n  04-AI-WORKBENCH-TWIN-AGENTS-AND-AI-MEMORY.md\n  05-WORK-CONTINUITY-AND-HANDOFF.md\n  06-IDENTITY-CONFIG-INTEGRATION-DISCOVERY-ACTIVATION.md\n  07-INGESTION-FOUR-FLOWS-AND-GOVERNED-WRITES.md\n  08-PROJECTION-UI-AND-CONTEXT-COMPOSITION.md\n  09-CAPABILITY-FABRIC-AND-ADK.md\n  10-GOVERNANCE-AUTHORITY-AND-APPROVAL.md\n  11-HERMES-EXECUTION-AND-PROVIDERS.md\n  12-SYNC-VERIFICATION-RECONCILIATION.md\n  13-MEMORY-KNOWLEDGE-EVIDENCE-AND-PRIVACY.md\n  14-MCP-CONTINUITY-BRIDGE-MARKETPLACE-SDK.md\n  15-SECURITY-TENANCY-AUDIT-OBSERVABILITY.md\n  16-ONBOARDING-CUSTOMER-ZERO-AND-GO-LIVE.md\n  17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md\n  18-CANONICAL-GLOSSARY.md\n  contracts/\n  adr/\n  archive/\n```\n\n`02-BUSINESS-CONTEXT-SPINE.md` owns the logical schema. Connector-specific documents may extend mappings but may not redefine canonical business entities.\n\n---\n\n# 23. Final Mental Model\n\n```text\n                    BUSINESS GOALS\n               Mission · Objectives · KPIs\n                         │\n                         ▼\n              BUSINESS CONTEXT SPINE\n                         │\n       ┌─────────────────┼──────────────────┐\n       │                 │                  │\n       ▼                 ▼                  ▼\n   HUMAN WORK        AI WORK             KNOWLEDGE\n       │                 │                  │\n       └────────────── WORK ────────────────┘\n                         │\n                 CAPABILITY FABRIC\n                         │\n                    GOVERNANCE\n                         │\n                      HERMES\n                         │\n                 EXTERNAL SYSTEMS\n                         │\n              OUTCOME / EVIDENCE\n                         │\n            VERIFY → RECONCILE\n                         │\n                         ▼\n               SPINE CANONICAL STATE\n                         │\n                         ▼\n                 REHYDRATE BOTH\n                         │\n                    NEXT WORK\n```\n\nThe missing logical piece is therefore explicitly closed:\n\n> **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.**\n"}