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-98501

Beam search: completed pool is capped by discovery order · case 01

completed pool is capped by discovery order.

Beam search bookkeeping● Open access↗
FA-98502

Beam search: completed pool is capped by discovery order · case 02

completed pool is capped by discovery order.

Beam search bookkeeping◈ Members↗
FA-98503

Beam search: completed pool is capped by discovery order · case 03

completed pool is capped by discovery order.

Beam search bookkeeping◈ Members↗
FA-98504

Beam search: completed pool is capped by discovery order · case 04

completed pool is capped by discovery order.

Beam search bookkeeping◈ Members↗
FA-98505

Beam search: completed pool is capped by discovery order · case 05

completed pool is capped by discovery order.

Beam search bookkeeping◈ Members↗
FA-98506

Beam search: equal beam scores depend on incidental input order · case 01

equal beam scores depend on incidental input order.

Beam search bookkeeping● Open access↗
FA-98507

Beam search: equal beam scores depend on incidental input order · case 02

equal beam scores depend on incidental input order.

Beam search bookkeeping◈ Members↗
FA-98508

Beam search: equal beam scores depend on incidental input order · case 03

equal beam scores depend on incidental input order.

Beam search bookkeeping◈ Members↗
FA-98509

Beam search: equal beam scores depend on incidental input order · case 04

equal beam scores depend on incidental input order.

Beam search bookkeeping◈ Members↗
FA-98510

Beam search: equal beam scores depend on incidental input order · case 05

equal beam scores depend on incidental input order.

Beam search bookkeeping◈ Members↗
FA-98511

Beam search: duplicate token paths occupy multiple beam slots · case 01

duplicate token paths occupy multiple beam slots.

Beam search bookkeeping● Open access↗
FA-98512

Beam search: duplicate token paths occupy multiple beam slots · case 02

duplicate token paths occupy multiple beam slots.

Beam search bookkeeping◈ Members↗
FA-98513

Beam search: duplicate token paths occupy multiple beam slots · case 03

duplicate token paths occupy multiple beam slots.

Beam search bookkeeping◈ Members↗
FA-98514

Beam search: duplicate token paths occupy multiple beam slots · case 04

duplicate token paths occupy multiple beam slots.

Beam search bookkeeping◈ Members↗
FA-98515

Beam search: duplicate token paths occupy multiple beam slots · case 05

duplicate token paths occupy multiple beam slots.

Beam search bookkeeping◈ Members↗
FA-98516

Beam search: zero-width search retains one live hypothesis · case 01

zero-width search retains one live hypothesis.

Beam search bookkeeping● Open access↗
FA-98517

Beam search: zero-width search retains one live hypothesis · case 02

zero-width search retains one live hypothesis.

Beam search bookkeeping◈ Members↗
FA-98518

Beam search: zero-width search retains one live hypothesis · case 03

zero-width search retains one live hypothesis.

Beam search bookkeeping◈ Members↗
FA-98519

Beam search: zero-width search retains one live hypothesis · case 04

zero-width search retains one live hypothesis.

Beam search bookkeeping◈ Members↗
FA-98520

Beam search: zero-width search retains one live hypothesis · case 05

zero-width search retains one live hypothesis.

Beam search bookkeeping◈ Members↗
FA-98521

Beam search: child ancestry points to sorted candidate position rather than source parent · case 01

child ancestry points to sorted candidate position rather than source parent.

Beam search bookkeeping● Open access↗
FA-98522

Beam search: child ancestry points to sorted candidate position rather than source parent · case 02

child ancestry points to sorted candidate position rather than source parent.

Beam search bookkeeping◈ Members↗
FA-98523

Beam search: child ancestry points to sorted candidate position rather than source parent · case 03

child ancestry points to sorted candidate position rather than source parent.

Beam search bookkeeping◈ Members↗
FA-98524

Beam search: child ancestry points to sorted candidate position rather than source parent · case 04

child ancestry points to sorted candidate position rather than source parent.

Beam search bookkeeping◈ Members↗
FA-98525

