{"slug":"canonical/02-BUSINESS-CONTEXT-SPINE-6.1","title":"Business Context Spine 6.1","section":"canonical","sectionLabel":"Canon","status":"canon","type":"document","path":"canonical/02-BUSINESS-CONTEXT-SPINE-6.1.md","bytes":12036,"description":"Universal tenant spine schema, multi-engine persistence, and operational truth model.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## Complete Logical Schema, SSOT and Connector Mapping Contract\n\n**Status:** Canonical downstream schema specification  \n**Parent authority:** SpineWorkspace Founder Canon, 31 August 2026\n\n## Purpose\n\nThis document is the logical contract for the Business Context Spine. It answers the previously ambiguous question:\n\n> **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?**\n\n### Core chain\n\n```text\nConnector\n→ Provider Object\n→ Provider Field\n→ Mapping\n→ Canonical Object\n→ Canonical Field\n→ Relationship\n→ KPI / Signal\n→ Projection\n→ Human + AI Work\n→ Capability\n→ Governance\n→ Execution\n→ Outcome\n→ Verify\n→ Reconcile\n→ Canonical State\n→ Continuity\n```\n\n---\n\n# A. Logical Spine Layers\n\n| Layer | Meaning | Canonical examples |\n|---|---|---|\n| 1. Identity & Authority | Who/where/under whose authority | tenant, workspace, principal, role, grants |\n| 2. Business Entities | What the organization operates | accounts, people, opportunities, contracts, tickets |\n| 3. Relationships | How entities connect | account-contact, account-opportunity, feature-release |\n| 4. Operational State | Current business state | status, stage, health, risk, SLA, owner |\n| 5. KPI & Signals | Measurement and detected change | ARR, pipeline, churn risk, SLA breach |\n| 6. Work & Continuity | Human/AI coordination | Work, decisions, commitments, handoffs |\n| 7. Knowledge & Evidence | Supporting information | documents, conversations, source links |\n| 8. Derived Context | Authorized runtime representation | Human projection, AI context, Work context |\n\nThese are logical layers; physical storage can differ.\n\n---\n\n# B. Universal Field Groups\n\nEvery business object is composed from these reusable field groups.\n\n## Identity\n\n`id`, `tenant_id`, `workspace_id`, `entity_type`, `external_ids`, `source_record_refs`\n\n## Lifecycle\n\n`status`, `lifecycle_stage`, `created_at`, `updated_at`, `first_seen_at`, `last_seen_at`, `deleted_at`\n\n## Ownership\n\n`owner_id`, `team_id`, `department`, `role`, `responsible_principal`\n\n## Commercial\n\n`currency`, `amount`, `contract_value`, `arr`, `mrr`, `price`, `quantity`, `payment_status`\n\n## Time\n\n`start_date`, `end_date`, `due_at`, `renewal_date`, `effective_date`, `period_start`, `period_end`\n\n## Health / Risk\n\n`health_score`, `risk_score`, `priority`, `severity`, `confidence`, `trend`, `impact`\n\n## Relationships\n\n`parent_id`, `account_id`, `contact_id`, `related_entity_ids`, `dependency_ids`, `blocker_ids`\n\n## Evidence\n\n`source_links`, `source_record_refs`, `evidence_refs`, `provenance`, `freshness_at`\n\n## Interaction\n\n`available_capabilities`, `approval_required`, `required_authority`, `next_action`, `next_best_work`, `watchable`, `shareable`\n\n## Governance\n\n`visibility_scope`, `classification`, `policy_refs`, `authority_context`, `audit_ref`\n\n---\n\n# C. Canonical Object Inventory\n\nThe canonical business object set is:\n\n```text\nOrganization\nAccount\nPerson\nLead\nOpportunity\nContract\nSubscription\nProduct\nOrder\nInvoice\nPayment\nTicket\nIncident\nInteraction\nMeeting\nTask\nWork\nProject\nCampaign\nEmployee\nTeam\nFeature\nEngineeringIssue\nRepository\nRelease\nDeployment\nGoal\nDecision\nCommitment\nKPI\nSignal\nKnowledgeRecord\nEvidenceRecord\nPolicy\nApproval\nExecutionPlan\nOutcomeEvent\nContinuityRun\nConnectionBinding\nCapability\n```\n\nConnector-specific provider objects remain provider objects until mapped into these canonical objects or retained as source evidence.\n\n---\n\n# D. Business Domain Coverage\n\n## Executive\n\n**Objects:** Organization, Goal, KPI, Risk, Decision, Work.\n\n**Fields:**\n\n`mission`, `objective`, `strategic_priority`, `target`, `actual`, `variance`, `owner_id`, `deadline`, `risk`, `dependencies`, `decision`, `rationale`.\n\n## Sales\n\n**Objects:** Lead, Person, Account, Opportunity, Contract, Interaction.\n\n**Fields:**\n\n`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`.\n\n## RevOps\n\n**Objects:** Funnel, Opportunity, KPI, Forecast, Account, Subscription.\n\n**Fields:**\n\n`pipeline_value`, `pipeline_coverage`, `stage_conversion`, `velocity`, `win_rate`, `quota`, `quota_attainment`, `forecast`, `forecast_accuracy`, `cac`, `ltv`, `arr`, `mrr`, `expansion`, `contraction`, `churn`.\n\n## Customer Success\n\n**Objects:** Account, Subscription, Contract, Renewal/Work, Interaction, Ticket, KPI.\n\n**Fields:**\n\n`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`.\n\n## Support\n\n**Objects:** Ticket, Incident, SLA, Account, Interaction.\n\n**Fields:**\n\n`severity`, `priority`, `category`, `sla_target`, `sla_due_at`, `sla_status`, `first_response_at`, `resolution_at`, `backlog_state`, `escalation_status`, `customer_impact`, `root_cause`, `sentiment`.\n\n## Marketing\n\n**Objects:** Campaign, Lead, Person, Attribution, KPI, Content.\n\n**Fields:**\n\n`budget`, `spend`, `channel`, `audience`, `leads_generated`, `mql`, `sql`, `opportunities_generated`, `pipeline_generated`, `revenue_attributed`, `impressions`, `clicks`, `conversions`, `cpl`, `cac`, `roi`, `roas`.\n\n## Finance\n\n**Objects:** Invoice, Payment, Subscription, Contract, Order, KPI, Budget.\n\n**Fields:**\n\n`invoice_date`, `due_date`, `balance_due`, `payment_status`, `aging_days`, `revenue`, `mrr`, `arr`, `gross_margin`, `cash`, `burn`, `runway`, `dso`, `budget`, `actual`, `variance`.\n\n## Operations\n\n**Objects:** Process, Task, Workflow, SLA, Project, KPI.\n\n**Fields:**\n\n`process_name`, `owner_id`, `status`, `cycle_time`, `throughput`, `sla`, `exception_rate`, `backlog`, `automation_rate`, `dependencies`, `blockers`.\n\n## Product\n\n**Objects:** Product, Feature, Goal, Roadmap, Release, KPI.\n\n**Fields:**\n\n`business_value`, `customer_value`, `priority`, `target_date`, `adoption_target`, `adoption_actual`, `status`, `dependency_ids`, `risk_score`, `roadmap_status`.\n\n## Engineering\n\n**Objects:** Repository, EngineeringIssue, Project, Release, Deployment, Incident, KPI.\n\n**Fields:**\n\n`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`.\n\n## People\n\n**Objects:** Employee, Team, Position, Goal, Work.\n\n**Fields:**\n\n`employment_status`, `employment_type`, `title`, `department`, `manager_id`, `location`, `capacity`, `skills`, `cost_center`, `start_date`, `end_date`, `open_role`.\n\n## Legal\n\n**Objects:** Contract, Obligation, Policy, Matter, Approval.\n\n**Fields:**\n\n`contract_type`, `effective_date`, `end_date`, `renewal_date`, `notice_period`, `obligation`, `compliance_status`, `risk_level`, `legal_owner_id`, `approval_state`.\n\n## Platform / Administration\n\n**Objects:** Tenant, ConnectionBinding, Capability, Policy, Approval, Audit, KPI.\n\n**Fields:**\n\n`provider`, `connection_status`, `scopes`, `consent`, `policy_grants`, `capability_grants`, `primary_route`, `health`, `freshness`, `sync_state`, `reconciliation_state`, `revocation`, `schema_version`.\n\n---\n\n# E. Connector-to-Object Mapping\n\n## CRM\n\n```text\nSalesforce / HubSpot / Dynamics\nAccount       → Account\nContact       → Person\nLead          → Lead\nOpportunity   → Opportunity\nCase          → Ticket\nTask/Event    → Interaction / Task\n```\n\n## ERP / Finance\n\n```text\nCustomer       → Account\nVendor         → Organization / Person\nItem/Product   → Product\nSales Order    → Order\nInvoice        → Invoice\nPayment        → Payment\nSubscription   → Subscription\n```\n\n## Support\n\n```text\nTicket/Case    → Ticket\nIncident       → Incident\nSLA            → SLA\nRequester      → Person\nOrganization   → Account\n```\n\n## Communication\n\n```text\nEmail          → Interaction / EvidenceRecord\nCalendar Event → Meeting / Interaction\nSlack Message  → Interaction / EvidenceRecord\nTeams Message  → Interaction / EvidenceRecord\nZoom Meeting   → Meeting / Interaction\n```\n\n## Productivity / Knowledge\n\n```text\nDocument       → KnowledgeRecord\nPage           → KnowledgeRecord\nComment        → EvidenceRecord\nFolder/space   → Knowledge relationship\n```\n\n## Product / Engineering\n\n```text\nJira Issue     → EngineeringIssue / Feature / Task\nLinear Issue   → EngineeringIssue / Feature / Task\nGitHub Issue   → EngineeringIssue\nPull Request   → Engineering evidence / Task\nRepository     → Repository\nRelease        → Release\nDeployment     → Deployment\n```\n\n## Marketing\n\n```text\nCampaign       → Campaign\nContact        → Person\nLead           → Lead\nAnalytics      → KPI / EvidenceRecord\nAttribution    → KPI attribution\n```\n\n## HR\n\n```text\nWorker         → Employee\nPosition       → Position\nDepartment     → Team / Organization unit\nManager        → Employee relationship\n```\n\n## Infrastructure\n\n```text\nService        → Platform Service\nDeployment     → Deployment\nIncident       → Incident\nMetric         → KPI\nLog/Event      → EvidenceRecord / Signal\n```\n\n---\n\n# F. Field Mapping Example\n\n```yaml\nprovider: salesforce\nobject: Account\nfield: AnnualRevenue\n\ncanonical:\n  entity: Account\n  field: annual_revenue\n  type: money\n\ntransformation:\n  - numeric_normalization\n  - currency_resolution\n\nidentity:\n  key: Salesforce.Account.Id\n\nprovenance:\n  retain_source_record: true\n  retain_source_timestamp: true\n\nwrite:\n  mode: governed_canonical\n  conflict_policy: tenant_precedence\n```\n\nThe mapping layer is versioned and testable.\n\n---\n\n# G. SSOT Rule\n\nThe Spine becomes SSOT for **normalized, governed organizational business context**.\n\nIt is not SSOT for:\n\n- raw provider payloads;\n- provider-specific UI behavior;\n- transient caches;\n- model-generated guesses;\n- unverified execution outcomes;\n- private personal memory;\n- AI working memory.\n\nThose remain in their respective state planes.\n\n---\n\n# H. KPI → Signal → Work\n\n```text\nKPI\n ↓\nThreshold / trend / comparison\n ↓\nSignal\n ↓\nBusiness impact\n ↓\nWork\n ↓\nCapability\n ↓\nGovernance\n ↓\nExecution\n ↓\nOutcome\n ↓\nVerification\n ↓\nReconciliation\n```\n\nExample:\n\n```text\nRenewal KPI\nARR at risk ↑\n       ↓\nrenewal_risk signal\n       ↓\nAccount Work created\n       ↓\nprepare_renewal capability\n       ↓\nGovernance\n       ↓\nTwin prepares renewal brief\n       ↓\nHuman reviews\n       ↓\nsend_followup capability\n       ↓\nHermes\n       ↓\nCRM / Gmail\n       ↓\nOutcome\n       ↓\nRe-ingest\n       ↓\nVerified activity\n       ↓\nAccount timeline / health refreshed\n```\n\n---\n\n# I. Human and AI Projection Fields\n\nThe Projection Engine should be able to derive:\n\n```text\ndisplay_fields\nfilter_fields\nsort_fields\ngroup_fields\nsummary_fields\nkpi_fields\nsignal_fields\nrelationship_fields\nevidence_fields\nwork_fields\naction_fields\napproval_fields\ncontinuity_fields\n```\n\nFor AI:\n\n```text\ncontext_entity\nsemantic_type\nbusiness_role\ncurrent_state\nhistory\nrelationships\nevidence\nfreshness\ngoals\nconstraints\nauthority\ncapabilities\nrisk\npolicy\nwork_id\ncontinuity_refs\n```\n\n---\n\n# J. Completeness Test\n\nFor each connector and object:\n\n```text\n[ ] discovered\n[ ] consented\n[ ] connection bound\n[ ] source object classified\n[ ] fields mapped\n[ ] identity resolved\n[ ] relationships resolved\n[ ] provenance retained\n[ ] initial hydration complete\n[ ] KPI contribution known\n[ ] signal contribution known\n[ ] projection contribution known\n[ ] capability contribution known\n[ ] governance requirements known\n[ ] execution route known\n[ ] outcome re-ingestion tested\n[ ] verification tested\n[ ] reconciliation tested\n[ ] revocation tested\n```\n\nOAuth-only integration is therefore **not** an integration-complete state.\n"}