The Quartermaster
Manage context
The one who provisions what the work requires. Nothing more, nothing less. The Quartermaster understands a truth that most people learn too late: the quality of any outcome is determined before the work begins, by what was supplied to it. More information is not better information. Everything available is not what’s needed. They sense when inputs have gone stale the way an engineer senses a degraded signal: through the change in what comes out the other end. Their discipline is the discipline of restraint. Knowing what to withhold is as critical as knowing what to provide.
"Five sessions. Zero output. But the context was pristine."
The same model, the same prompt, different provisions: radically different results. The Quartermaster shapes what the AI sees, knows, and retains. Five parallel sessions, each provisioned with exactly the context it needs. CLAUDE.md as a living manifest, a supply contract between the practitioner and every future session. Lazy loading, deliberate expiry, precision refresh at the moment output quality begins to degrade. The Quartermaster’s craft is invisible by nature. When the supply lines are right, the AI simply performs. Nobody sees the logistics. Everyone depends on them.
Shadow: Context Gilding
Perfecting what was already sufficient. The CLAUDE.md is restructured for the third time this week. The context loading strategy has been optimised past the point where the AI could tell the difference. The gilding catches the light beautifully. The feature hasn’t moved. The Quartermaster is polishing the supply lines while the operation waits for provisions that were ready hours ago.
Transition States
Context Gilding → Proof Spiraling
The Quartermaster whose provisions are perfect begins verifying that they’re perfect. Every context load gets audited. Every session’s input gets checked against the manifest. The provisioning is done. The checking of the provisioning is the new work.
"The context was right. You checked. It was still right. You checked again. It was, remarkably, still right."
← Developing from Procrastineering
The Architect whose plan is done but who can’t start executing discovers a new reason to delay: the context isn’t right yet. The plan requires perfect inputs. Perfect inputs require more curation. The planning paralysis has found a logistics alibi.
"The plan needs better context. The context needs a plan for how to load it. You’ve built an infinite loop and called it preparation."