FAILURE MAP
← Case archive

FA-100087 / Preference pair construction / Member archive

Preference pairs: only adjacent candidates are paired · case 02

only adjacent candidates are paired.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Candidates are [id,score]. Return every unordered pair [higher_id,lower_id] once; tied scores are skipped. Order follows input index pairs.

Why this case matters

A small deterministic preference-data transform makes pair semantics inspectable without a training framework.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
nonadjacent pair[["a2", "b2"]][["a2", "b2"], ["a2", "c2"], ["c2", "b2"]]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 ↗