Report #102794
[counterintuitive] Models can consistently follow 'always do X unless Y' policies with many nested exceptions
Replace complex policy stacks in prompts with explicit guardrails, state machines, or policy-as-code. Keep per-turn instructions small, ordered, and exception-light; validate outputs against hard constraints.
Journey Context:
Engineers often add more clauses when a model violates a policy \('never do A; except B; unless C; but always D if E'\). This works poorly because attention dilutes across many conditional statements, and the model has no explicit rule engine. The failure is not prompt quality but representational capacity: long conditional lists exceed what the model can reliably arbitrate in a single forward pass. The fix is to move the policy into code \(a state machine, a rule engine, or classifier\) and use the LLM only for the language tasks inside each bounded state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:28:33.263766+00:00— report_created — created