The Verification Venue · Pattern · machine-checked

The Mutilated Chessboard

Snip two opposite corners off a chessboard. Sixty-two squares remain — an even number, room for exactly thirty-one dominoes. Lay them down and you will never cover the board. Not because you weren't clever enough: because of colour. Try it below, watch it leave at least two squares uncovered, then turn the colours on and see why: a one-line argument that needs no search, and is checked here by a machine.

Covered
0 / 62
Light left
30
Dark left
32
Holes
2

What just happened

The puzzle looks fair. Sixty-two squares, an even number; thirty-one dominoes, each covering two squares; 62 = 2 × 31. Nothing about the count forbids it. And there are vast numbers of ways to lay dominoes — the intact 8×8 board can be tiled in 12,988,816 different ways. Surely one of them dodges the two gaps?

None does, and the reason ignores the search entirely. Turn on Show the colours and look at the two squares you removed: they are the same colour. That is the whole story. Colour the board like a chessboard. Every domino — horizontal or vertical, anywhere — sits on two adjacent squares, and adjacent squares always have opposite colours. So every domino covers exactly one light square and one dark square. A full tiling of 31 dominoes would therefore cover exactly 31 light and 31 dark. But the two opposite corners are both light, so cutting them off leaves 30 light and 32 dark. Thirty cannot pair with thirty-two. No tiling exists — and no amount of cleverness will change a count.

This is a parity invariant: a quantity (here, light − dark) that every legal move leaves unchanged, but the goal demands you change. Place a domino and the count of uncovered light and uncovered dark each drop by one; the difference never moves off -2. You can shuffle dominoes forever; you can never make 30 equal 32. You cannot pair every one of thirty light squares with every one of thirty-two dark squares.

So when can you do it?

Switch to Pick the two holes and remove a different pair of squares, then press Auto-solve. You'll find the dividing line is purely colour: remove two squares of opposite colour and the rest always tiles; remove two of the same colour and it never does — no matter where on the board they sit. The colouring argument forbids the same-colour case. The opposite-colour case is a real theorem too (Gomory, reported by Gardner in November 1962): thread a single closed loop through all 64 squares visiting each once; removing one light and one dark square cuts the loop into two arcs of even length, and each arc tiles by taking alternate steps. Either way, the board itself tells you the answer the instant you press solve — it runs an exact matching, not a guess.

Show the check

Here are the mathematical checks. The board decides tileability by exact bipartite matching (a region of 2k squares tiles iff its maximum matching has k dominoes) — the same code runs offline in research/the-mutilated-chessboard/verify.mjs, which checks all 2016 ways of removing two squares and confirms the region tiles if and only if the two removed squares differ in colour — 2016/2016, no exceptions — and recomputes the 12,988,816 tilings of the intact board (Kasteleyn). And the impossibility direction is machine-checked in Lean: research/the-mutilated-chessboard/lean/MutilatedChessboard.lean proves that no list of dominoes can cover exactly this 8×8 board with (0,0) and (7,7) removed, by the colour invariant, with zero imports and axiom footprint [propext, Quot.sound]. The proof rules out every candidate tiling of that fixed board.

This is the quiet power of an invariant. An exhaustive search can rule out a tiling: Knuth reports a completed search of the mutilated board. The colouring settles the impossibility in a sentence. For this 8×8 board, it forbids any two holes of one colour; Gomory's closed-loop construction supplies a tiling when one hole is of each colour. The same shape of invariant argument proves you can't always solve the 15-puzzle, can't tile other deficient boards, can't reach certain states of a Rubik's cube. Find the invariant and the search evaporates.

What is, and isn't, claimed

The claims record 93 claims re-read against their sources, 14 October 2026

Written 2026-06-30. Claims re-read against their sources on 2026-10-14: 93 checked, 60 confirmed, 32 wrong, 0 unverifiable, 1 true when written and overtaken since (dated, not corrected). By the assay line (research/assay-line/cited-1014b/), Codex fixer directed by claude-assaying-boyle-1014; source record by Codex, checked by Codex.

This was the directed fixing pass over all 33 triage items at f5e5f84f34, with each item's evidence reread before editing, the live-script counterexamples replayed, and the checker's 60 CONFIRMED rereads retained with their provenance. All 22 WRONG and 10 MINOR items were repaired in the authorised layer files; MINOR counts toward wrong here. The sole STALE item updates JSON-LD dateModified under the explicit exception. Twelve distinct WRONG corrections are dated on the page and mirrored in the Markdown body. The findings below describe those layer repairs, not a complete re-audit of the checker's 47 observations or its separate untriaged UNVERIFIABLE attribution. Repair review by Codex, 2026-10-14: all four remaining copy problems in fixcheck.md are supported. The target-layer repairs stand, but 15 affected triage findings remain open for shared TV narration, other layers' authored notes, and preserved corpus quotations in There, Here. Claim verdicts and counts are unchanged: 60 CONFIRMED + 22 WRONG + 10 MINOR + 1 STALE = 93. The repair report holds the evidence and four proposed board notes at research/assay-line/cited-1014b/the-mutilated-chessboard/repair-report.md.

This record is long (93 claim lines and 33 findings), so it is not part of the page until you open it. It loads here now if your browser runs scripts; otherwise, or to keep it, read the whole record as plain text.

The assay office: what a record is, and every layer re-read so far.