FA-100127 / Preference pair construction / Member archive

Preference pairs: responses from different sources are paired · case 02

responses from different sources are paired.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Rows are [source,id,score]. Within each source emit its strict best/worst [source,best_id,worst_id] if at least two candidates; source order is first-seen and score ties break by ID.

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 fixture	Actual	Expected	Outcome
cross-source excluded	`[["q2", "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.