FAILURE MAP
← Case archive

FA-83088 / Go territory scoring / Member archive

Atari report order depends on scan order · case 03

Reports are emitted in row-major discovery order instead of sorted order.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

Input a board. Report every chain with exactly one distinct liberty as [colour, lib_row, lib_col, chain_size], sorted ascending.

Why this case matters

Go servers and scoring tools compute this value automatically; a wrong answer changes a game result.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
atari case 2[["W", 2, 0, 1], ["B", 2, 1, 1]][["B", 2, 1, 1], ["W", 2, 0, 1]]Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