FAILURE MAP
← Case archive

FA-100179 / Annotation span alignment / Member archive

Nested annotations are sorted by end before start · case 04

Nested annotations are sorted by end before start.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Return [start,end,label] spans sorted by start ascending, then end descending, then label ascending.

Why this case matters

A small offline annotation transformation keeps span coordinates explicit when text or token boundaries change.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
nested first container[[1, 3, "z"], [2, 4, "b"], [2, 9, "a"]][[1, 3, "z"], [2, 9, "a"], [2, 4, "b"]]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 ↗