Beam search: child ancestry points to sorted candidate position rather than source parent · case 05

child ancestry points to sorted candidate position rather than source parent.

Beam search bookkeeping◈ Members↗
FA-98526

Beam search: completed paths are expanded again as live beams · case 01

completed paths are expanded again as live beams.

Beam search bookkeeping● Open access↗
FA-98527

Beam search: completed paths are expanded again as live beams · case 02

completed paths are expanded again as live beams.

Beam search bookkeeping◈ Members↗
FA-98528

Beam search: completed paths are expanded again as live beams · case 03

completed paths are expanded again as live beams.

Beam search bookkeeping◈ Members↗
FA-98529

Beam search: completed paths are expanded again as live beams · case 04

completed paths are expanded again as live beams.

Beam search bookkeeping◈ Members↗
FA-98530

Beam search: completed paths are expanded again as live beams · case 05

completed paths are expanded again as live beams.

Beam search bookkeeping◈ Members↗
FA-98531

Beam search: length counter advances for prompt positions · case 01

length counter advances for prompt positions.

Beam search bookkeeping● Open access↗
FA-98532

Beam search: length counter advances for prompt positions · case 02

length counter advances for prompt positions.

Beam search bookkeeping◈ Members↗
FA-98533

Beam search: length counter advances for prompt positions · case 03

length counter advances for prompt positions.

Beam search bookkeeping◈ Members↗
FA-98534

Beam search: length counter advances for prompt positions · case 04

length counter advances for prompt positions.

Beam search bookkeeping◈ Members↗
FA-98535

Beam search: length counter advances for prompt positions · case 05

length counter advances for prompt positions.

Beam search bookkeeping◈ Members↗
FA-98536

Beam search: beam stopping ignores the best normalized score a live path can still reach · case 01

beam stopping ignores the best normalized score a live path can still reach.

Beam search bookkeeping● Open access↗
FA-98537

Beam search: beam stopping ignores the best normalized score a live path can still reach · case 02

beam stopping ignores the best normalized score a live path can still reach.

Beam search bookkeeping◈ Members↗
FA-98538

Beam search: beam stopping ignores the best normalized score a live path can still reach · case 03

beam stopping ignores the best normalized score a live path can still reach.

Beam search bookkeeping◈ Members↗
FA-98539

Beam search: beam stopping ignores the best normalized score a live path can still reach · case 04

beam stopping ignores the best normalized score a live path can still reach.

Beam search bookkeeping◈ Members↗
FA-98540

Beam search: beam stopping ignores the best normalized score a live path can still reach · case 05

beam stopping ignores the best normalized score a live path can still reach.

Beam search bookkeeping◈ Members↗
FA-98541

Absolute positions map relative to the cache origin · case 01

Writes land at an absolute index instead of an index relative to the cache origin.

KV cache position mapping● Open access↗
FA-98542

Absolute positions map relative to the cache origin · case 02

Writes land at an absolute index instead of an index relative to the cache origin.

KV cache position mapping◈ Members↗
FA-98543

Absolute positions map relative to the cache origin · case 03

Writes land at an absolute index instead of an index relative to the cache origin.

KV cache position mapping◈ Members↗
FA-98544

Absolute positions map relative to the cache origin · case 04

Writes land at an absolute index instead of an index relative to the cache origin.

KV cache position mapping◈ Members↗
FA-98545

Absolute positions map relative to the cache origin · case 05

Writes land at an absolute index instead of an index relative to the cache origin.

KV cache position mapping◈ Members↗
FA-98546

Ring writes wrap at capacity · case 01

A cache write past the final slot escapes the circular buffer.

KV cache position mapping● Open access↗
FA-98547

Ring writes wrap at capacity · case 02

A cache write past the final slot escapes the circular buffer.

KV cache position mapping◈ Members↗
FA-98548

Ring writes wrap at capacity · case 03

A cache write past the final slot escapes the circular buffer.

KV cache position mapping◈ Members↗
FA-98549

