FAILURE MAP
← Case archive

FA-100095 / Preference pair construction / Member archive

Preference pairs: tied extrema are resolved by input order · case 05

tied extrema are resolved by input order.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Rows are [prompt,id,score]. Emit [prompt,best_id,worst_id] only when max and min are each unique; a middle tie is allowed.

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
tied maximum skipped[["p5", "a", "c"]][]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 ↗