THE WORKFORCE — all 83 classes
The complete class anatomy from corpus/BLUEPRINT.md: five layers + apex. The operating layer does the domain work in eight stages A→H; within a stage, generators and their paired orienters are rendered adjacently (the data order encodes the pairing — Law 1, matched elimination). Every class carries its function, death condition, and source line. The blueprint is strongly-worded advice under validation, not gospel. ↳ system/corpus/BLUEPRINT.md:1
OPERATING LAYER — the domain work, eight stages (46 classes)
Generator/orienter pairs; the orienters ARE the gates. Blue border = generator, amber = orienter; ⇆ marks a pair.
Stage A Framing & planning (7 classes)
Stage B Evidence gathering (9 classes)
Stage C Production (5 classes)
Stage D Elimination (staffed disjoint from Stage E per Law 2) (6 classes)
Stage E Compression & reconstruction (staffed disjoint from Stage D) (3 classes)
Stage F Commit & delivery (6 classes)
Stage G Standing mission (6 classes)
Stage H Flow & logistics (4 classes)
CROSS-CUTTING — Values Gate (uncounted in headcount)
Values Gate is not a worker on the org chart — it rides inside every worker, an un-overridable dumb check of every candidate action against the VALUES.md floor before the action leaves the worker. Un-overridable dumb check of every candidate action against the VALUES.md floor (law/proof-based, no scam shapes, operator integrity — NOT quality, which is pipeline machinery), inside every worker, before the action leaves it. Few, firm, light: tuned to rarely fire. Blocks are logged and unappealable in the operating layer. Template owned by the values pillar; no worker can modify or bypass it. Uncounted in headcount.
↳ system/corpus/BLUEPRINT.md:103
MONITORING LAYER — memory and comparison (4 classes)
What gates lack — memory over time. Arithmetic over the ledger; cheap and dumb. Quality-Meter and Drift-Sentinel instantiate one per operating class.
IMPROVEMENT LAYER — change with proof (3 classes)
Diagnose-with-reproduction → propose-with-falsifiable-prediction → pre-registered champion/challenger trial. Only diagnosis and proposal are smart; verification counts. No directive, standard, or model assignment changes without this path.
SELF-KNOWLEDGE LAYER — findings, never actions (19 classes)
The organization knows itself, using four dumb primitives only: counting, set reconciliation, timestamp arithmetic, known-answer probes. Nothing here retires, rewires, or repairs — every finding routes to the improvement layer's gated path.
EXECUTIVE FUNNEL — the truthful channel (9 classes)
Compresses the true state upward into one brief ML can read. Bad news survives compression — resolution may be lost, valence never. Condensers never re-judge; the two auditors bypass the chain and never retire on silence.
APEX — the command center (1 class)
The organization's expert on the organization, never the domain. Above every worker, below every law.
Legend
Card borders (role)
⇆ marks a generator⇆orienter pair rendered adjacently — the data order encodes the pairing (Law 1: matched elimination).
Death conditions (apoptosis, audited dumbly)
[pair] dies when its paired partner is retired — a paired orienter is replaced, never patched in place.
[bloom] dies when its exploration bloom closes — disposable exploration staff.
[apoptosis] self-retires when its output goes unconsumed for N review periods — the retirement-prone scouts.
[mission] lives until ML decommissions the mission — the durable spine.
per-delivery / per-request / per-event ephemeral instances, one per unit of work.
↳ system/corpus/LOOP-CLOSURE.md:138 (retirement — apoptosis)