FAILURE MAP

Understand the failure.
Verify the repair.

Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.

Explore the cases ↓How results are verified ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

WHAT THE ARCHIVE CONTAINS

100840 executable cases. 20168 are open.

Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.

The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗

A RECORD OF WHAT WENT WRONG

Browse the archive / 100840

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-82901

Opponent stones are treated as liberties · case 01

Surrounded chains are never captured and some suicides are accepted.

Go territory scoring● Open access↗
FA-82902

Opponent stones are treated as liberties · case 02

Surrounded chains are never captured and some suicides are accepted.

Go territory scoring◈ Members↗
FA-82903

Opponent stones are treated as liberties · case 03

Surrounded chains are never captured and some suicides are accepted.

Go territory scoring◈ Members↗
FA-82904

Opponent stones are treated as liberties · case 04

Surrounded chains are never captured and some suicides are accepted.

Go territory scoring◈ Members↗
FA-82905

Opponent stones are treated as liberties · case 05

Surrounded chains are never captured and some suicides are accepted.

Go territory scoring◈ Members↗
FA-82906

Ko ban is set when the capturing stone joins a friendly chain · case 01

A single-stone capture by a connected stone forbids an immediate recapture that is actually legal.

Go territory scoring● Open access↗
FA-82907

Ko ban is set when the capturing stone joins a friendly chain · case 02

A single-stone capture by a connected stone forbids an immediate recapture that is actually legal.

Go territory scoring◈ Members↗
FA-82908

Ko ban is set when the capturing stone joins a friendly chain · case 03

A single-stone capture by a connected stone forbids an immediate recapture that is actually legal.

Go territory scoring◈ Members↗
FA-82909

Ko ban is set when the capturing stone joins a friendly chain · case 04

A single-stone capture by a connected stone forbids an immediate recapture that is actually legal.

Go territory scoring◈ Members↗
FA-82910

Ko ban is set when the capturing stone joins a friendly chain · case 05

A single-stone capture by a connected stone forbids an immediate recapture that is actually legal.

Go territory scoring◈ Members↗
FA-82911

Ko is declared although the capturing stone has several liberties · case 01

Snapback-style single captures with open points around are flagged as ko.

Go territory scoring● Open access↗
FA-82912

Ko is declared although the capturing stone has several liberties · case 02

Snapback-style single captures with open points around are flagged as ko.

Go territory scoring◈ Members↗
FA-82913

Ko is declared although the capturing stone has several liberties · case 03

Snapback-style single captures with open points around are flagged as ko.

Go territory scoring◈ Members↗
FA-82914

Ko is declared although the capturing stone has several liberties · case 04

Snapback-style single captures with open points around are flagged as ko.

Go territory scoring◈ Members↗
FA-82915

Ko is declared although the capturing stone has several liberties · case 05

Snapback-style single captures with open points around are flagged as ko.

Go territory scoring◈ Members↗
FA-82916

Multi-stone captures create a ko ban · case 01

Capturing two stones marks the first captured point as a ko point.

Go territory scoring● Open access↗
FA-82917

Multi-stone captures create a ko ban · case 02

Capturing two stones marks the first captured point as a ko point.

Go territory scoring◈ Members↗
FA-82918

Multi-stone captures create a ko ban · case 03

Capturing two stones marks the first captured point as a ko point.

Go territory scoring◈ Members↗
FA-82919

Multi-stone captures create a ko ban · case 04

Capturing two stones marks the first captured point as a ko point.

Go territory scoring◈ Members↗
FA-82920

Multi-stone captures create a ko ban · case 05

Capturing two stones marks the first captured point as a ko point.

Go territory scoring◈ Members↗
FA-82921

Superko only compares against the position before the last move · case 01

Triple ko and longer cycles are accepted as legal.

Go territory scoring● Open access↗
FA-82922

Superko only compares against the position before the last move · case 02

Triple ko and longer cycles are accepted as legal.

Go territory scoring◈ Members↗
FA-82923

Superko only compares against the position before the last move · case 03

Triple ko and longer cycles are accepted as legal.

Go territory scoring◈ Members↗
FA-82924

Superko only compares against the position before the last move · case 04

