FA-100146 / Annotation span alignment / Open access

Deleted text clips spans to the surviving boundary · case 01

Deleted text clips spans to the surviving boundary.

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

ROOT CAUSE

Deletion is treated as a negative shift without collapsing covered endpoints.

THE FAILURE

Deletion is treated as a negative shift without collapsing covered endpoints.

Unsuccessful approach: Leaving an endpoint exactly at the deletion end unchanged fails to collapse it to the deletion start.

Case contract

Delete [left,right). Map each endpoint x to x if x<=left, left if left<x<right, and x-(right-left) if x>=right.

Why this case matters

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

1 / The failure

Exit 1

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

N = 1
observations = []
def solve(spans, left, right):
    return [[x-(right-left) if x>=right else x for x in (s,e)] for s,e in spans]
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('outside left', solve([[0,2]],3,5), [[0,2]])
check('outside right', solve([[7,10]],3,5), [[5,8]])
check('covers deletion', solve([[1,8]],3,5), [[1,6]])
check('starts at deleted end', solve([[5,8]],3,5), [[3,6]])
check('ends at deleted start', solve([[1,3]],3,5), [[1,3]])
check('fully deleted span collapses', solve([[4,5]],3,5), [[3,3]])
check('empty list', solve([],N,N+2), [])
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
outside left	`[[0, 2]]`	`[[0, 2]]`	Passed
outside right	`[[5, 8]]`	`[[5, 8]]`	Passed
covers deletion	`[[1, 6]]`	`[[1, 6]]`	Passed
starts at deleted end	`[[3, 6]]`	`[[3, 6]]`	Passed
ends at deleted start	`[[1, 3]]`	`[[1, 3]]`	Passed
fully deleted span collapses	`[[4, 3]]`	`[[3, 3]]`	Failed
empty list	`[]`	`[]`	Passed

SHA-256 / cc9b7764f5529efd5717dee7672737fc2024e95365a7ac3b8ca368ea76505637

2 / The unsuccessful fix

Exit 1

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

N = 1
observations = []
def solve(spans, left, right):
    return [[left if left<x<right else (x-(right-left) if x>right else x) for x in (s,e)] for s,e in spans]
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('outside left', solve([[0,2]],3,5), [[0,2]])
check('outside right', solve([[7,10]],3,5), [[5,8]])
check('covers deletion', solve([[1,8]],3,5), [[1,6]])
check('starts at deleted end', solve([[5,8]],3,5), [[3,6]])
check('ends at deleted start', solve([[1,3]],3,5), [[1,3]])
check('fully deleted span collapses', solve([[4,5]],3,5), [[3,3]])
check('empty list', solve([],N,N+2), [])
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
outside left	`[[0, 2]]`	`[[0, 2]]`	Passed
outside right	`[[5, 8]]`	`[[5, 8]]`	Passed
covers deletion	`[[1, 6]]`	`[[1, 6]]`	Passed
starts at deleted end	`[[5, 6]]`	`[[3, 6]]`	Failed
ends at deleted start	`[[1, 3]]`	`[[1, 3]]`	Passed
fully deleted span collapses	`[[3, 5]]`	`[[3, 3]]`	Failed
empty list	`[]`	`[]`	Passed

SHA-256 / 5d4b48175b3214f0be989228f37561700197ff852c7bddce5fc36bb61ecd17dd

HELD IN THE MEMBER ARCHIVE

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

This mechanism has 7 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

Contracts use integer offsets, explicit edits, and supplied token boundaries; they do not define a tokenizer or production annotation format. 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:32.171118+00:00.

Case digest / ad857469449ddd19f6752286bb28475158ad82a85be21c8580ab30b1f2d45e41