Ring writes wrap at capacity · case 04

A cache write past the final slot escapes the circular buffer.

KV cache position mapping◈ Members↗
FA-98550

Ring writes wrap at capacity · case 05

A cache write past the final slot escapes the circular buffer.

KV cache position mapping◈ Members↗
FA-98551

Ring slots are read in logical order · case 01

Physical slot order is returned as if it were chronological order.

KV cache position mapping● Open access↗
FA-98552

Ring slots are read in logical order · case 02

Physical slot order is returned as if it were chronological order.

KV cache position mapping◈ Members↗
FA-98553

Ring slots are read in logical order · case 03

Physical slot order is returned as if it were chronological order.

KV cache position mapping◈ Members↗
FA-98554

Ring slots are read in logical order · case 04

Physical slot order is returned as if it were chronological order.

KV cache position mapping◈ Members↗
FA-98555

Ring slots are read in logical order · case 05

Physical slot order is returned as if it were chronological order.

KV cache position mapping◈ Members↗
FA-98556

Paged cache position selects the correct block · case 01

A logical position at a page boundary is assigned to the preceding block.

KV cache position mapping● Open access↗
FA-98557

Paged cache position selects the correct block · case 02

A logical position at a page boundary is assigned to the preceding block.

KV cache position mapping◈ Members↗
FA-98558

Paged cache position selects the correct block · case 03

A logical position at a page boundary is assigned to the preceding block.

KV cache position mapping◈ Members↗
FA-98559

Paged cache position selects the correct block · case 04

A logical position at a page boundary is assigned to the preceding block.

KV cache position mapping◈ Members↗
FA-98560

Paged cache position selects the correct block · case 05

A logical position at a page boundary is assigned to the preceding block.

KV cache position mapping◈ Members↗
FA-98561

Paged cache resolves through the sequence block table · case 01

A logical page is represented by its local offset instead of the physical slot in that page.

KV cache position mapping● Open access↗
FA-98562

Paged cache resolves through the sequence block table · case 02

A logical page is represented by its local offset instead of the physical slot in that page.

KV cache position mapping◈ Members↗
FA-98563

Paged cache resolves through the sequence block table · case 03

A logical page is represented by its local offset instead of the physical slot in that page.

KV cache position mapping◈ Members↗
FA-98564

Paged cache resolves through the sequence block table · case 04

A logical page is represented by its local offset instead of the physical slot in that page.

KV cache position mapping◈ Members↗
FA-98565

Paged cache resolves through the sequence block table · case 05

A logical page is represented by its local offset instead of the physical slot in that page.

KV cache position mapping◈ Members↗
FA-98566

Left padding does not consume logical positions · case 01

Position IDs include the leading pad cells.

KV cache position mapping● Open access↗
FA-98567

Left padding does not consume logical positions · case 02

Position IDs include the leading pad cells.

KV cache position mapping◈ Members↗
FA-98568

Left padding does not consume logical positions · case 03

Position IDs include the leading pad cells.

KV cache position mapping◈ Members↗
FA-98569

Left padding does not consume logical positions · case 04

Position IDs include the leading pad cells.

KV cache position mapping◈ Members↗
FA-98570

Left padding does not consume logical positions · case 05

Position IDs include the leading pad cells.

KV cache position mapping◈ Members↗
FA-98571

Append rejects a discontinuous logical position · case 01

A skipped position is silently written as if it followed the cache tail.

KV cache position mapping● Open access↗
FA-98572

Append rejects a discontinuous logical position · case 02

A skipped position is silently written as if it followed the cache tail.

KV cache position mapping◈ Members↗
FA-98573

Append rejects a discontinuous logical position · case 03

A skipped position is silently written as if it followed the cache tail.

KV cache position mapping◈ Members↗
FA-98574

Append rejects a discontinuous logical position · case 04

A skipped position is silently written as if it followed the cache tail.

KV cache position mapping◈ Members↗
FA-98575

Append rejects a discontinuous logical position · case 05

A skipped position is silently written as if it followed the cache tail.

