{"slug":"canonical/adr/ADR-2026-09-03-02-nine-planes-three-fabrics-canon-decision","title":"ADR-2026-09-03-02 — Nine-Plane Analytical View and Three-Fabric Compression: canon adoption","section":"canonical","sectionLabel":"Canon","status":"canon","type":"adr","path":"canonical/adr/ADR-2026-09-03-02-nine-planes-three-fabrics-canon-decision.md","bytes":3466,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** APPROVED — 2026-09-03 (founder ruling: **Option A**)\n\n**Decision: ADOPTED as analytical vocabulary (non-authoritative).** The\nnine-plane view and three-fabric compression are permitted lenses for\nexplanation, review, and onboarding. The frozen guardrail:\n\n> **Lenses never become authority.** Planes and fabrics never appear as the\n> authority for a normative claim; any conflict resolves to the Founder Canon\n> chain. No runtime abstraction may be introduced *because* a plane or fabric\n> names it — runtime components enter the architecture through canon or ADR,\n> not through taxonomy.\n\n## Context\n\nThe Canonical Companion (`FULL_END_TO_END_ARCHITECTURE_v1.md`) freezes two analytical syntheses as explicitly non-canonical:\n\n- **§21 Nine-Plane Analytical View** — Organizational / Experience / Cognitive / Work / Capability / Authority / Execution / Closure / Continuity, over shared infrastructure.\n- **§22 Three-Fabric Compression** — Spine Fabric (context + continuity) · Capability Fabric (action + execution) · Twin (cognitive load).\n\nThe Founder Canon (v6.0.0, §14/§31) defines the runtime as a single chain and the master map, without a plane taxonomy or a fabric trio. Both syntheses emerged from end-to-end explanation work; neither has been adopted or declined. Canon §32's warning stands: capability is a resulting system property, not an independent pillar — which is exactly why the \"Capability Fabric\" framing needs an explicit ruling rather than drift.\n\n## Options\n\n### Option A — Adopt both as analytical vocabulary (non-authoritative)\n\nCanon stays the sole authority for semantics. The plane/fabric terms become *permitted analytical lenses* for documentation, review, and onboarding — usable to explain, never to define. The Companion's labels change from \"PROPOSED\" to \"adopted as analytical vocabulary; canon wins conflicts.\"\n\n- Gain: compression for review conversations; stable words for gap-register mapping (the in-tree §17 register already maps planes to code).\n- Cost: two vocabularies coexist; requires discipline that no normative statement ever cites only a plane.\n\n### Option B — Decline\n\nThe Companion's §21/§22 move to an appendix marked \"historical synthesis, superseded as explanatory scaffolding.\" All explanation uses only canon chain terms (Spine, Work, Twin, Capability Fabric-as-resolver, Governance, Hermes, Closure, Continuity).\n\n- Gain: single vocabulary; zero competition.\n- Cost: longer explanations; the gap register's plane mapping needs rewording.\n\n### Option C — Adopt into canon as structural taxonomy\n\n**Recommended against.** Would create a second taxonomy beside the Founder Canon's own and begin redefining architecture — the outcome the review explicitly guarded against.\n\n## Ruling (as approved)\n\nOption A with the guardrail sentence frozen: *planes and fabrics are lenses for\nexplanation and review; they never appear as the authority for a normative\nclaim, and any conflict resolves to the Founder Canon chain.*\n\n## Consequences\n\nQ1 is closed. The narrative layer is frozen permanently: only canon changes,\ncode-disproof, runtime mismatch, or explicit founder revision reopen it. The\nCompanion's §21/§22 labels are updated from PROPOSED to \"adopted analytical\nvocabulary\"; the canon statement itself is unchanged — nothing entered canon\nauthority by this ruling.\n"}