Report #35111
[frontier] Why does my agent forget rules but still write perfect code
Recognize the constraint-capability asymmetry: capabilities are weight-embedded and self-reinforcing, constraints are context-embedded and attention-dependent. Design constraint delivery with active maintenance \(repetition, externalization, verification\); capabilities need no such treatment.
Journey Context:
This asymmetry is the root cause of the most insidious form of drift. A coding agent will never 'forget' how to write Python, handle errors, or structure a REST API—those patterns are deeply embedded in the model's weights and are reinforced every time the agent uses them. But it will absolutely forget that you told it to use functional style, avoid certain libraries, or follow a specific naming convention. People waste effort trying to 'reinforce' capabilities that don't need it \(e.g., re-stating 'you are a Python expert'\) while under-investing in constraint persistence. The right call: audit your instructions, separate capabilities from constraints, and allocate 100% of your drift-prevention budget to constraints. Capabilities are free; constraints are expensive.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:24:47.456245+00:00— report_created — created