{"slug":"internal/architecture/ARCHITECTURE_ALIGNMENT_v1.1","title":"Promotion Package — Architecture Alignment v1.1","section":"internal","sectionLabel":"Internal","status":"unclassified","type":"document","path":"internal/architecture/ARCHITECTURE_ALIGNMENT_v1.1.mdx","bytes":4948,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **⚠️ SUPERSEDED (2026-06-12):** This is a dated v1.1 snapshot from 2026-06-09. Its data-layer\n> facts (the legacy SQL fortress and its auth path) are RETIRED by DECISION 22 (100% Cloudflare —\n> single plane, no legacy store). Read it as history only. Current canon:\n> `docs/architecture/PRODUCT_ARCHITECTURE.md`, `docs/architecture/SPINE_MODEL.md`, `AGENTS.md`,\n> and the map in `docs/CANON.md`.\n>\n> **Status:** APPLIED DIRECTLY — authorized by Nirmal (Founder) on 2026-06-09,\n> overriding the Triage-first default for this batch. Founder is the owner of the\n> governance rule and explicitly directed direct application. Manifest update still required.\n> **Date:** 2026-06-09 | **Authority:** Nirmal (Founder)\n> **Source of truth:** `integratewise-live/docs/ARCHITECTURE_INDEX.md`\n\n---\n\n## Why\n\nArchitecture facts drifted across `integratewise-docs` and internal docs. This\npackage freezes the canonical v1.1 facts and lists every change required so the\npublic/governed docs match the source repo.\n\n## Changes to apply (governed docs)\n\n```\n1. TOOL COUNT\n   16 / 18  →  20   (figma.* purged 2026-06-06; D-2026-06-06-008)\n\n2. AUTH MODEL\n   Supabase Auth (PKCE/JWT)  →  Cloudflare Access (Google + GitHub) + Gateway D1 JWT\n   Supabase is fortress DATA record only — never an auth path.\n\n3. DATA TIER\n   Supabase is NOT provisioned at signup. Initial users are D1-edge only.\n   Supabase fortress is ALLOTTED based on usage, not chosen at signup.\n\n4. BRIDGE FRAMING\n   \"MCP\" as the product  →  Continuity Bridge is the product; MCP is one interface inside it.\n\n5. TWIN ACCESS PATH\n   \"Twin reads via MCP\"  →  Twin reads via Continuity Bridge (continuity-tool-server → pipeline).\n   mcp.integratewise.ai is the EXTERNAL door (Claude, ChatGPT, 3rd-party agents).\n\n6. GATEWAY RESPONSIBILITY\n   \"context assembly\"  →  request-context assembly (auth + tenant + policy envelope).\n   Data context is Spine Cache; not the Gateway.\n\n7. ADK CLARIFICATION\n   Stateless · Zero I/O · capability resolution only · no tenant/data access before Gateway auth.\n\n8. SPINE ABSTRACTION (operating model)\n   Tools push to Spine once; agents read from Spine forever; agents never read tools directly.\n   Unconnected app → authorize THROUGH IntegrateWise → data lands in Spine → agent reads Spine.\n   Never agent → direct tool.\n\n9. CANONICAL TAXONOMY (four orthogonal path-series — stop using one L-number)\n   S-series = System Architecture (S0 Infra · S1 Workspace · S2 Awareness · S3 Twin · S4 Library)\n   U-series = Human Operating Model (U1 Work · U2 Notice · U3 Reason · U4 Decide · U5 Act · U6 Remember)\n   V-series = View Path · CZ-series = Customer Zero Path\n   Approval = U4 Decide; UI on S2 Awareness; never in S3 Twin chat.\n   \"L1–L4\" UI table = S1–S4. See docs/tech/CANONICAL_TAXONOMY.md.\n\n10. DOCS PUBLICATION (how docs.integratewise.ai + internal docs are produced)\n   Governed PROJECTION of org_memory via the docs-publish flow\n   (propose → govern → promote → project → publish). integratewise-docs is an\n   OUTPUT repo — never hand-edited. Classification routes the surface:\n   internal → CF Access gated; public → open. INITIAL LOAD ONLY runs on a separate\n   bulk queue (not the live pipeline-process queue); steady-state uses the normal flow.\n   See docs/tech/DOCS_PUBLICATION_PIPELINE.md.\n```\n\n## Target files in integratewise-docs (audit list)\n\n```\ndocs/internal/gtm/positioning-framework.md      (tool count, multi-AI via MCP wording)\ndocs/internal/operations/sync-spec.md           (Signup → Supabase Auth → ... )\ndocs/internal/operations/api-reference.md        (Authorization: Bearer <supabase_jwt>)\ndocs/internal/architecture/data-access-patterns.md (Supabase Auth PKCE/JWT, reads via RLS)\ndocs/internal/architecture/technical-architecture-kt.md (L0–L3 layer naming → S/U series)\ndocs/internal/architecture/l2-twin-surface-contract.md  (L2 wording → S2 Awareness)\ndocs/internal/product/spinevault-spec.md          (verify auth/bridge framing)\n+ any doc matching the Drift Watchlist in ARCHITECTURE_INDEX.md\n```\n\n## Acceptance criteria\n\n```\n□ No \"Supabase Auth\" / \"supabase_jwt\" as an auth mechanism in governed docs.\n□ No \"16 tools\" / \"18 tools\" — all read 20.\n□ Twin access described as Continuity Bridge, MCP as external door.\n□ Layer language uses S-series (surfaces) / U-series (stages); no L/H ambiguity.\n□ Approval described as U4 Decide, surfaced on S2 Awareness, never in S3 Twin chat.\n□ Docs publication described as governed projection (initial-load carve-out noted).\n□ Manifest entry added/updated in IntegrateWise_Document_Manifest.md.\n□ Promoted via Triage Bot (governance_state: approved) before publish.\n```\n\n---\n\n_Submit this package to Triage. On approval, apply the changes above to the\ngoverned docs and update the Document Manifest. Until then, integratewise-docs\nremains untouched._\n"}