The Lucy Syndrome
Why AI agents forget corrections, and the enforcement layer that makes them hold. The core research line — from the diagnosis to functional scars to instrumenting a live system.
-
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.
-
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.
-
A month of functional scars: 934 fires, one broken validation loop, and what it cost
I wired ten functional scars into my own workspace and let them run for a month. Half the signal came from one hook with documented false positives, and 3,838 captured opportunities sat unread. Here are the numbers and what they forced me to build.
-
Functional Scars — turning corrections into a primitive
fscars 0.1.0 is out — a bolt-on correction primitive for AI coding agents, built on the framework from the Lucy Syndrome paper. Apache 2.0, pip install fscars.
-
From memory to scar: a four-layer progression
Anthropic shipped managed memory stores in April. They sit at the third of four layers. The fourth, hooks, is the one that closes the Lucy loop.
-
The Lucy Syndrome: Why LLMs Forget Corrections
LLMs don't remember yesterday. That gap has a name, a causal mechanism, and a fix that doesn't require better memory.
-
The Lucy Syndrome and AI
LLMs don't remember yesterday — and that gap has a name. A five-part essay on the Lucy Syndrome, functional scars, and what it takes for a production system to actually learn.
-
Questions and answers
Questions about the Lucy Syndrome essay — its scope, its method, and what functional scars actually look like in operation. Compiled from real conversations and updated as new questions arrive.
-
Where this came from
The informal companion to the Lucy Syndrome essay — how the observation started, how the system around it took shape, and why an operator in Paraguay ended up writing about model amnesia.