A work order materializes as a directory tree where every governed concept is a subdirectory and every artifact is a file. Gatekeepers read the tree; they cannot pass on words alone.
Real WO: build_rig. File counts via find <wo> -type f | wc -l on each subtree.
The WO contract is signed and lives in workorder/. Architect's plan goes in dispatch_design/. Per-task work packages live in dispatch_work_packages/. Witness output, gate verdicts, and ED-bank entries land in gate_evidence/<task>/. Auto-generated verdicts go to gate_evidence/generated_packets/. The gatekeeper service reads these directories; nothing happens off-record.
ONE WORK ORDER · ON DISK
workorder/ 3 files the signed contract
dispatch_design/ 4 files architect plan
dispatch_work_packages/ 78 files task packets handed to devs
gate_evidence/<task>/ 4–38 files evidence per task (×11 tasks)
gate_evidence/generated/ 8,438 files auto-checksummed verdicts
grounding/ 152 files per-role resume overlays
observations/ 4 files banked decisions + discoveries
standdown/checkpoint/ 1 file RESUME packet
gatekeeper_workspace/ ~48k files live gatekeeper state + transport
Per-task breakdown (this WO):
t-a1 20 · t-a2 16 · t-a3 30 · t-a4 10
t-b1 16 · t-b2 38 · t-b3 34 · t-b4 27
tea4 6 · teb3 4 · testapi 0