Triple ko and longer cycles are accepted as legal.

Go territory scoring◈ Members↗
FA-82925

Superko only compares against the position before the last move · case 05

Triple ko and longer cycles are accepted as legal.

Go territory scoring◈ Members↗
FA-82926

Situational superko ignores whose turn it is · case 01

Repeating a position with a different player to move is rejected in situational mode.

Go territory scoring● Open access↗
FA-82927

Situational superko ignores whose turn it is · case 02

Repeating a position with a different player to move is rejected in situational mode.

Go territory scoring◈ Members↗
FA-82928

Situational superko ignores whose turn it is · case 03

Repeating a position with a different player to move is rejected in situational mode.

Go territory scoring◈ Members↗
FA-82929

Situational superko ignores whose turn it is · case 04

Repeating a position with a different player to move is rejected in situational mode.

Go territory scoring◈ Members↗
FA-82930

Situational superko ignores whose turn it is · case 05

Repeating a position with a different player to move is rejected in situational mode.

Go territory scoring◈ Members↗
FA-82931

Superko reports the most recent repeat instead of the first · case 01

The reported conflicting move number points at a later repetition.

Go territory scoring● Open access↗
FA-82932

Superko reports the most recent repeat instead of the first · case 02

The reported conflicting move number points at a later repetition.

Go territory scoring◈ Members↗
FA-82933

Superko reports the most recent repeat instead of the first · case 03

The reported conflicting move number points at a later repetition.

Go territory scoring◈ Members↗
FA-82934

Superko reports the most recent repeat instead of the first · case 04

The reported conflicting move number points at a later repetition.

Go territory scoring◈ Members↗
FA-82935

Superko reports the most recent repeat instead of the first · case 05

The reported conflicting move number points at a later repetition.

Go territory scoring◈ Members↗
FA-82936

The candidate position is appended to history before it is checked · case 01

Every move is reported as repeating itself.

Go territory scoring● Open access↗
FA-82937

The candidate position is appended to history before it is checked · case 02

Every move is reported as repeating itself.

Go territory scoring◈ Members↗
FA-82938

The candidate position is appended to history before it is checked · case 03

Every move is reported as repeating itself.

Go territory scoring◈ Members↗
FA-82939

The candidate position is appended to history before it is checked · case 04

Every move is reported as repeating itself.

Go territory scoring◈ Members↗
FA-82940

The candidate position is appended to history before it is checked · case 05

Every move is reported as repeating itself.

Go territory scoring◈ Members↗
FA-82941

13x13 handicap stones land on the third line · case 01

Handicap on 13x13 uses 3-3 points instead of 4-4 points.

Go territory scoring● Open access↗
FA-82942

13x13 handicap stones land on the third line · case 02

Handicap on 13x13 uses 3-3 points instead of 4-4 points.

Go territory scoring◈ Members↗
FA-82943

13x13 handicap stones land on the third line · case 03

Handicap on 13x13 uses 3-3 points instead of 4-4 points.

Go territory scoring◈ Members↗
FA-82944

13x13 handicap stones land on the third line · case 04

Handicap on 13x13 uses 3-3 points instead of 4-4 points.

Go territory scoring◈ Members↗
FA-82945

13x13 handicap stones land on the third line · case 05

Handicap on 13x13 uses 3-3 points instead of 4-4 points.

Go territory scoring◈ Members↗
FA-82946

A one-stone handicap places a stone · case 01

Handicap 1 (no komi, black first) puts a black stone on the board.

Go territory scoring● Open access↗
FA-82947

A one-stone handicap places a stone · case 02

Handicap 1 (no komi, black first) puts a black stone on the board.

Go territory scoring◈ Members↗
FA-82948

A one-stone handicap places a stone · case 03

Handicap 1 (no komi, black first) puts a black stone on the board.

Go territory scoring◈ Members↗
FA-82949

A one-stone handicap places a stone · case 04

Handicap 1 (no komi, black first) puts a black stone on the board.

Go territory scoring◈ Members↗
FA-82950

A one-stone handicap places a stone · case 05

Handicap 1 (no komi, black first) puts a black stone on the board.

