{"slug":"canonical/04-CANONICAL-END-TO-END-SPECIFICATION","title":"Canonical End-to-End Specification","section":"canonical","sectionLabel":"Canon","status":"canon","type":"document","path":"canonical/04-CANONICAL-END-TO-END-SPECIFICATION.md","bytes":27074,"description":"The complete single-continuous-system architecture of IntegrateWise: Discover → Hydrate → Normalize → Classify → Relate → Project → Work → Execute → Reconcile → Grow.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\nThe architecture is expressed as one continuous system rather than as separate features.\n\nThe governing idea is:\n\n> **Humans and AI work toward the same business objective, from their own workbenches, using the same governed business context.**\n\nThe mechanism is:\n\n> **Discover → Hydrate → Normalize → Classify → Relate → Project → Work → Execute → Reconcile → Grow.**\n\nThis aligns with the current canonical architecture: the Spine is the protected organizational-context core, the Workbench is a projection of that Spine, the Projection Engine composes authorized context contracts, and the Continuity Bridge/MCP boundary exposes the system to external AI/application surfaces.\n\n---\n\n# 1. What IntegrateWise Actually Is\n\nIntegrateWise is **not another CRM, another ETL platform, another AI chatbot, or another collection of connectors**.\n\nThe existing systems remain the systems where operational work happens.\n\nIntegrateWise provides the layer that makes those systems **contextually continuous**.\n\n```text\n                     EXISTING ECOSYSTEM\n\n Salesforce   HubSpot   Zendesk   Jira   Slack   Gmail   Notion\n      │           │        │       │       │       │       │\n      └───────────┴────────┴───────┴───────┴───────┴───────┘\n                              │\n                              ▼\n                         IW SPINE NETWORK\n                              │\n                              ▼\n                             SPINE\n                              │\n                ┌─────────────┼─────────────┐\n                ▼             ▼             ▼\n             Context        Memory      Relationships\n                │             │             │\n                └─────────────┼─────────────┘\n                              ▼\n                     PROJECTION ENGINE\n                              │\n                              ▼\n                         WORKBENCH\n                              │\n                    ┌─────────┴─────────┐\n                    ▼                   ▼\n                  HUMAN               TWIN\n                    │                   │\n                    └─────────┬─────────┘\n                              ▼\n                         DECISION / WORK\n                              │\n                              ▼\n                     GOVERNED EXECUTION\n                              │\n                              ▼\n                     SOURCE SYSTEMS\n                              │\n                              ▼\n                       RECONCILIATION\n                              │\n                              ▼\n                            SPINE\n```\n\nThe canonical operating loop is explicitly:\n\n**Tools → Spine → Workbench → Human/AI → Tools → Reconciliation → Spine.**\n\n---\n\n# 2. The First Principle: Know the User\n\nWhen a user installs or authorizes **IW Spine Network MCP** through an AI host such as ChatGPT, the first objective is **not to start copying data**.\n\nThe first objective is:\n\n> **Understand the user and discover the ecosystem in which that user already works.**\n\nSo the first event is:\n\n```text\nUSER\n  │\n  ▼\nAUTHORIZE IW SPINE NETWORK\n  │\n  ▼\nDISCOVERY\n  │\n  ├── User\n  ├── Tenant\n  ├── Workspace\n  ├── Role\n  ├── Department\n  ├── Connected tools\n  ├── MCPs\n  ├── Plugins\n  ├── Skills\n  ├── Knowledge sources\n  ├── Files\n  └── Existing work/context\n```\n\nThis is the missing bridge between an **AI host** and a **business-context system**.\n\nThe architecture defines host-environment discovery, connector/capability discovery, first-use hydration and initial Twin context as part of onboarding.\n\n---\n\n# 3. Important Boundary: Discovery Does Not Mean Credential Theft\n\nIf ChatGPT has 50 tools, IntegrateWise does **not** receive ChatGPT's private OAuth credentials.\n\nLikewise, if Claude has 50 connected applications, IntegrateWise does not silently acquire Claude's credentials.\n\nThe architecture must distinguish:\n\n```text\nDISCOVERY\n≠\nCREDENTIAL REUSE\n```\n\nThe Spine Network discovers what the host exposes and what is authorized to be discovered.\n\nThe actual live capability can subsequently be reached through:\n\n1. The current host, if that host exposes it;\n2. An IntegrateWise-authorized connection;\n3. Another explicitly authorized capability route.\n\nHost authorization does not automatically transfer OAuth authority between hosts.\n\nTherefore the promise is:\n\n> **Continuity without unnecessary re-authentication—not unauthorized credential sharing.**\n\n---\n\n# 4. Discovery: The User's Existing AI Ecosystem Becomes Visible to Spine\n\nSuppose:\n\n```text\nClaude\n├── Salesforce\n├── HubSpot\n├── Slack\n├── Gmail\n├── Notion\n├── Jira\n├── GitHub\n├── Linear\n├── Zendesk\n└── 40 other tools\n```\n\nThe user should not have to manually register those 50 systems one by one.\n\nThe host discovery process identifies the capabilities available to the user.\n\n```text\nClaude\n  │\n  ▼\nIW Spine Network\n  │\n  ▼\nDiscovery\n  │\n  ├── Tool 1\n  ├── Tool 2\n  ├── Tool 3\n  ├── ...\n  └── Tool 50\n        │\n        ▼\nCapability / Connection Registry\n```\n\nThis does **not** mean all 50 tools become data warehouses inside Spine.\n\nIt means Spine understands:\n\n> **These capabilities exist, they are associated with this user's ecosystem, and here is how authorized work can reach them.**\n\n---\n\n# 5. Then Spine Hydrates\n\nOnce discovery establishes the ecosystem, the system starts building the user's business context.\n\nThere are three primary data flows, with Flow D providing the prerequisite authority and activation layer.\n\n## Flow D — Identity and Authority\n\n```text\nIdentity\nAuthentication\nAuthorization\nConsent\nTenant\nWorkspace\nRole\nPermissions\nConnector eligibility\nIngestion activation\n```\n\nFlow D must exist before A/B/C ingestion.\n\n---\n\n# 6. Flow A — Structural Business Data\n\nThe first data layer is structured operational information.\n\nFor ten connectors:\n\n```text\nConnector 1 → SSOT\nConnector 2 → SSOT\nConnector 3 → SSOT\n...\nConnector 10 → SSOT\n```\n\nExamples:\n\n```text\nAccount\nContact\nOpportunity\nTicket\nSubscription\nInvoice\nUsage\nProject\nTask\nStatus\nOwner\nKPI\n```\n\nBut:\n\n> **IntegrateWise does not copy the entire connector.**\n\nIt extracts the **canonical entities and relationships required for business continuity**.\n\nThe bulk operational data remains in the originating systems.\n\nSo:\n\n```text\nSOURCE SYSTEM\n      │\n      ├──────────────► Operational detail stays here\n      │\n      └──────────────► Relevant SSOT\n                             │\n                             ▼\n                           SPINE\n```\n\n---\n\n# 7. Flow B — Business Context\n\nFlow B captures what happens **around the structured records**.\n\nFor example:\n\n```text\nEmails\nSlack\nDocuments\nTickets\nComments\nMeeting notes\nMeeting transcripts\nTasks\nProjects\nCommitments\nDecisions\n```\n\nThis is what explains the structured state.\n\nFor example:\n\n```text\nCRM:\nRenewal = delayed\n```\n\ndoes not tell you why.\n\nFlow B may contain:\n\n```text\nCustomer email:\n\"We cannot proceed until the issue is fixed.\"\n\nSupport:\nTicket unresolved.\n\nProduct:\nFeature request still pending.\n\nSlack:\nCSM escalating the issue.\n```\n\nTogether:\n\n```text\nSTRUCTURED STATE\n        +\nBUSINESS CONTEXT\n        =\nBUSINESS STORY\n```\n\n---\n\n# 8. Flow C — Conversational / AI Continuity\n\nFlow C captures the continuity created by AI interaction.\n\n```text\nChatGPT conversations\nClaude conversations\nAI sessions\nTwin interactions\nAgent work\nPlans\nProposals\nTool execution context\nGenerated artifacts\nCandidate memories\n```\n\nThis matters because the AI itself becomes part of the user's working history.\n\nFor example:\n\n```text\nUser:\n\"Investigate why ACME renewal is slipping.\"\n\nAI:\n\"Potential causes are support backlog and declining adoption.\"\n\nUser:\n\"Check product usage.\"\n\nAI:\n\"Usage dropped 23%.\"\n\nUser:\n\"Prepare a customer recovery plan.\"\n```\n\nThat sequence itself becomes useful context.\n\nIt should not disappear when the chat session ends.\n\n---\n\n# 9. Processing Before It Becomes Spine Context\n\nA/B/C data is processed through the normalization and knowledge pipeline:\n\n```text\nSource\n  │\n  ▼\nIngestion\n  │\n  ▼\nNormalization\n  │\n  ├── Entity extraction\n  ├── Relationship mapping\n  ├── Metadata\n  ├── Provenance\n  ├── RAG indexing\n  └── Embeddings\n  │\n  ▼\nCanonical Spine\n```\n\nThe Spine is more than a SQL database: it includes operational truth/state, evidence, search, embeddings, relationships, provenance, event history and bounded context projections.\n\n---\n\n# 10. What Actually Lives in the Spine\n\nThe resulting Spine contains the **continuity representation** of the business.\n\nConceptually:\n\n```text\nSPINE\n│\n├── Entities\n├── Relationships\n├── Business state\n├── KPIs\n├── Signals\n├── Communications/context\n├── Knowledge\n├── Memory\n├── Evidence\n├── Provenance\n├── Events\n├── Work\n├── Connections\n├── Capabilities\n├── Continuity\n└── Projection state\n```\n\nThe important distinction is:\n\n> **Spine stores what the organization needs to remember and understand—not a blind copy of every source system.**\n\n---\n\n# 11. Three Memory Classifications\n\nOnce the information enters the continuity layer, it must be classified.\n\n```text\n                         SPINE\n                           │\n              ┌────────────┼────────────┐\n              ▼            ▼            ▼\n       ORGANIZATIONAL    USER        AGENTIC\n          MEMORY       MEMORY        MEMORY\n```\n\n### Organizational\n\nShared tenant-level truth.\n\n```text\nAccounts\nContracts\nPolicies\nFormal decisions\nCompany KPIs\nOrganizational context\n```\n\n### User\n\nThe individual user's working context.\n\n```text\nPersonal preferences\nPrivate working context\nTasks\nPersonal focus\nDrafts\nUser-specific views\n```\n\n### Agentic\n\nAI operational continuity.\n\n```text\nPlans\nAgent work\nProposals\nExecution history\nWorking state\nCandidate memories\n```\n\nThe distinction is critical because AI-generated information cannot automatically become organizational truth without explicit human governance.\n\n---\n\n# 12. The Universal Anchor: Account\n\nFor B2B, the primary cross-system anchor is:\n\n> **Account.**\n\nExample:\n\n```text\nACME\n│\n├── CRM\n├── Support\n├── Billing\n├── Product Usage\n├── Email\n├── Slack\n├── Meetings\n├── Documents\n├── Projects\n└── AI conversations\n```\n\nThe account becomes the gravitational center through which the different systems can be related.\n\n---\n\n# 13. Why Account Changes Everything\n\nConsider:\n\n```text\nSupport ticket unresolved\n        ↓\nFeature request unresolved\n        ↓\nProduct usage declines\n        ↓\nCustomer health declines\n        ↓\nRenewal becomes risky\n        ↓\nPayment is delayed\n```\n\nThe information is distributed across different systems.\n\nThe CSM may only see:\n\n```text\nUsage ↓\n```\n\nThe salesperson may only see:\n\n```text\nPayment delayed\n```\n\nSupport sees:\n\n```text\nTicket open\n```\n\nProduct sees:\n\n```text\nFeature request\n```\n\nThe Spine connects these signals through the account.\n\n---\n\n# 14. Spine Does Not Need to Know Everything\n\nSuppose Spine knows:\n\n```text\nACME\nHubSpot Account ID = 123\nZendesk Account ID = 456\nStripe Customer ID = 789\n```\n\nAnd:\n\n```text\nRenewal = at risk\nUsage = declining\nSupport issue = unresolved\n```\n\nBut the user asks:\n\n> \"What exactly happened in the last three support interactions?\"\n\nSpine doesn't need to contain every Zendesk conversation.\n\nInstead:\n\n```text\nCo-worker\n   │\n   ▼\nSpine\n   │\n   ▼\nACME\n   │\n   ▼\nZendesk connection/capability\n   │\n   ▼\nAccount ID 456\n   │\n   ▼\nRetrieve required detail\n   │\n   ▼\nContext assembly\n```\n\nThat is the **SSOT + deep-source retrieval model**.\n\n---\n\n# 15. MCP's Actual Role\n\nThis makes the role of MCP much clearer.\n\nMCP is not the Spine.\n\nMCP is not the business context.\n\nMCP is not the source of truth.\n\nMCP is a **communication/capability protocol**.\n\n```text\nSPINE\n  │\n  ▼\nCO-WORKER\n  │\n  ▼\nCAPABILITY FABRIC\n  │\n  ▼\nMCP / API / AGENT\n  │\n  ▼\nSOURCE PLATFORM\n```\n\nThe architecture defines MCP as the outward protocol boundary and MCP Pool as the inward registry of approved MCP servers/tools.\n\n---\n\n# 16. The Co-worker's Job\n\nThe Co-worker does not blindly query ten systems.\n\nIt first asks:\n\n> **What do I already know?**\n\nThen:\n\n> **What is missing?**\n\nThen:\n\n> **Where can I obtain that missing information?**\n\nSo:\n\n```text\nUSER QUESTION\n     │\n     ▼\nCO-WORKER\n     │\n     ▼\nREAD SPINE\n     │\n     ▼\nUNDERSTAND ACCOUNT\n     │\n     ▼\nCONTEXT COMPLETE?\n   /          \\\n YES           NO\n │             │\n │             ▼\n │       CAPABILITY FABRIC\n │             │\n │       MCP / API / AGENT\n │             │\n │       SOURCE SYSTEM\n │             │\n │       REQUIRED DETAIL\n │             │\n └───────┬─────┘\n         ▼\n   CONTEXT ASSEMBLY\n         │\n         ▼\n       USER\n```\n\nThis is where the system becomes materially different from a normal RAG application.\n\n---\n\n# 17. Projection\n\nThe Spine contains organizational context.\n\nThe user should **not** receive all of it.\n\nThe Projection Engine composes the authorized view.\n\nThe canonical model defines the Projection Engine as the sole composer of authorized, versioned Workbench/context contracts.\n\nThe projection is determined by:\n\n```text\nRole\n×\nDepartment\n×\nIndustry\n×\nPermissions\n×\nConnectors\n×\nCurrent Context\n×\nAccount\n```\n\n---\n\n# 18. Same Account, Different Projection\n\n### Sales\n\n```text\nACME\n├── Opportunity\n├── Pipeline\n├── Stage\n├── Contacts\n├── Competitors\n├── Pricing\n└── Close date\n```\n\n### CSM\n\n```text\nACME\n├── Health\n├── Usage\n├── Support\n├── SLA\n├── Commitments\n├── Renewal\n└── Risk\n```\n\n### Marketing\n\n```text\nACME\n├── Engagement\n├── Campaigns\n├── Content\n├── Account activity\n└── Attribution\n```\n\nThe account is the same.\n\nThe context is the same underlying organizational reality.\n\nThe **projection is different**.\n\n---\n\n# 19. Connectors Automatically Enrich the Projection\n\nSuppose the tenant has:\n\n```text\nCRM\nSupport\nBilling\nProduct Analytics\nConversation Intelligence\n```\n\nThe projection can expose:\n\n```text\nCRM → pipeline\nSupport → tickets\nBilling → renewal/payment\nProduct → usage\nConversation Intelligence → call signals\n```\n\nIf Gong is added:\n\n```text\nNEW CONNECTOR\n      ↓\nCATEGORY\n      ↓\nDOMAIN EXTENSION\n      ↓\nNEW FIELDS / KPIs\n      ↓\nSPINE SCHEMA VERSION\n      ↓\nPROJECTION UPDATE\n```\n\nThis is **schema growth rather than schema freeze**: a new connector activates a semantic/domain extension, registers fields/KPIs, adjusts the versioned Spine schema and enriches the user projection.\n\n---\n\n# 20. The Workbench\n\nThe Workbench is not another database.\n\nIt is a **projection of the Spine**.\n\n```text\nSPINE\n  │\n  ▼\nPROJECTION ENGINE\n  │\n  ▼\nAUTHORIZED CONTEXT CONTRACT\n  │\n  ▼\nWORKBENCH\n```\n\nThe Workbench can show:\n\n* Accounts\n* Tasks\n* Signals\n* KPIs\n* Communications\n* Documents\n* Timeline\n* Work\n* Approvals\n* Relevant connector capabilities\n* Twin interactions\n\nThese are projections, not independent truth stores.\n\n---\n\n# 21. Then the Human + AI Loop Starts\n\nNow the system has context.\n\nThe user doesn't need to rebuild it.\n\nThe OODA loop becomes:\n\n```text\nOBSERVE\nSpine shows what is happening.\n\n      ↓\n\nORIENT\nCo-worker assembles cross-system context.\n\n      ↓\n\nDECIDE\nHuman determines what matters.\n\n      ↓\n\nACT\nAI prepares/executes the authorized work.\n\n      ↓\n\nRECONCILE\nSystem verifies what actually happened.\n\n      ↓\n\nREMEMBER\nSpine is updated.\n\n      ↓\n\nGROW\nNext cycle starts with more context.\n```\n\n---\n\n# 22. Human Authority Remains Central\n\nAI can:\n\n```text\nSearch\nCorrelate\nAnalyze\nSummarize\nPrepare\nRecommend\nDraft\nCoordinate\nExecute authorized actions\n```\n\nThe human decides:\n\n```text\nIs this the right solution?\nDoes this actually solve the problem?\nIs this appropriate for this customer?\nShould we proceed?\nWhat matters?\n```\n\nTherefore:\n\n> **AI gathers, connects and proposes. Human judges, decides and authorizes.**\n\nThe Spine remembers both sides of the interaction.\n\n---\n\n# 23. Execution\n\nOnce the user approves:\n\n```text\nUSER DECISION\n      │\n      ▼\nPROPOSAL\n      │\n      ▼\nGOVERNANCE\n      │\n      ▼\nAPPROVAL TOKEN\n      │\n      ▼\nHERMES\n      │\n      ▼\nCAPABILITY FABRIC\n      │\n      ▼\nMCP / API / AGENT\n      │\n      ▼\nSOURCE SYSTEM\n```\n\nThe crucial rule is:\n\n> **Provider acceptance is not final truth.**\n\nOutcome capture must be followed by verification/reconciliation before the Spine is treated as updated truth.\n\n---\n\n# 24. Reconciliation\n\nSuppose the Co-worker creates a Salesforce opportunity update.\n\nSalesforce says:\n\n```text\nSUCCESS\n```\n\nThat is only an **Outcome Event**.\n\nThe system then verifies:\n\n```text\nExpected state\n      vs\nActual state\n```\n\nThen:\n\n```text\nEXPECTED\n   ↓\nEXECUTED\n   ↓\nPROVIDER OUTCOME\n   ↓\nRE-INGEST\n   ↓\nVERIFY\n   ↓\nRECONCILE\n   ↓\nCANONICAL SPINE UPDATE\n```\n\nOnly then does the projection refresh.\n\n---\n\n# 25. The Spine Therefore Gets Better Over Time\n\nEvery completed cycle produces additional continuity.\n\n```text\nDAY 1\nDiscovery\n     ↓\nInitial Spine\n\nDAY 2\nNew work\n     ↓\nMore context\n\nDAY 3\nNew execution\n     ↓\nNew outcome\n\nDAY 30\nAccumulated business history\n\nDAY 300\nDeep organizational + user + AI continuity\n```\n\nThe next interaction starts from:\n\n```text\nKNOWN CONTEXT + NEW DELTA\n```\n\nThat is the core value.\n\n---\n\n# 26. The Complete Architecture\n\n```text\n                         AI HOST\n                  ChatGPT / Claude / etc.\n                              │\n                              ▼\n                    IW SPINE NETWORK MCP\n                              │\n                         AUTHORIZATION\n                              │\n                              ▼\n                          DISCOVERY\n                              │\n        ┌─────────────────────┼─────────────────────┐\n        │                     │                     │\n        ▼                     ▼                     ▼\n      USER                ECOSYSTEM              WORK\n   Identity/Role       MCPs/Tools/Plugins     Conversations\n   Tenant/Workspace    Skills/Connections     Files/Activity\n        │                     │                     │\n        └─────────────────────┼─────────────────────┘\n                              ▼\n                           FLOW D\n                 Identity / Authority / Activation\n                              │\n             ┌────────────────┼────────────────┐\n             ▼                ▼                ▼\n          FLOW A            FLOW B            FLOW C\n        Structured         Business          AI /\n           SSOT             Context       Conversations\n             │                │                │\n             └────────────────┼────────────────┘\n                              ▼\n                   NORMALIZATION / RAG /\n                  EMBEDDINGS / PROVENANCE\n                              │\n                              ▼\n                     CANONICAL SPINE\n                              │\n             ┌────────────────┼────────────────┐\n             ▼                ▼                ▼\n       ORGANIZATIONAL       USER            AGENTIC\n          MEMORY           MEMORY           MEMORY\n             │                │                │\n             └────────────────┼────────────────┘\n                              ▼\n                         ACCOUNT MODEL\n                              │\n                              ▼\n                      RELATIONSHIP GRAPH\n                              │\n                              ▼\n                     PROJECTION ENGINE\n                              │\n                 ROLE × DEPT × INDUSTRY\n                 × CONNECTORS × CONTEXT\n                              │\n                              ▼\n                         WORKBENCH\n                              │\n                       USER / TWIN\n                              │\n                              ▼\n                         USER INTENT\n                              │\n                              ▼\n                      CONTEXT ASSEMBLY\n                              │\n                    ┌─────────┴─────────┐\n                    ▼                   ▼\n              SPINE CONTEXT        MISSING DATA\n                    │                   │\n                    │             CAPABILITY FABRIC\n                    │                   │\n                    │          MCP / API / AGENT\n                    │                   │\n                    │             SOURCE SYSTEM\n                    │                   │\n                    └─────────┬─────────┘\n                              ▼\n                       HUMAN DECISION\n                              │\n                              ▼\n                         GOVERNANCE\n                              │\n                              ▼\n                           HERMES\n                              │\n                              ▼\n                          EXECUTION\n                              │\n                              ▼\n                     PROVIDER OUTCOME\n                              │\n                              ▼\n                        RE-INGESTION\n                              │\n                              ▼\n                       RECONCILIATION\n                              │\n                              ▼\n                   VERIFIED SPINE UPDATE\n                              │\n                              ▼\n                     EVIDENCE + AUDIT\n                              │\n                              ▼\n                      MEMORY PROMOTION\n                              │\n                              ▼\n                    LIVE WORKBENCH REFRESH\n                              │\n                              ▼\n                        NEXT WORK CYCLE\n                              │\n                              ▼\n                           GROWTH\n```\n\n---\n\n# 27. The Most Important Conceptual Separation\n\n| Layer                 | Primary responsibility                                   |\n| --------------------- | -------------------------------------------------------- |\n| **Host**              | Where the user/AI is operating                           |\n| **IW Spine Network**  | External access/distribution boundary into IntegrateWise |\n| **Discovery**         | Understand user ecosystem and available capabilities     |\n| **Connectors**        | Reach source systems                                     |\n| **Flow A**            | Structured SSOT                                          |\n| **Flow B**            | Business context                                         |\n| **Flow C**            | AI/conversational continuity                             |\n| **Flow D**            | Identity, authority and activation                       |\n| **Spine**             | Canonical business continuity/context                    |\n| **Account**           | Cross-system business anchor                             |\n| **Projection Engine** | Decide what context the user is authorized to see        |\n| **Workbench**         | Human operating surface                                  |\n| **Twin / Co-worker**  | Contextual intelligence                                  |\n| **Capability Fabric** | Resolve how an authorized capability can be performed    |\n| **MCP**               | Communication/protocol boundary                          |\n| **Governance**        | Authority and approval boundary                          |\n| **Hermes**            | Approved execution lifecycle                             |\n| **Reconciliation**    | Determine whether the intended change actually occurred  |\n\n---\n\n# 28. The Actual Product Flywheel\n\nEverything ultimately reduces to this:\n\n```text\n                  KNOW\n                   │\n                   ▼\n               DISCOVER\n                   │\n                   ▼\n                HYDRATE\n                   │\n                   ▼\n                REMEMBER\n                   │\n                   ▼\n                 LEARN\n                   │\n                   ▼\n                PROJECT\n                   │\n                   ▼\n                  WORK\n                   │\n                   ▼\n                DECIDE\n                   │\n                   ▼\n                EXECUTE\n                   │\n                   ▼\n              RECONCILE\n                   │\n                   ▼\n                 GROW\n                   │\n                   └──────────────► KNOW\n```\n\nOr, in the shortest possible form:\n\n> **Know the user. Learn the user. Grow with the user.**\n\nAnd the technical interpretation is:\n\n> **Discover the user's ecosystem, preserve the business context that matters, project the right context to the right human or AI worker, execute through governed capabilities, reconcile the outcome, and continuously add the resulting knowledge back into the Spine.**\n"}