FIELD NOTE / X
A long context can remember the wrong rule.
The short film, the complete written thought, and the evidence behind it.
The X conversation link will follow its public release.
A long context can remember the wrong rule.
Video caption
A long context can remember the wrong rule. It lacks the facts needed to challenge it. Use the fact only after checking its current authority. Narration uses Eric's authorized AI voice clone. #EricFieldNotes
Full written post / accessibility read
A handoff note says delegated managers may approve access. The rule changes for one customer tier. A later agent reads the old note perfectly and makes a coherent change that reopens the forbidden path.
The retained sentence does not say which source authorized it, which policy version it described, when it became effective or who owns exceptions. More tokens cannot supply missing provenance.
Keep a versioned decision record beside the code. When the next worker acts, compare that record with the current signed policy and run the protected tier-specific denial case.
Make policy updates mark affected memories stale and require a fresh source read at the action boundary. Do this because persistent context helps only when the worker can tell whether the remembered conclusion still applies.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Four-beat scene transcript
1. A long context can remember the wrong rule.
A handoff note says delegated managers may approve access. The rule changes for one customer tier. A later agent reads the old note perfectly and makes a coherent change that reopens the forbidden path.
Visual: Persistence does not make a statement current.
2. The note has no validity envelope.
The retained sentence does not say which source authorized it, which policy version it described, when it became effective or who owns exceptions. More tokens cannot supply missing provenance.
Visual: It lacks the facts needed to challenge it.
3. Record a decision, not just a summary.
Keep a versioned decision record beside the code. When the next worker acts, compare that record with the current signed policy and run the protected tier-specific denial case.
Visual: Source, version, time, exception and owner travel together.
4. Memory needs invalidation.
Make policy updates mark affected memories stale and require a fresh source read at the action boundary. Do this because persistent context helps only when the worker can tell whether the remembered conclusion still applies.
Visual: Use the fact only after checking its current authority.
Research and claim limits
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.