FA-100041 / Preference pair construction / Open access

Preference pairs: responses are paired by list position · case 01

responses are paired by list position.

Verified by executionVariant 1 · 6 checks per implementationDownload source bundle ↓JSON ↗

ROOT CAUSE

Candidate response IDs are discarded, so differently ordered annotations attach to the wrong text.

THE FAILURE

Candidate response IDs are discarded, so differently ordered annotations attach to the wrong text.

Unsuccessful approach: Sorting each list independently by ID still misaligns records when one side lacks an ID.

Case contract

Responses and judgments are lists of [id,value]. Return [id,response,judgment] rows for IDs present in both, ordered by response input order.

Why this case matters

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

1 / The failure

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(responses, judgments):
    return [[r[0],r[1],judgments[i][1]] for i,r in enumerate(responses) if i<len(judgments)]
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
a='a'+str(N); b='b'+str(N)
check('reordered judgments',solve([[a,'A'],[b,'B']],[[b,0],[a,1]]),[[a,'A',1],[b,'B',0]])
check('one shared id',solve([[a,'A']],[[a,1]]),[[a,'A',1]])
check('missing judgment',solve([[a,'A'],[b,'B']],[[b,0]]),[[b,'B',0]])
check('no responses',solve([],[[a,1]]),[])
check('no judgments',solve([[a,'A']],[]),[])
check('extra judgment ignored',solve([[a,'A']],[[a,1],[b,0]]),[[a,'A',1]])
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
reordered judgments	`[['a1', 'A', 0], ['b1', 'B', 1]]`	`[['a1', 'A', 1], ['b1', 'B', 0]]`	Failed
one shared id	`[['a1', 'A', 1]]`	`[['a1', 'A', 1]]`	Passed
missing judgment	`[['a1', 'A', 0]]`	`[['b1', 'B', 0]]`	Failed
no responses	`[]`	`[]`	Passed
no judgments	`[]`	`[]`	Passed
extra judgment ignored	`[['a1', 'A', 1]]`	`[['a1', 'A', 1]]`	Passed

SHA-256 / a7acf0b4738d9f17509ab8595d437106cf8715abc7ce815243afb8a759863b91

2 / The unsuccessful fix

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(responses, judgments):
    return [[r[0],r[1],j[1]] for r,j in zip(sorted(responses),sorted(judgments))]
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
a='a'+str(N); b='b'+str(N)
check('reordered judgments',solve([[a,'A'],[b,'B']],[[b,0],[a,1]]),[[a,'A',1],[b,'B',0]])
check('one shared id',solve([[a,'A']],[[a,1]]),[[a,'A',1]])
check('missing judgment',solve([[a,'A'],[b,'B']],[[b,0]]),[[b,'B',0]])
check('no responses',solve([],[[a,1]]),[])
check('no judgments',solve([[a,'A']],[]),[])
check('extra judgment ignored',solve([[a,'A']],[[a,1],[b,0]]),[[a,'A',1]])
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
reordered judgments	`[['a1', 'A', 1], ['b1', 'B', 0]]`	`[['a1', 'A', 1], ['b1', 'B', 0]]`	Passed
one shared id	`[['a1', 'A', 1]]`	`[['a1', 'A', 1]]`	Passed
missing judgment	`[['a1', 'A', 0]]`	`[['b1', 'B', 0]]`	Failed
no responses	`[]`	`[]`	Passed
no judgments	`[]`	`[]`	Passed
extra judgment ignored	`[['a1', 'A', 1]]`	`[['a1', 'A', 1]]`	Passed

SHA-256 / 715dd887dce62b28d60c13267c0894e060b422dc84d9f54fe9542ad6ee499ce8

HELD IN THE MEMBER ARCHIVE

The verified repair and its recorded checks are member-only.

This mechanism has 6 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.

Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.

Member access is invitation-based. Sign in with your invited account to inspect the repair.

Verification & scope

These are explicit toy record contracts; they do not claim compatibility with a trainer or improved model behavior. This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.

Observations recorded using Python 3.12.14 at 2026-09-30T16:48:31.262198+00:00.

Case digest / 511dec0852e7a593132e74e65e0b5cfae3cc370d1536385409b8459a738d183e