Fifteen months of workshops. Three generations of agent tooling. The tools kept changing; the operating principles didn't. What you're holding is the distilled result — the lessons that survived — split into two layers: durable directives that outlived every tool migration, and a versioned command console where every snippet carries a stamp proving it was re-checked against the CLIs actually installed today, not remembered from a slide.
The tools are disposable. The lessons are the equipment.— the whole guide, in one sentence
Every command in this guide was re-run against currently installed tooling on the stamp date — not copied forward on faith. Muscle memory is a liability in a field that reinvents itself quarterly; the stamp tells you exactly how much to trust yours.
| Stamp | Meaning |
|---|---|
| verified 2026-07-10 | Type it as written. Probed against the live CLI on the stamp date. |
| changed | Still works, but the surface moved — read the note first. |
| risky | Verified, but explicitly dangerous. Isolation + external verification required. |
| superseded | The concept survives; the entry point moved. The note names the current equivalent. |
| removed | Gone. Kept for archaeology; the note names the nearest replacement. |
Stamps older than ~3 months are a smell. The whole reference is re-verified by an automated probe suite before every workshop — details at the end of the Command Console.
These lessons weren't designed — they were forced, one era at a time. Each era below ended when its favorite habit hit a wall. Knowing the arc helps you recognize which era you're operating in right now:
The agent lives inside the editor and follows instructions. The human's edge is supplying reality: official scaffolds, curated files, search results, real examples, tests. "Context engineering" becomes a deliberate craft — the agent performs only as well as the evidence it can see.
Print mode, JSON streams, pipes, shell functions, tool allowlists, hooks. The agent stops being a chat window and becomes a Unix process you can wrap, compose, and reuse. Plan in one context, execute in another. Convert every repeated success into a named tool.
Fan-out is easy; reviewing the fan-out is not. Human attention doesn't scale with token spend. Overlapping agents create merge debt. More context can make results worse. The correction: normal code, explicit task boundaries, small commits, one or two supervised tracks.
Keep foundational instructions thin. Load specialized guidance only when relevant. Enforce invariants with hooks, not prose. Generate alternatives with councils — but reserve the final choice for human taste. Treat agent-built infrastructure as a sandcastle until its value earns durability.
The destination: disposable implementation under a durable human contract. Requirements, decisions, constraints, and proof scenarios outlive any individual chat. A coordinator holds the goal; narrow workers get bounded contexts; saved checks — not agent narration — establish completion.
CH·02
Field Procedures
16 named workflows in four mission phases — each with steps, a use-when, and its proof of completion.
CH·03
The Command Console
The versioned command reference. Every snippet stamped against today's CLIs — 21 probes, 0 drift.
CH·04
The Training Ladder
Ten levels from shell literacy to human judgment. In order. Skipping rungs is how autonomy hurts you.
CH·05
The Codex
The shared vocabulary, plus the museum of superseded equipment — retired for reasons worth knowing.
An agent saying "done" is not evidence. Completion is established by a saved, inspectable artifact outside the conversation — a passing test run, a diff, a log, a screenshot, a receipt.
No saved check, no claim.
This is the single lesson every era re-taught in a new costume. In the editor era it was "agents without tests are dangerous." In the process era it was independent review and stop hooks. By 2026 it hardened into proof scenarios and the four words above — and it applies to this guide itself: the stamps exist because the guide obeys its own rule.
The little robot will always project the thumbs-up. Take the receipt instead.
disposable implementation // durable human contract