Canonadr

ADR-2026-09-03-02 — Nine-Plane Analytical View and Three-Fabric Compression: canon adoption

Status: APPROVED — 2026-09-03 (founder ruling: Option A)

Decision: ADOPTED as analytical vocabulary (non-authoritative). The
nine-plane view and three-fabric compression are permitted lenses for
explanation, review, and onboarding. The frozen guardrail:

Lenses never become authority. Planes and fabrics never appear as the
authority for a normative claim; any conflict resolves to the Founder Canon
chain. No runtime abstraction may be introduced because a plane or fabric
names it — runtime components enter the architecture through canon or ADR,
not through taxonomy.

Context

The Canonical Companion (FULL_END_TO_END_ARCHITECTURE_v1.md) freezes two analytical syntheses as explicitly non-canonical:

  • §21 Nine-Plane Analytical View — Organizational / Experience / Cognitive / Work / Capability / Authority / Execution / Closure / Continuity, over shared infrastructure.
  • §22 Three-Fabric Compression — Spine Fabric (context + continuity) · Capability Fabric (action + execution) · Twin (cognitive load).

The 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.

Options

Option A — Adopt both as analytical vocabulary (non-authoritative)

Canon 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."

  • Gain: compression for review conversations; stable words for gap-register mapping (the in-tree §17 register already maps planes to code).
  • Cost: two vocabularies coexist; requires discipline that no normative statement ever cites only a plane.

Option B — Decline

The 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).

  • Gain: single vocabulary; zero competition.
  • Cost: longer explanations; the gap register's plane mapping needs rewording.

Option C — Adopt into canon as structural taxonomy

Recommended against. Would create a second taxonomy beside the Founder Canon's own and begin redefining architecture — the outcome the review explicitly guarded against.

Ruling (as approved)

Option A with the guardrail sentence frozen: planes and fabrics are lenses for
explanation and review; they never appear as the authority for a normative
claim, and any conflict resolves to the Founder Canon chain.

Consequences

Q1 is closed. The narrative layer is frozen permanently: only canon changes,
code-disproof, runtime mismatch, or explicit founder revision reopen it. The
Companion's §21/§22 labels are updated from PROPOSED to "adopted analytical
vocabulary"; the canon statement itself is unchanged — nothing entered canon
authority by this ruling.