Posts
All the articles I've posted.
-
Give the agent the real source of truth
An AI setup I call MARCO placed 26 drainage culverts into our road-design software from a one-column list. The speed wasn't the interesting part. What mattered was finding which file held the real toe of the slope, and turning the fix into a reusable skill.
-
Anatomy of a four-minute boot
Where my Claude Code sessions actually spent their first four minutes, and what cut it to thirty seconds without losing any context. Hooks were three seconds of the problem. The model's diligence was the rest.
-
How do you know a correction held? Instrumenting an agent in production
Functional scars make a correction persist. They don't tell you whether the system as a whole is getting better. So I instrumented every session — deterministic, zero-token, never blocking — and let a monthly pass turn the evidence into mechanism changes. The first thing the data caught was me.
-
The same scar, two agents
fscars 0.4.0 promotes the Codex adapter from instructions to native hooks. A correction you write once now fires deterministically in both Claude Code and Codex — and the scar itself does not change. Here is how each side works, and the one honest limitation.