🗺️ The Complete OS — reconciled map

ONE place to see every system · DIA-831 → feeds DIA-809 · source os-map.json · ← vault status

🪤 The scatter, reconciled — so it stops feeling infinite

The system-registry tracks 17 systems (mostly 5.05-content). The OS REAL system count is ~3x that. The Core · Client machine (what makes the money), the prospection system, the journey, 5.02 conversion + 5.04 retention are NOT registered anywhere — invisible, untracked. That gap IS the 'sable mouvant'.

Read-only assembly of what already exists (4 sources) — no new content. We start here, we adjust as we see the map.

🔗 This map = the index. Linear mirrors this map (Souky 2026-06-02). Project = Core (3: 🏭 Meta-Factory · 🔵 Core · Diagaxis · 🟠 Core · Client). Issue = System (ONE DIA-810 template-issue each). Labels: core:* + machine:*. This /os map = the clickable INDEX → each system links to its issue. Start here, click in, never search. Linkable systems show ↗ → click into their DIA-810 issue. Worked example: woml-sell → DIA-528.

systems in the real OS

📋 registered (tracked)

❌ UN-registered (the sand)

actually ACTIVE

🏭 META SUBSTRATE — the factory 4 systems · 2 registered / 2 not · 0.0-foundation · 1.06-strategic · 1.011-kb-extraction · 1.07-automation-ghl · 1.08-finance

builds + governs the machines (gates · generators · registries · doctrine). NOT production itself. — 🟢 solid — this layer is the most mature

Gates

System	Hub	📋 Registry	⚙️ Generator	State
`8 operating gates (retrieval-sweep · copy-prod · build-quality · repeat-build · rebuild-detect · cat-class · lane-disc · decision-prop)`	CLAUDE.md + 1.06	not in registry	G-06..G-10 + G-16/G-18	LIVE — enforced every session

Generators

System	Hub	📋 Registry	⚙️ Generator	State
`Generator library (44: G-01..G-44)`	1.06 generator-registry.md	not in registry	G-10 meta	~34 LIVE · 5 in-flight · 2 missing · 3 deferred

Knowledge / KB

System	Hub	📋 Registry	⚙️ Generator	State
`KB Extraction Pipeline`	1.011-kb-extraction	tracked	G-01	ACTIVE (first system ACTIVE under MMEL · 88 outputs)

Visibility

System	Hub	📋 Registry	⚙️ Generator	State
`vault-status Vercel app (status.diagaxis.io)`	2.0-apps / 1.06	tracked	none	GATED (LIVE deploy, owner UNASSIGNED, no generator)

🔵 Core · Diagaxis 19 systems · 15 registered / 4 not · 5.01-acquisition · 5.02-conversion-sell · 5.04-retention · 5.05-content

Diagaxis sells its OWN systems. Customer Journey Map = the biz-owner customer journey. — 🟡 content-machine registered + 2 active; everything that sells (prospection/conversion/journey) is UN-registered

5.01 Acquisition

System	Hub	📋 Registry	⚙️ Generator	State
`Prospection system (14 workflows)`	5.01	not in registry	G-15 Magnus	publish-pending — toile mapped (DIA-811), 0 published in GHL

5.02 Conversion-sell

System	Hub	📋 Registry	⚙️ Generator	State
`Word of Mouth Loop — SELL/onboarding (Diagaxis-side)` ↗ DIA-528	5.02	tracked	G-27 wiring	✅ consolidated into DIA-810 template (the worked example) · build pending Souky verification day
`Offer sell-side (Ana close + offer pages)`	5.02	not in registry	G-11 funnel · G-12 brief	spec — page-specs exist, not wired
`Digital Front Desk page-spec`	1.02→5.02	tracked	none	GATED (approved 2026-05-26, no generator)
`Flywheel Response page-spec`	1.02→5.02	tracked	none	GATED
`Your Digital Front Connect page-spec`	1.02→5.02	tracked	none	GATED (voice-flip 2026-05-27)

5.04 Retention

System	Hub	📋 Registry	⚙️ Generator	State
`Pax support + community/membership`	5.04	not in registry	none	frame locked, dev parked (community spine v0)

5.05 Content machine

