FAILURE MAP
← Case archive

FA-100112 / Preference pair construction / Member archive

Preference pairs: stale annotation revisions remain active · case 02

stale annotation revisions remain active.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Rows are [pair_id,revision,chosen,rejected,valid], with unique revisions per pair. Latest revision wins regardless of validity; emit chosen/rejected only when that latest row is valid, otherwise None. Pair order is first-seen.

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
later reversal[["p2", "a", "b"]][["p2", "b", "a"]]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 ↗