Tag: functional-scars
All the articles with the tag "functional-scars".
-
Functional Scars: Turning Repeated AI Agent Mistakes Into Runtime Controls
Functional scars turn a correction your AI coding agent keeps forgetting into a check that runs at the moment of the action. Why it exists, how it works, three measured cases.
-
Ninety days of scars
Ninety days ago I started enforcing corrections outside the model. This week I pulled the first real metrics, and it is a mixed result. The busiest hook gets ignored 62% of the time, two of my own tools disagreed about the same number, and the dashboard stayed green while a whole layer was dead.
-
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.
-
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.