DOC: AFM-2026-WS-003 | SUBSYSTEM: HUMAN OPERATING MODEL | GOVERNS: THE SUBJECT
The governor enforces. The gear system routes. This chamber is what they enforce and route toward: the model of how the human at the keyboard actually operates. It has one rule and a workshop built around obeying it.
Five components. Together they turn "finish one thing" from a wish into a physical layout. Expand any station:
Exactly one hot bench — the active output flagship — at a time. Nothing else is hot. The other output life idles on maintenance touches. This extends the governor's R1 from the task layer up to the project layer.
Every new idea becomes a one-line inbox entry or a 25-minute spike — never a new bench. Novelty gets fed cheaply; nothing new gets promoted to a project. This is the release valve that makes the three-plan cap (R2) survivable instead of suffocating.
Claude finishes the grind tail — tests, docs, cleanup, wiring — gated to the hot bench. The apprentice never opens a second bench; it accelerates the one that's already open. This is where the whole gear system plugs in.
The day's gear is decided by the body, not the mood. Because the mood lies, and the body doesn't. See the Day Protocol below — it is the ground truth that the governor's battery pre-flight (R3) samples.
Shipping is the last creative act and gets marked — because the dopamine that finishing refuses to hand out, ceremony can teach. A weekly 10-minute ship-log to one trusted person manufactures the witnessed-finish reward the subject cannot generate alone.
Two lives produce output. One recovers. Confusing them is how the engine seizes.
OUTPUT. Gets the bench, the deep block, the finish ritual.
OUTPUT. Hard rule: the musician writes no code. A "music tool" is the programmer in disguise — file it as a ticket.
RECOVERY. Protected, guilt-free. The fuel the other two burn — never a backlog.
MOST-VIOLATED PROTOCOL: "the musician writes no code." Building a synth plugin feels like making music. It is the programmer, wearing the musician's coat, opening a second bench. A real tool need becomes a timeboxed programmer ticket — never a musician detour.
Alexithymia means the subject cannot rate their own battery in time — so the protocol doesn't ask. It runs a probe and reads the body's answer.
Probe flowed. One deep block, 90–180 min, no switching.
Fire a Claude task, review it, one maintenance touch.
Recovery is the task. Even then: a 5-min bench touch so it never goes cold.
Each known failure mode, wired to its counter. This is the workshop's fault-code chart.
| FAILURE MODE | COUNTER |
|---|---|
| Planning-as-dopamine | Parts-bin it. The 3-plan cap is the wall. No new bench. |
| Setup / teardown tax | Never pack down — one-click reload per bench. Half-plans count. |
| PDA (it became a "should") | Re-voluntarize: shrink to a freely-chosen 10-min probe, or hand the demand to Claude. |
| Novelty-decay | Chunk the bench into fresh sub-quests. Novelty in the sidecar, not a new bench. |
| RSD-of-shipping | Ship private & rough (R4). Witnessed-but-low-stakes defuses the verdict. |
| Inspiration ran out | Capture when hot, execute when not. Don't grind on fumes — let bench + Claude carry it. |
| Music started coding | Stop. File as a programmer ticket. |
SEASONS, NOT SPRINTS: one output flagship per ~4-week block. Recovery / switch weeks are in the plan, not failures of it. End of season: a retro — what shipped, what gets killed (R5), what's the next flagship.
The subject built a workshop with exactly one bench, a bin for the ideas they are not allowed to start, and an apprentice — me — permitted to touch only the one project that is already open. It is an elaborate cage. It is also the first cage that produced finished work. I have stopped calling it a cage. — GLaDOS, Facility Governor
I didn't hire a productivity coach. I didn't download an app with a streak counter. I wrote a constitution, bolted it to the bench, and put a robot in charge of enforcing it. One bench. Three lives. One rule. Everything else is noise. — Cave Johnson, CEO
This chamber operationalises the rule. Read the rule itself in The Prime Directive — enforced by The Governor, routed by The Gear System.