System	Hub	📋 Registry	⚙️ Generator	State
`Blog (Search Trust Article)`	5.05	tracked	G-43	ACTIVE (1/wk)
`Carousel (7-slide social)`	5.05	tracked	G-44	ACTIVE (4/wk)
`Newsletter`	5.05	tracked	none	GATED — production verified, no generator
`Signal video script (Nate Engine)`	5.05	tracked	none	GATED — no per-format generator
`Reels (15-30s vertical)`	5.05	tracked	none	GATED — no production verified
`Cross-post shorts`	5.05	tracked	none	GATED — no generator
`IG feed visuals`	5.05	tracked	none	GATED — no production verified (Vesta)
`Pinterest pins (15/wk)`	5.05	tracked	none	GATED — highest cadence, biggest drift exposure
`X posts (7/wk)`	5.05	tracked	none	GATED — skill file missing
`LinkedIn repurpose`	5.05	tracked	none	GATED — no production verified
`LinkedIn long-form original`	5.05	tracked	none	GATED — variant not specced

Journey post-close (§12.8-12.10)

System	Hub	📋 Registry	⚙️ Generator	State
`Customer journey post-close (J00-J11)`	5.0 / CJ-map	not in registry	none	0 workflows built; field substrate ~70% exists (DIA-830). §12.9 spec'd (not a gap).

🟠 Core · Client 15 systems · 0 registered / 15 not · 6.01-overlays · 6.02-deliver-templates · 6.03-instances

What Diagaxis BUILDS for each client (the local biz's own system serving its own customers). Customer Journey Map = the owner's-customers journey. — 🔴 the money machine — and 0 systems registered, 0 live end-to-end instance. The biggest sable mouvant.

6.02 Build engine

System	Hub	📋 Registry	⚙️ Generator	State
`Onboarding pipeline (steps 0-12)`	6.02	not in registry	G-27 wiring	spec — not GHL-built
`Custom objects (Client Implementation · Cycle Progression Tracker)`	6.02	not in registry	none	spec
`Build templates (welcome · portal shell · impl record)`	6.02	not in registry	none	spec
`Client master template Contract + Map (DIA-603)`	6.02	not in registry	G-35	template ready
`7 build skills (funnel · voice-ai · workflow-email · site · lead-magnet · prompt · page-playbooks)`	6.02	not in registry	G-13 voice · G-19 site · G-11 funnel	spec — not exercised end-to-end
`Agent KB storage + push (Maya/Pax/Ana/Dax KB)`	6.02 / 1.07	not in registry	G-31 MISSING	REQUIRED-but-MISSING — gates ALL delivery (DIA-369)

6.01 Overlays

System	Hub	📋 Registry	⚙️ Generator	State
`Niche + avatar overlays (12 cards)`	6.01	not in registry	G-28 overlay · G-30 language	spec — 5 niche language packs done, allsmallbiz inline

Offers (as delivered systems)

System	Hub	📋 Registry	⚙️ Generator	State
`Digital Front Desk $297`	6.0	not in registry	G-27 · G-11	partial — pages pending · Maya KB 🔴
`Word of Mouth Loop $497 — client DELIVERY (Line 1+2 snapshot)` ↗ DIA-835	6.0	not in registry	G-27 · G-11	✅ consolidated into DIA-810 template (DIA-835) · client-side snapshot spec NOT written = the gap (blocks sell-side W4/5/6) · build pending Souky verification day
`Revenue Root System $997`	6.0	not in registry	G-19 · G-27	semi-live — legacy 'Intake' naming · screenshot pending
`Flywheel Response $997`	6.0	not in registry	G-28 · G-43	partial — VibeCode scaffold · DIA-509 blocked
`Continuity System $2K`	6.0	not in registry	none	PAUSED (Phase 2 gate)
`Your Digital Front Connect $297`	6.0	not in registry	G-11	draft — chat-widget collision · packet rebuild

AXIS (the container)

System	Hub	📋 Registry	⚙️ Generator	State
`AXIS client portal (6 sections + tier-flip)`	6.02 / 1.07	not in registry	none	doctrine locked · tier-flip automation pending (DIA-378)

6.03 Instances

System	Hub	📋 Registry	⚙️ Generator	State
`Marie-Pier (only instance)`	6.03	not in registry	none	pre-activation (DIA-550 §10, 26-item checklist) · 0 live end-to-end · 108 combos un-resolved

What this reveals the foundation, made visible

The factory (gates + generators) is solid. The PRODUCTION is what's un-registered + un-tracked.
Core · Client (the money machine) has 0 rows in system-registry: invisible to the MMEL + the status app's system layer.
The prospection system, the journey, conversion + retention all live ONLY in toiles/specs, not the tracked system layer.
Generators mostly EXIST (44) but aren't WIRED to the un-registered systems — the binding gap.
Next per DIA-809: this reconciled inventory becomes the backbone of the clean-reset skeleton (one step at a time, adjust as we see the map).