• repo prose: source truth
• diagram: illustrative snapshot, refreshed at topology / milestone changes
• repo README.md and docs/architecture.md: canonical structure articulation

The diagram conforms to apexSolarKiss/design-system-ASK Tier 1 + Tier 2 by reference at generation time. The compiled diagrams.css in this folder is render support, not identity source truth. design-system-ASK remains the visual authority; this folder does not own visual identity.

diagrams-chrome.js, diagrams-fit.js, diagrams-text-layout.js, diagrams-pointer.js, diagrams-static-H-engine.js, diagrams.css, and export-png.js are design-system-owned — vendored byte-identical and not edited here. diagrams-fit.js computes a zero-band base candidate, keeps that candidate's scale when it already clears the caption / legend / HUD panels, and reserves the measured panel edges only when the candidate would collide; the engine's v3 balance option then centers the drawing vertically between the chrome above and below it, and compactClearance: 32 caps the total clearance at 32px while the responsive chrome is compact. The engine requires the fit helper's v3 and throws a named error with an older copy. diagrams-text-layout.js is the shared text-measurement and role-layout contract: role caps, line heights and the wrapping primitive live there rather than in each engine, and it declares the patterns it serves. Both must load immediately before the engine, in that order; the engine throws a named error rather than falling back silently if either is missing, and it checks the text-layout carrier's callable interface and its declared target list rather than merely its presence — so a stale or wrong-plane mirror fails at load instead of deep inside layout.

With no required panel reservation, the prior fit arithmetic is preserved, against the clearance in force (80px, or 32px in the compact chrome), while each available axis is at least twice that clearance. On a more constrained positive axis, total clearance degrades continuously and consumes at most half the available space. Within a fixed available rectangle and panel-reservation state, reducing that axis cannot increase its clearance-limited scale contribution.

Because that fit can land below the engine's ordinary zoom-out floor on a constrained viewport, the live floor is the lower of the historical base floor and the most recent Fit — so zoom-out is a no-op at Fit rather than increasing the scale. Fit itself is never clamped.

• topology or milestone change: refresh the source data file
• per-PR repo edits: do not refresh
• per-article work: do not refresh
• ecology-level structural shift: open a new source-vN

README.md                                       this file
control-surface_architecture-tree.html          renders TREE_D01
control-surface_architecture-tree.source.js     TREE_D01 data
control-surface_intent-inbox-lifecycle.html          renders TREE_D08
control-surface_intent-inbox-lifecycle.source.js     TREE_D08 data (source-v2) — the routed-instance
                                                     lifecycle as a standalone figure: four events,
                                                     state-keyed resolution, the state machine, closure
                                                     coupling, the two evidence axes, _STATE.md, and
                                                     artifact-instance identity.
                                                     Overlay/events/resolution/state-machine/closure/
                                                     axes/queue/instance-identity are owned by
                                                     AGENTS.shared.md; the
                                                     concrete _STATE.md state vocabulary is owned by
                                                     docs/advisor-project-surface-architecture.md
diagrams-chrome.js                              DS-owned responsive chrome; loads after
                                                the chrome markup and BEFORE the fit
                                                support
diagrams-pointer.js                             DS-owned shared pointer controller
                                                (v2); loads after the chrome and
                                                BEFORE the fit support
diagrams-fit.js                                 DS-owned shared fit support; loads
                                                immediately BEFORE the engine
diagrams-text-layout.js                         DS-owned shared text measurement +
                                                role layout (caps, line heights,
                                                wrapping); loads AFTER the fit
                                                support and BEFORE the engine
diagrams-static-H-engine.js                     layout + pan/zoom engine
diagrams.css                                    compiled Tier 1 + Tier 2 style
export-png.js                                   3840×2880 PNG export
_dsa-tokens/                                    vendored Tier 1 + Tier 2 token mirror

• Open control-surface_architecture-tree.html directly in a browser, or via GitHub Pages if configured.
• Drag to pan; scroll to zoom; HUD controls in the bottom-left; ⤢ to fit. On a phone, one finger pans the drawing from anywhere on it and two pinch it — never the page — and on a narrow or crowded canvas the caption and legend close behind About and Legend beside or above the HUD, with the header's subtitle and stamp moved into About.
• Theme follows the OS preference (prefers-color-scheme); the CSS supports explicit data-theme="light" or data-theme="dark" on <html> if a specific theme is needed.
• The PNG export outputs a 3840×2880 image in the resolved theme.

This repo-local diagram originated in the v9 operator-side ecology-ASK diagram package and was first absorbed here at source-v2 // render-v9.

The current tuple is source-v7 // render-v20 (2026-10-08). Source advances when the authored architecture changes; render advances only when the renderer realization changes.

The operator-side package and historical render iterations remain in ecology-ASK-EXTERNAL/scratch/ and are not repo truth.

• TREE_D02 (method-ASK topology) — lives in apexSolarKiss/method-ASK/docs/diagrams/ (landed)
• TREE_D03 (system-ASK topology) — operator-side only; not authorized for any repo absorption
• Operator-side context architecture substrate (private; conform by reference, do not absorb)
• Tier 3 identity inside the diagram artifacts — excluded by the Tier model; both figures remain Tier 1 + Tier 2. index.html is a separate ASK-branded live navigation surface and carries an ASK-assigned Tier-3 value for that surface only: the assignment does not propagate into either diagram, does not make control-surface ASK-the-entity, and does not come from surface-shell, which ships a slot and no mark.
• Runtime dynamic import from design-system-ASK CSS (no; conform at generation time)