False Resolution
The agent proposes a compromise that addresses each constraint individually but subtly violates one in joint interpretation, shipping as success but discovered as failure at audit.
Problem
The compromise survives the agent's self-check because each constraint is individually addressed at surface level. The violation is in the joint interpretation: e.g. the constraint 'all information in a single encrypted file' is violated by 'three encrypted files', which addresses size + encryption individually but breaks the joint property. The user accepts the compromise because it sounds plausible, and discovers the violation downstream (often during audit).
Solution
Pair with: priority-matrix-conflict-resolution (the resolution pattern), conflict-competency-gap (the underlying limitation), decision-paralysis (the sibling failure mode). At review time, treat 'compromise that addresses each constraint individually' as a red flag and check joint satisfaction explicitly.
When to use
- Never. Cite as a known failure mode for sophisticated LLMs on multi-objective input.
- Use as a code-review red flag for agent-proposed 'compromises'.
- Surface in design reviews of multi-objective workloads.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.