Go territory scoring◈ Members↗
FA-82951

Six-stone handicap uses top and bottom side points · case 01

The fifth and sixth stones sit on the top/bottom edges instead of left/right.

Go territory scoring● Open access↗
FA-82952

Six-stone handicap uses top and bottom side points · case 02

The fifth and sixth stones sit on the top/bottom edges instead of left/right.

Go territory scoring◈ Members↗
FA-82953

Six-stone handicap uses top and bottom side points · case 03

The fifth and sixth stones sit on the top/bottom edges instead of left/right.

Go territory scoring◈ Members↗
FA-82954

Six-stone handicap uses top and bottom side points · case 04

The fifth and sixth stones sit on the top/bottom edges instead of left/right.

Go territory scoring◈ Members↗
FA-82955

Six-stone handicap uses top and bottom side points · case 05

The fifth and sixth stones sit on the top/bottom edges instead of left/right.

Go territory scoring◈ Members↗
FA-82956

Even handicaps get a centre stone · case 01

Six- and eight-stone handicaps receive tengen as an extra stone.

Go territory scoring● Open access↗
FA-82957

Even handicaps get a centre stone · case 02

Six- and eight-stone handicaps receive tengen as an extra stone.

Go territory scoring◈ Members↗
FA-82958

Even handicaps get a centre stone · case 03

Six- and eight-stone handicaps receive tengen as an extra stone.

Go territory scoring◈ Members↗
FA-82959

Even handicaps get a centre stone · case 04

Six- and eight-stone handicaps receive tengen as an extra stone.

Go territory scoring◈ Members↗
FA-82960

Even handicaps get a centre stone · case 05

Six- and eight-stone handicaps receive tengen as an extra stone.

Go territory scoring◈ Members↗
FA-82961

Even-sized boards receive side and centre handicap stones · case 01

A 10x10 board with 5+ handicap gets off-centre "tengen" stones.

Go territory scoring● Open access↗
FA-82962

Even-sized boards receive side and centre handicap stones · case 02

A 10x10 board with 5+ handicap gets off-centre "tengen" stones.

Go territory scoring◈ Members↗
FA-82963

Even-sized boards receive side and centre handicap stones · case 03

A 10x10 board with 5+ handicap gets off-centre "tengen" stones.

Go territory scoring◈ Members↗
FA-82964

Even-sized boards receive side and centre handicap stones · case 04

A 10x10 board with 5+ handicap gets off-centre "tengen" stones.

Go territory scoring◈ Members↗
FA-82965

Even-sized boards receive side and centre handicap stones · case 05

A 10x10 board with 5+ handicap gets off-centre "tengen" stones.

Go territory scoring◈ Members↗
FA-82966

Two-stone handicap uses the wrong diagonal · case 01

The first two stones go to upper-left and lower-right.

Go territory scoring● Open access↗
FA-82967

Two-stone handicap uses the wrong diagonal · case 02

The first two stones go to upper-left and lower-right.

Go territory scoring◈ Members↗
FA-82968

Two-stone handicap uses the wrong diagonal · case 03

The first two stones go to upper-left and lower-right.

Go territory scoring◈ Members↗
FA-82969

Two-stone handicap uses the wrong diagonal · case 04

The first two stones go to upper-left and lower-right.

Go territory scoring◈ Members↗
FA-82970

Two-stone handicap uses the wrong diagonal · case 05

The first two stones go to upper-left and lower-right.

Go territory scoring◈ Members↗
FA-82971

Columns after H are shifted because I is not skipped · case 01

J10 is parsed one column too far right and I5 is accepted.

Go territory scoring● Open access↗
FA-82972

Columns after H are shifted because I is not skipped · case 02

J10 is parsed one column too far right and I5 is accepted.

Go territory scoring◈ Members↗
FA-82973

Columns after H are shifted because I is not skipped · case 03

J10 is parsed one column too far right and I5 is accepted.

Go territory scoring◈ Members↗
FA-82974

Columns after H are shifted because I is not skipped · case 04

J10 is parsed one column too far right and I5 is accepted.

Go territory scoring◈ Members↗
FA-82975

Columns after H are shifted because I is not skipped · case 05

