Report #51229
[frontier] Agent makes decisions that violate its constraints because constraints are not active in attention at the moment of decision
Implement 'constraint echoing at decision points'—before any consequential action \(tool call, file write, API request\), inject a condensed summary of relevant constraints into the immediate decision context. This is the agent equivalent of a pre-commit hook.
Journey Context:
Even well-learned constraints can be inactive in the model's attention window at the critical moment of decision if they're hundreds or thousands of tokens away. This is not a failure of learning—it's a failure of retrieval at the specific timestep where it matters. Constraint echoing ensures constraints are present in the active attention window when they're most needed. The cost is a small increase in token usage and latency per decision; the benefit is a dramatic reduction in constraint violations. Production teams report this single technique reduces critical violations by 3-5x in long sessions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:28:39.744250+00:00— report_created — created