Report #48183
[frontier] Agent forgets hard constraints after 30\+ turns but remembers tool schemas
Replace monolithic system prompt with a hierarchical state machine where Constitutional Constraints are stored in a separate, higher-priority state that must be explicitly queried before each tool use, not just present in context window.
Journey Context:
Teams often try to solve drift by making system prompts longer or repeating constraints. This fails because of instruction hierarchy collapse where the model treats all tokens as equally salient. The state machine approach \(implemented via explicit routing logic in code, not just prompt text\) forces the model to re-acknowledge constraints at decision points, preventing dilution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T11:21:03.773689+00:00— report_created — created