J10 is parsed one column too far right and I5 is accepted.

Go territory scoring◈ Members↗
FA-82976

GTP row numbers are read from the top edge · case 01

D4 lands on the fourth row from the top instead of the bottom.

Go territory scoring● Open access↗
FA-82977

GTP row numbers are read from the top edge · case 02

D4 lands on the fourth row from the top instead of the bottom.

Go territory scoring◈ Members↗
FA-82978

GTP row numbers are read from the top edge · case 03

D4 lands on the fourth row from the top instead of the bottom.

Go territory scoring◈ Members↗
FA-82979

GTP row numbers are read from the top edge · case 04

D4 lands on the fourth row from the top instead of the bottom.

Go territory scoring◈ Members↗
FA-82980

GTP row numbers are read from the top edge · case 05

D4 lands on the fourth row from the top instead of the bottom.

Go territory scoring◈ Members↗
FA-82981

Lower-case vertices and "pass" are rejected · case 01

Engines sending d4 or pass get "invalid".

Go territory scoring● Open access↗
FA-82982

Lower-case vertices and "pass" are rejected · case 02

Engines sending d4 or pass get "invalid".

Go territory scoring◈ Members↗
FA-82983

Lower-case vertices and "pass" are rejected · case 03

Engines sending d4 or pass get "invalid".

Go territory scoring◈ Members↗
FA-82984

Lower-case vertices and "pass" are rejected · case 04

Engines sending d4 or pass get "invalid".

Go territory scoring◈ Members↗
FA-82985

Lower-case vertices and "pass" are rejected · case 05

Engines sending d4 or pass get "invalid".

Go territory scoring◈ Members↗
FA-82986

Column one past the board edge or row zero is accepted · case 01

Vertices outside the board are converted to coordinates.

Go territory scoring● Open access↗
FA-82987

Column one past the board edge or row zero is accepted · case 02

Vertices outside the board are converted to coordinates.

Go territory scoring◈ Members↗
FA-82988

Column one past the board edge or row zero is accepted · case 03

Vertices outside the board are converted to coordinates.

Go territory scoring◈ Members↗
FA-82989

Column one past the board edge or row zero is accepted · case 04

Vertices outside the board are converted to coordinates.

Go territory scoring◈ Members↗
FA-82990

Column one past the board edge or row zero is accepted · case 05

Vertices outside the board are converted to coordinates.

Go territory scoring◈ Members↗
FA-82991

tt is treated as a pass on boards larger than 19x19 · case 01

A real move at column 20 row 20 on a 21x21 board is dropped as a pass.

Go territory scoring● Open access↗
FA-82992

tt is treated as a pass on boards larger than 19x19 · case 02

A real move at column 20 row 20 on a 21x21 board is dropped as a pass.

Go territory scoring◈ Members↗
FA-82993

tt is treated as a pass on boards larger than 19x19 · case 03

A real move at column 20 row 20 on a 21x21 board is dropped as a pass.

Go territory scoring◈ Members↗
FA-82994

tt is treated as a pass on boards larger than 19x19 · case 04

A real move at column 20 row 20 on a 21x21 board is dropped as a pass.

Go territory scoring◈ Members↗
FA-82995

tt is treated as a pass on boards larger than 19x19 · case 05

A real move at column 20 row 20 on a 21x21 board is dropped as a pass.

Go territory scoring◈ Members↗
FA-82996

SGF column and row are returned swapped · case 01

Moves are mirrored across the main diagonal.

Go territory scoring● Open access↗
FA-82997

SGF column and row are returned swapped · case 02

Moves are mirrored across the main diagonal.

Go territory scoring◈ Members↗
FA-82998

SGF column and row are returned swapped · case 03

Moves are mirrored across the main diagonal.

Go territory scoring◈ Members↗
FA-82999

SGF column and row are returned swapped · case 04

Moves are mirrored across the main diagonal.

Go territory scoring◈ Members↗
FA-83000

SGF column and row are returned swapped · case 05

Moves are mirrored across the main diagonal.

Go territory scoring◈ Members↗

INSPECTABLE BY DESIGN

Every result has a runnable source.

Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.

Read the methodology ↗