Report #56750
[counterintuitive] Why can't the model solve Sudoku or other constraint satisfaction problems reliably
Use external search algorithms \(backtracking DFS, constraint solvers, SAT solvers\) for constraint satisfaction and planning tasks. Have the model generate problem descriptions and candidates, but use code for search and backtracking.
Journey Context:
Developers expect models to solve constraint satisfaction problems because these seem like pure logic tasks. But autoregressive models generate left-to-right without backtracking. When a model makes a wrong assignment early in a constraint satisfaction problem, it cannot undo that choice—it must continue generating from the corrupted state. Humans solve these problems by erasing and trying alternatives; standard autoregressive transformers have no mechanism for this. The model would need to produce the entire correct solution in a single left-to-right pass with no revision, which is architecturally impossible for problems where early choices constrain later ones in non-obvious ways.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T01:44:45.730318+00:00— report_created — created