{"slug":"canonical/adr/ADR-2026-09-04-16-canonical-end-to-end-specification","title":"ADR-2026-09-04-16: Canonical End-to-End Specification","section":"canonical","sectionLabel":"Canon","status":"canon","type":"adr","path":"canonical/adr/ADR-2026-09-04-16-canonical-end-to-end-specification.md","bytes":3938,"description":"Architecture Decision Record formalizing the single continuous operating loop, discovery boundary, SSOT + deep retrieval pattern, 3-tier memory, and closed-loop reconciliation.","updated":"2026-09-04","source":"integratewise/Integratewise-docs-wiki","content":"\n\n## Status\n**APPROVED / FOUNDER-CANONICAL**\n\n## Context\nIntegrateWise previously documented capabilities across separate domain specifications (Spine schema, Projection Engine, Capability Fabric, Hermes execution, Reconciliation). While accurate, describing capabilities in isolation created the risk of fragmented understanding.\n\nThe product needed a single continuous end-to-end architectural specification expressing the entire system as one unbroken continuum:\n> **Humans and AI work toward the same business objective, from their own workbenches, using the same governed business context.**\n\n## Decision\n\n1. **Adopt the 10-Stage Continuous Operating Continuum**:\n   `Discover → Hydrate → Normalize → Classify → Relate → Project → Work → Execute → Reconcile → Grow`.\n   The operating loop is explicitly:\n   `Tools → Spine → Workbench → Human/AI → Tools → Reconciliation → Spine`.\n\n2. **Ecosystem Discovery without Credential Theft**:\n   Authorizing IW Spine Network MCP via an AI host (ChatGPT, Claude) discovers the user's existing tools, MCPs, skills, and context without transferring private OAuth credentials. Live capabilities route through:\n   - The current host (if exposed);\n   - An IntegrateWise-authorized connection; or\n   - Another explicitly authorized capability route.\n\n3. **Prerequisite Flow D & Ingestion Separation (A, B, C)**:\n   - **Flow D**: Identity, authority, permissions, and activation (prerequisite).\n   - **Flow A**: Structured operational SSOT (bulk remains in source systems).\n   - **Flow B**: Business context (emails, Slack, transcripts, documents explaining why).\n   - **Flow C**: Conversational and AI continuity (chat sessions, agent plans, candidate memories).\n\n4. **Account as the Universal B2B Anchor**:\n   Account is the cross-system gravitational center relating CRM deals, support tickets, billing status, usage metrics, communications, and AI sessions.\n\n5. **SSOT + Deep-Source Retrieval Pattern**:\n   Spine maintains the canonical state and external entity IDs. When deep transaction details are required (e.g. specific support ticket transcripts), the Co-worker queries the source system on demand via the Capability Fabric.\n\n6. **Three Memory Classifications**:\n   - **Organizational Memory**: Shared tenant-level truth (accounts, contracts, policies, KPIs).\n   - **User Memory**: Individual working context (preferences, personal drafts, focused views).\n   - **Agentic Memory**: AI operational continuity (plans, working state, candidate memories).\n   Agentic outputs require explicit human approval before being promoted to organizational truth.\n\n7. **Projections as Ephemeral Contracts**:\n   The Workbench never stores independent state. The Projection Engine composes authorized context contracts based on:\n   `Role × Department × Industry × Permissions × Connectors × Context × Account`.\n\n8. **Provider Outcome != Final Truth (Closed-Loop Reconciliation)**:\n   A success response from an external provider (e.g. Salesforce API 200 OK) is only an outcome event. True Spine updates occur only after re-ingestion, verification, and reconciliation against expected state.\n\n9. **The Core Flywheel**:\n   `Know the user → Learn the user → Grow with the user`.\n\n## Consequences\n- Every subsystem operates as an integrated phase of the master flywheel.\n- Eliminates security and compliance risks associated with cross-host credential leakage.\n- Guarantees zero context drift for AI while maintaining 100% human decision authority.\n"}