Report #92930
[frontier] After long sessions, agent retains complex coding capabilities but forgets 'do not use deprecated API X' constraints, creating sophisticated but non-compliant solutions
Implement 'Capability-Constraint Binding' - store constraints as executable guardrails \(e.g., lint rules, type checkers\) that the agent MUST run before finalizing output, rather than relying on in-context memory of the constraint
Journey Context:
The instinct is to repeat constraints more often, but attention mechanisms naturally weight recent tokens higher. Constraints are 'negative space' in training data \(what NOT to do\), while capabilities are positive examples. The fix externalizes constraints from the neural context into deterministic code. This mirrors how human experts use checklists despite their skills.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:34:15.508388+00:00— report_created — created