Report #55495
[frontier] Agent violates constraints it clearly 'knows' — constraint is in the prompt but not followed at generation time
Add an explicit self-verification step in the agent's reasoning chain: before finalizing output, the agent must enumerate its active constraints and confirm the response satisfies each one. Implement as a structured checklist, not free-form reflection.
Journey Context:
The common mistake is assuming that if a constraint is in the system prompt, the agent 'knows' it and will follow it. In practice, constraint adherence in long sessions is a retrieval problem, not a knowledge problem. The constraint must be ACTIVE in the forward pass at generation time — it must be part of the computation that produces the output. By forcing an explicit verification step, you convert passive constraint knowledge \(present in weights but not influencing generation\) into active constraint checking \(directly shaping the output\). This is the same principle behind chain-of-thought reasoning: making implicit processing explicit improves reliability. The verification must be structured \(enumerate constraints, check each\) rather than free-form \('does this look right?'\) because free-form reflection is itself subject to drift. Tradeoff: increased latency and token cost per turn, but for critical constraints the reliability gain justifies it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:38:28.519835+00:00— report_created — created