How to play
The winning condition for Nawabari is precise: every cell, edge, region, and fixed clue satisfies the clue centered rectangle partition completion test. No hidden solution values are printed to justify the result; the rules engine validates the submitted position.
- Before the first move in Nawabari, identify which marks are givens and which controls are decisions. Partition the board into rectangles, each containing one clue whose value counts how many sides of that rectangle touch the outer border. The browser stores that distinction with the seeded opening so a restart never changes the puzzle or deal.
- Use the live board controls to change one legal decision at a time. Partition the board into rectangles, each containing one clue whose value counts how many sides of that rectangle touch the outer border. The runtime validates the resulting state before it records a move or opens a new undo branch.
- The winning condition for Nawabari is precise: every cell, edge, region, and fixed clue satisfies the clue centered rectangle partition completion test. No hidden solution values are printed to justify the result; the rules engine validates the submitted position.
Strategy tips
- For each clue, enumerate rectangles whose number of outer-border sides matches it, then eliminate overlaps by confirming every rectangle contains exactly one clue.
- Counting board-edge cells instead of rectangle sides gives the wrong clue value and can make an otherwise complete partition invalid.
- Use undo to compare the last branch if two completions look plausible, then recheck the exact requirement: every cell, edge, region, and fixed clue satisfies the clue centered rectangle partition completion test. A locally attractive move can still break a distant constraint.