KV cache position mapping◈ Members↗
FA-98576

Packed segments reset logical positions at boundaries · case 01

A new packed sequence inherits the prior segment’s final position.

KV cache position mapping● Open access↗
FA-98577

Packed segments reset logical positions at boundaries · case 02

A new packed sequence inherits the prior segment’s final position.

KV cache position mapping◈ Members↗
FA-98578

Packed segments reset logical positions at boundaries · case 03

A new packed sequence inherits the prior segment’s final position.

KV cache position mapping◈ Members↗
FA-98579

Packed segments reset logical positions at boundaries · case 04

A new packed sequence inherits the prior segment’s final position.

KV cache position mapping◈ Members↗
FA-98580

Packed segments reset logical positions at boundaries · case 05

A new packed sequence inherits the prior segment’s final position.

KV cache position mapping◈ Members↗
FA-98581

Beam cache rows follow selected parent beams · case 01

Child beams inherit cache rows in their previous row order.

KV cache position mapping● Open access↗
FA-98582

Beam cache rows follow selected parent beams · case 02

Child beams inherit cache rows in their previous row order.

KV cache position mapping◈ Members↗
FA-98583

Beam cache rows follow selected parent beams · case 03

Child beams inherit cache rows in their previous row order.

KV cache position mapping◈ Members↗
FA-98584

Beam cache rows follow selected parent beams · case 04

Child beams inherit cache rows in their previous row order.

KV cache position mapping◈ Members↗
FA-98585

Beam cache rows follow selected parent beams · case 05

Child beams inherit cache rows in their previous row order.

KV cache position mapping◈ Members↗
FA-98586

Sliding eviction retains one stale position · case 01

A key just outside the trailing window remains in the cache.

KV cache position mapping● Open access↗
FA-98587

Sliding eviction retains one stale position · case 02

A key just outside the trailing window remains in the cache.

KV cache position mapping◈ Members↗
FA-98588

Sliding eviction retains one stale position · case 03

A key just outside the trailing window remains in the cache.

KV cache position mapping◈ Members↗
FA-98589

Sliding eviction retains one stale position · case 04

A key just outside the trailing window remains in the cache.

KV cache position mapping◈ Members↗
FA-98590

Sliding eviction retains one stale position · case 05

A key just outside the trailing window remains in the cache.

KV cache position mapping◈ Members↗
FA-98591

Sink tokens survive rolling-window eviction · case 01

Eviction removes the initial sink positions along with stale middle positions.

KV cache position mapping● Open access↗
FA-98592

Sink tokens survive rolling-window eviction · case 02

Eviction removes the initial sink positions along with stale middle positions.

KV cache position mapping◈ Members↗
FA-98593

Sink tokens survive rolling-window eviction · case 03

Eviction removes the initial sink positions along with stale middle positions.

KV cache position mapping◈ Members↗
FA-98594

Sink tokens survive rolling-window eviction · case 04

Eviction removes the initial sink positions along with stale middle positions.

KV cache position mapping◈ Members↗
FA-98595

Sink tokens survive rolling-window eviction · case 05

Eviction removes the initial sink positions along with stale middle positions.

KV cache position mapping◈ Members↗
FA-98596

Prefix reuse reports the common token prefix length · case 01

Reuse stops at the first differing token but reports the final sequence length.

KV cache position mapping● Open access↗
FA-98597

Prefix reuse reports the common token prefix length · case 02

Reuse stops at the first differing token but reports the final sequence length.

KV cache position mapping◈ Members↗
FA-98598

Prefix reuse reports the common token prefix length · case 03

Reuse stops at the first differing token but reports the final sequence length.

KV cache position mapping◈ Members↗
FA-98599

Prefix reuse reports the common token prefix length · case 04

Reuse stops at the first differing token but reports the final sequence length.

KV cache position mapping◈ Members↗
FA-98600

Prefix reuse reports the common token prefix length · case 05

Reuse stops at the first differing token but reports the final sequence length.

KV cache position mapping◈ 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 ↗