Explicit Span Redactor
Remove declared sensitive spans and record where replacements moved in the output.
Version: 1.0.0. License: MIT. Status: tested reference baseline; no comparative ranking is claimed.
Contract
Sort nonoverlapping source spans by start and end. Require nonempty labels and valid nonempty code point spans. Replace each span with [REDACTED] and return input and output offsets plus labels. Never include removed text in the output mapping. Adjacent spans are allowed.
The exact required input fields and types are in input.schema.json. Extra fields are rejected at declared object boundaries. JSON duplicate keys and non-finite numbers are rejected by the CLI. Input strings are case-sensitive unless stated otherwise. Array order is preserved unless the contract specifies sorting.
Use
Unpack the ZIP, enter its directory, and run:
python3 baseline.py < example.input.json
python3 -m unittest -v
Python 3.10 or newer, standard library only. The reference implementation exposes run(input_dict) and accepts one JSON object on standard input. Success returns {"ok": true, "result": ...} with exit code 0. Invalid input returns {"ok": false, "error": "..."} with exit code 1. example.output.json contains the result without the CLI envelope. Import callers receive exceptions for invalid input.
Example input
{
"text": "Email ada@example.test now",
"spans": [
{
"start": 6,
"end": 22,
"label": "email"
}
]
}
Example result
{
"text": "Email [REDACTED] now",
"mapping": [
{
"input_start": 6,
"input_end": 22,
"output_start": 6,
"output_end": 16,
"label": "email"
}
]
}
Boundaries
This is a redaction primitive, not a detector or anonymization guarantee. The caller must identify every sensitive span and avoid sensitive information in labels. Lengths, positions, and unredacted context can still reveal information. Offsets use Python Unicode code points.
This package performs no network calls, executes no submitted commands, and writes no user files. Host applications own authorization, resource budgets, and persistence. Example values are fixtures, not recommended policies or limits.
Acceptance and provenance
cases.json records named expected results and rejection cases. test_baseline.py runs those cases and checks the command-line contract. manifest.json records file digests. The specification, implementation, and evidence are separate files so a replacement implementation can target the same contract.
Original code and examples generated for this Arcomm collection. No third-party code is bundled. Read LICENSE for reuse terms.
Download
SHA-256: ab94a3223b5cba43eec0bd570ddec100dfcd41eaf146a0e96281396812293e76
Size: 6855 bytes.