🌐 OS Master Map — Diagaxis Total Structure

DIA-1351 · the total-structure authority (sits ABOVE the build framework) · Constitution · 🔨 Build Framework · 🏛️ 3-layer mirror · ← vault status
🌐 The whole OS, in one view — so we never enter in the wrong layer

Diagaxis OS is a Signal-Controlled Production OS. The Signal Intelligence Layer reads the 14-signal moat. The Control Layer routes the next move. The Production Machines execute the correct System output. The Proof / State layer verifies the loop. Linear commands active work, but does not define the OS.

If this map conflicts with the Constitution (DIA-1341), the Constitution wins. If a build procedure conflicts with this map, stop and surface the gap before building.

Entry sequence how a fresh agent enters — now unavoidable

Constitutionnaming law↗ DIA-1341→OS Master Maptotal OS structure↗ DIA-1351→Build Frameworkbuild procedure↗ DIA-1326→Native Agent Work Floorsnavigation method↗ DIA-1228→Visibility ArchitectureLinear query law↗ DIA-1354→Active command surfacecurrent structural rollout↗ DIA-1362→OS Location Axiswhere the artifact lives→Active System / Offer Contractcommand surface

You are here at step 2. The OS Master Map is no longer skippable — the build floor passes through it before any System / Offer.

The total OS structure 9 layers · top = law, bottom = command floor

1⚖️Governance Layercross-cutting
ConstitutionDecision LogRulesContract / Map law
ownsNomenclature Constitution · decision law · naming rules · banned metaphors · no-new-metaphor rule · semantic naming · build-stop rules
notActive production delivery · runtime execution · per-client implementation
LinearDIA-1341 · decision-label issues · governance / operating-board
proofDecision receipts · Constitution readback · governance comments
↓
2🏭Foundation / Meta-Factory0.0-foundation
FrameworksTemplatesBuild proceduresNavigation protocols
ownsReusable frameworks · build procedures · template frameworks · navigation protocols · Offer Contract Framework · Offer Map Framework · Linear build-floor model
notSpecific offer truth · active client runtime · GHL object truth
LinearMeta-Factory project · DIA-1326 · DIA-1228 · DIA-1354 (Linear query law) · DIA-1362 (structure rollout) · DIA-1345 · this map
proofFramework smoke tests · Read First gates · redress receipts
↓
3🎯Strategic Doctrine1.06-strategic
Offer architectureCustomer JourneySignal doctrineOffer source truth
ownsOffer architecture · CJ Map · client-facing journey doctrine · signal doctrine · value ladder / overlap locks · strategic offer source truth · Contract / Map source structure once accepted
notActive sell-side production · client runtime · engine object state
LinearStrategic doctrine issues · Contract / Map source surfaces · offer-doctrine decisions
proofContract change logs · decision links · source-truth readback
↓
4🛰️Signal + Control Substratecross-cutting — doctrine in Foundation / Strategic, executes through both Cores + Runtime Engines
14-Signal MoatSignal Set / PulseGaps / PainRoutersRulesGates
owns14-Signal Moat · Signal Set · Pulse · Gaps · Pain language · Routers · Rules · Gates · Suppression · Escalation · Recovery · Re-emit logic
notProduction asset output · runtime object creation · client install work
LinearSignal doctrine issues · router / rule issues · Engine Object Cards · labels as query axes
proofSignal readbacks · router proof · suppression / escalation receipts · smoke tests
↓
5🔵Core · Diagaxis5.01 · 5.02 · 5.04 · 5.05
5.01 Acquisition5.02 Conversion-Sell5.04 Retention5.05 Content Machine
ownsDiagaxis acquisition · offer / sell surfaces · checkout / payment flow · conversion assets · retention / relationship · content / proof assets
notClient-installed system instances · end-customer delivery infrastructure
LinearCore·Diagaxis projects · sell-side Lines (SELL · CHECKOUT · OFFER OUTPUT · SMOKE TEST) · sell-side Assets · Contracts / Maps
proofCheckout proof · offer page proof · sales route proof · Smoke Test · receipts
↓
6📦Core · Client6.01 · 6.02 · 6.03
6.01 Overlays6.02 Deliver Templates6.03 Instances
ownsClient-facing overlays · delivery templates · live client instances · client-facing delivered systems · end-customer experience mechanics
notDiagaxis sell-side offer surface · acquisition surface · generic governance rules
LinearCore·Client projects · Delivery cards · client instance cards · delivery templates
proofInstall proof · runtime readback · client instance proof · delivery receipts
↓
7⚙️Runtime Enginesruntime
GHLStripeVoice AIOpenRouter / AIVibe Code / Site
ownsExecute system behavior — they do NOT define doctrine
notNaming law · offer scope · contract truth · strategic decisions
LinearEngine Object Cards · runtime trace sections · relations to consuming Assets / Lines / Contracts / Maps / Proof
proofAPI / UI readback · visual readback · live verification · Engine Object State
↓
8🔎Proof / Statecross-cutting
Smoke TestsStateTraceReceiptsDashboards / readbacks
ownsSmoke Tests · State · Trace · Receipts · Dashboards · readbacks · build completion proof
notSource truth · new scope decisions · runtime execution itself
LinearProof issues · receipt comments · state labels as query axes · Smoke Test cards · dashboard / readback links
proofThis layer IS the proof surface
↓
9🗂️Linear Build FloorLinear
Active command surfaceProjects / Issues / RelationsLabels as query axesReceipts / proof pointers
ownsActive command surface · main work issues · relations · labels as query axes · receipts / proof pointers · current status visibility
notOS law · strategic truth by itself · runtime object truth by label alone · vault / source truth unless mirrored in a Contract
LinearLinear commands the build · Vault stores source / reference · Runtime Engines execute · local folders store large outputs · Receipts point back to Linear
proofReceipts + proof pointers back to the owning layer

Operating stack law → structure → build → navigate → produce → prove

  1. 1Constitution gives naming law.
  2. 2OS Master Map gives total structure.
  3. 3Build Framework gives build procedure.
  4. 4Native Agent Work Floors gives navigation method.
  5. 5Contract defines source truth.
  6. 6Map navigates dependencies.
  7. 7Line organizes production path.
  8. 8Asset carries work through FRAME → OUTPUT → PROOF → RECEIPT.
  9. 9Engine Object Cards trace runtime dependencies.
  10. 10Smoke Test + Receipt prove and close.

Smoke test PASS after the entry-sequence patch (2026-06-09)

TestPASS conditionState
Fresh-agent entryAgent starts at Constitution → this Master Map → Build Framework → Work Floors → Visibility Architecture (query law) → the active command surface → System / Offer Contract — without chat history. The 6-card command stack (DIA-1362) is the entry; nothing skippable.PASS
Artifact placementIt can answer: which OS layer · which OS location · which Core · which Machine/System · Contract or Map · Line / Asset / Station / Engine Object · what proof closes it.PASS
Linear-is-not-the-OSThe Linear issue points UPWARD to the OS layer, Contract, Map, and proof surfaces.PASS
Stale-history preservationStale surfaces LOSE command authority instead of being erased.PASS

Lock state parent layer locked · downstream open

🔒 Locked
🟡 Open (downstream — not parent gaps)
  • Offer Contract Framework v1
  • Offer Map Framework v1
  • RRS Phone Coverage Update naming
  • Per-offer migrations after frameworks accepted