The quiet accountant behind every heal that overflows and every zap that fizzles.
Most of the surprising moments in Quantum Chess — a heal that hands you a Queen, a zap that does nothing, a piece that suddenly reveals itself without ever being touched — trace back to one rule that never appears on screen. Your side always owns exactly one chess set: 8 Pawns, 2 Knights, 2 Bishops, 2 Rooks, 1 Queen, and 1 King. Not “started with.” Owns, right now, always. Every piece, living or captured, fills exactly one slot in that set in every world consistent with what is known. This bookkeeping is the census, and once you can feel it working, the game stops surprising you and starts obeying you.
Watch it work on a live board →
Because the totals are fixed, any new fact immediately constrains everything else. Confirm two of your pieces as Knights and there are no Knights left to go around — so Knight vanishes from every other piece you own, in the same instant, across the whole board. Establish enough facts and pieces you never moved can collapse entirely, because the census has eliminated every alternative. A background solver recomputes all of this after every move; you don’t manage it by hand, but you can and should anticipate it. This instant, non-local propagation is the entanglement in the design.
A piece in the capture tray isn’t out of the game as far as the census is concerned. It sits there as a definite type and counts against its side’s totals forever. Capture an opponent’s piece and it collapses to its cheapest identity — usually a Pawn — which permanently spends one of their Pawn slots. That has a knock-on effect: with fewer cheap slots left on their side, their remaining pieces can no longer be those cheap types, so the expensive identities concentrate on the survivors. Every capture makes the rest of the enemy army easier to read.
A heal restores a friend’s cheapest missing identity — but only if the census has a slot free. If Pawn is fully claimed elsewhere, the heal can’t hand back a Pawn, so it overflows upward to the next available identity. Heal a bare piece when both your Knights are already accounted for and it might come back as Pawn-or-Bishop instead. Late in a game, with most cheap slots spent, a well-aimed heal can restore Queen — or, when your side has lost every King possibility, King itself. The overflow isn’t a special case; it’s just the census refusing to double-book a slot.
A zap tries to strip a target’s most valuable possibility, but it may only remove an identity cleanly — without forcing a census cascade that would rewrite other pieces. If shedding King from this piece would, through the ledger, illegally alter something elsewhere, the zap skips that identity and tries the next. If nothing can be cleanly removed, the zap fizzles entirely and the target shows a gold shield. Closed groups — N pieces sharing exactly N identities — are the classic example: their identities are load-bearing, so the census protects them until the group is broken from the outside.
The protection on your last King is the census refusing to let the set lose its only King. A zap can remove King while a second maybe-King still exists to absorb the slot, but when a volley would strip King from every remaining holder at once, each affected piece keeps King and the zap falls through to Queen. The set must always contain its King somewhere; the ledger simply won’t balance otherwise.