The home page shows only what's newest. This is the full drawer: the dated dispatches in the ledger, and the library of readings and reference texts they're drawn from. Nothing here expires just because it stopped being new.
A routine is just a Claude Code session that triggers itself. Field notes on trigger, context, and steerability, plus a work order builder you fill in and copy.
The agent can produce more than you can responsibly inspect. The next skill is keeping verification cheaper than generation.
Six months of defaulting to HTML for plans, reviews, and diagrams: what changed, what broke, and the one carve-out I keep. A reply to Thariq and Kurtis Redux.
Twenty-one rules went in. Five survived contact with real work, and one of them was “write less here.”
When the loop stalls, I reach for the same four corrections, in order, before I touch the prompt.
An HTML diff with the reviewer’s notes pinned in the margin beats a comment thread every single time.
Where the cheaper agent holds, where it folds, and how its prompting wants to be shaped differently.
Treat the agent as a study partner, not a vending machine. A reading method that survives long sessions.
Notes from how a shop that ships every day delegates to its agents, and where the humans stay.
Ask the model to write the prompt before you write the task. Why the extra hop earns its keep.
Seven points where a human still has to step into the agent’s loop, and what each one costs you.
Skill compounds where the work happens, not in the docs. A case for letting the agent watch you work.
The dispatches don't come from nowhere. These are the pieces behind them: field readings of the corpus I work from, and the reference texts they argue with. Undated by design; they're a shelf, not a feed.