FA-97985 / Training label alignment / Member archive
Conflicting duplicate labels are resolved by last-write order · case 05
Conflicting duplicate labels are resolved by last-write order.
Case contract
Records are [example_id,label]. Return ordered [id,label] for IDs with a single consistent label; omit IDs with conflicts.
Why this case matters
A small deterministic training-data operation makes label ownership and ordering explicit.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| conflict omitted | [["a", 6], ["b", 0]] | [["b", 0]] | 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 ↗