Add source-preserving tokenizer - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tokenize()interfaceWordTokenvalues with original[start, end)character offsetsWhy
The contextual classifier needs word-level inputs, while every public span and later edit must continue to refer to exact coordinates in the original transcript. This tokenizer establishes that source-preserving seam before model subword tokenization is introduced.
Invariant
For every returned token,
text[token.start:token.end] == token.text. Empty and whitespace-only inputs return no tokens.Without this invariant, model predictions could be mapped back to the wrong transcript evidence, breaking provenance and potentially rewriting text outside the accepted span. The tests independently pin exact tokens and offsets across whitespace, punctuation, apostrophes, leading zeros, alphanumeric values, email-like text, hyphens, and time punctuation.
Validation
uv run pytest— 44 passeduv run ruff check .uv buildgit diff --check