FA-3761 / Tokenization / Open access

A two-character operator is split into single tokens · case 01

A two-character operator is split into single tokens.

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

ROOT CAUSE

The implementation applies an operation whose text or grammar semantics violate this contract: Tokenize only <, <=, >, >=, = and == using maximal munch; spaces ignored.

THE FAILURE

The implementation applies an operation whose text or grammar semantics violate this contract: Tokenize only <, <=, >, >=, = and == using maximal munch; spaces ignored.

Unsuccessful approach: The attempted repair handles the primary example but still violates a separate boundary of the same contract.

Case contract

Tokenize only <, <=, >, >=, = and == using maximal munch; spaces ignored.

Why this case matters

A local executable model for consumers of structured text; oracle values are authored literals, not outputs copied from the repaired implementation.

1 / The failure

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json
import re, unicodedata, json, csv, io, html, base64, binascii, codecs, struct
from urllib.parse import quote, unquote, unquote_to_bytes, urlencode, parse_qsl, urlsplit, urlunsplit
from email.header import decode_header, make_header
from email.utils import getaddresses
from xml.etree import ElementTree as ET
import shlex, string, textwrap

N = 1
observations = []
def solve(x):
    try:
        return list(x.replace(' ',''))
    except Exception as exc:
        return {"error": type(exc).__name__}
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('boundary 1', solve('a<=b'), ['<='])
check('boundary 2', solve('== >='), ['==', '>='])
check('boundary 3', solve('< ='), ['<', '='])
check('boundary 4', solve(''), [])
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
boundary 1	`['a', '<', '=', 'b']`	`['<=']`	Failed
boundary 2	`['=', '=', '>', '=']`	`['==', '>=']`	Failed
boundary 3	`['<', '=']`	`['<', '=']`	Passed
boundary 4	`[]`	`[]`	Passed

SHA-256 / 38625f0e2099058d0aab71a2a8f741be0f83f6883e5197b72d90f7d19701217b

2 / The unsuccessful fix

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json
import re, unicodedata, json, csv, io, html, base64, binascii, codecs, struct
from urllib.parse import quote, unquote, unquote_to_bytes, urlencode, parse_qsl, urlsplit, urlunsplit
from email.header import decode_header, make_header
from email.utils import getaddresses
from xml.etree import ElementTree as ET
import shlex, string, textwrap

N = 1
observations = []
def solve(x):
    try:
        return re.findall(r'[<>=]|<=|>=|==',x)
    except Exception as exc:
        return {"error": type(exc).__name__}
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('boundary 1', solve('a<=b'), ['<='])
check('boundary 2', solve('== >='), ['==', '>='])
check('boundary 3', solve('< ='), ['<', '='])
check('boundary 4', solve(''), [])
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
boundary 1	`['<', '=']`	`['<=']`	Failed
boundary 2	`['=', '=', '>', '=']`	`['==', '>=']`	Failed
boundary 3	`['<', '=']`	`['<', '=']`	Passed
boundary 4	`[]`	`[]`	Passed

SHA-256 / ad7b7c392aaa17ef4ed7ef85b96cd0c6f3f71616e3dd249b3df0c9dd7bf714d4

HELD IN THE MEMBER ARCHIVE

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

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

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-29T14:37:30.398343+00:00.

Case digest / fb18e77d0fe7cc865d39a5967b01b6c2090a5b0a530a514d5ec43e9bc35ce291