🔒 The structure, unified — so decisions stop scattering
11h+ continuous work = many decisions + logic. Without ONE unified structure it scatters (scatter → panic → invent). The OS Master Map locks WHAT the OS is; this 3-layer mirror locks WHERE each piece lives — so you never hunt 'which issue did we decide this in' again.
ONE unified picture of WHERE the OS lives so decisions/logic stop scattering. The 3-layer mirror — Vault = frozen KB · Linear = the PRIORITY operational post · app = live mirror — sits UNDER the OS Master Map (DIA-1351, the 9-layer total structure): the Master Map says WHAT the OS is, this says WHERE each piece lives + runs. Governed by the Nomenclature Constitution (DIA-1341) — a Signal-Controlled Production OS. Read-only render of D111.
The 3 layers one role each · linked by clickable links
📄 VAULT = frozen KB / reference
The read-only reference base. Read at a build's START, written at its END only — FROZEN until the 'big reboot card' (Souky 2026-06-09): things move too fast to maintain it mid-flow. Never the live truth — Linear is.
holds
entity masters (DIA-603 · 9-section · the 'one space per entity')
specs · frameworks · skills · SOPs (the producers)
decision-log (D-IDs) · registries
rule
Read-on-demand only · FROZEN until the big reboot card — no card-by-card maintenance. LightRAG paused.
verdict
🧊 frozen KB — read on demand, NOT the live truth (Linear is). Maintenance deferred to ONE big reboot card when stable.
🎫 LINEAR = the PRIORITY operational post
Where the work RUNS — the priority surface now (things move too fast to maintain the vault mid-flow). NOT a passive status board — the running instance, structured by the granularity ladder. Linear commands the build; it does not DEFINE the OS (that is the Master Map).
holds
the 3 Cores (Diagaxis · Client · Meta) = Projects
System = Project · Line (SELL · CHECKOUT · OFFER OUTPUT · SMOKE TEST) = issue under it
Asset = the command card (FRAME → OUTPUT → PROOF → RECEIPT) · Station = a step (row / sub-issue)
rule
ALL action in the issue · Souky filtered by effort: · verifier ≠ executor.
verdict
🎯 the un-bottleneck — tells each operator their next move, no walls
📱 APP = the LIVE MIRROR
status.diagaxis.io — REFLECTS the live state, never holds the work. Data-fed from the JSON contracts / registries / ledger, plugged into hub + system status, real-time.
holds
the OS Master Map (/master-map) + Build Framework (/build) + the /os index + the toiles + /structure
fed by os-master-map.json · os-map.json · the toile-*.json · the verification-ledger
rule
Data-fed + live = reflects reality. NEVER a detached static .html (= a picture in time that drifts).
verdict
🪞 the screen — read-on-demand, always true
Linear structure System → Line → Asset → Station
Level
Is
Linear primitive
Example
System
a Core / Machine — a packaged offer or client mechanism
Linear Project
🔵 Core · Diagaxis · 🟠 Core · Client · 🏭 Meta
Line
a production lane under the System
Issue (under the System)
LINE · RRS · SELL / CHECKOUT / OFFER OUTPUT / SMOKE TEST
one execution step — a ROW in the asset's step-table (sub-issue only if multi-day)
Table row + ledger
spec ✅ · GHL-publish ⏳ · smoke ⏳
Granular where it helps (assets), compact where it would explode (steps = rows). A System's Lines + Assets are issues; Stations stay rows in the asset step-table + ledger — never one issue per step.
🦴 Skeleton-first
Build the System + its Lines (grouped by Core) as the navigable structure BEFORE filling content. Each Line explodes into Assets + Stations only when actively built. Light-when-dormant, full-when-active — a pointer, not a doctrine copy. → no walls of disconnected issues.
The WHY each piece un-bottlenecks Souky
Structural piece
The payoff
UNIFY ALL ASSETS up front
you SEE the whole build → anti-mushroom / anti-wall (never discover asset #15 mid-build)
State matrix on the System / Line
the whole build (asset × stage) at a glance → zero hunting
Owner-lanes (Claude · Vulcan · Souky · Codex)
1 owner per step, in parallel, no collision
Souky's lane filtered by effort:
the AID, not a review → you read only YOUR micro-tasks (inputs provided) — the real un-bottleneck
ALL action in the issue
zero va-et-vient vault↔active (vault read at start, written at end)
verifier ≠ executor + live evidence
anti-drift — no ✅ without proof:
S·D·R·C judgment capture
the JUDGMENT (why) is the durable artifact → we never re-litigate (e.g. the email-source hunt this session)
❌ Detached static .html (dashboards/*.html · offer-dashboards/*.html · visual-maps/*.html) → a 'picture in time' that drifts. Consolidate INTO the live app.
HTML as a DELIVERABLE (a VibeCode funnel IS html) is unaffected — that's the product, not the navigation surface.
🔧 Builds carry per-step detail (not thin stubs)
Active build = function · goal · definition-of-done · responsible-agent · checklist PER STATION (D104-D107).
For a VISUAL build (funnel/page) the per-station detail = the VibeCode 9-step method — vibecode-funnel-clone-and-niche-swap-framework.md §10 (HTML-first rebuild → brand → mobile → integrations → avatar-language → niche-clone, + §10.9 receipt). LINKED from the issue so it never drifts out of reach again.
Reuses what already exists nothing new invented
Existing framework
Role in the structure
DIA-1341 Constitution + DIA-1351 OS Master Map
the naming law + the 9-layer total structure this 3-layer mirror sits under
DIA-1326 Build Framework + DIA-1228 Work Floors
the production model: System → Line → Asset → Station · FRAME → OUTPUT → PROOF → RECEIPT
DIA-603 entity masters (9-section)
the 'one space per entity' truth — 20 already exist
os-map.json + /os
the clickable index of the systems
3 Cores + core:/machine: labels
the Linear projection of the layers/machines
Nothing new invented — D111 CONNECTS frameworks already built. Reconciled 2026-06-09 to the signed Constitution model; the pre-Constitution DIA-810 '4-phase Delivery' framing it formerly cited is superseded (Asset stage DELIVERY→OUTPUT per DIA-1350) and pending its own redress.