Tag: claude-code
All the articles with the tag "claude-code".
-
The optimization you wrote isn't the one that runs
I had the optimization written and approved, and a week later it still wasn't what ran. The fix wasn't a better design. It was making the trigger deterministic and leaving the judgment to the model.
-
Does this only work in Claude Code?
The most common objection to the Lucy Syndrome framework is that it's a Claude Code trick. It isn't. OpenAI shipped a native hook API for Codex, and the same functional scar now fires unchanged in both runtimes with identical deny semantics — the difference quarantined in a thin adapter. That is the empirical test of invariant I4: enforcement that runs outside the model's trust boundary belongs to no single platform.
-
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.