Measure only the usable validation context prefix

This commit is contained in:
2026-11-16 14:14:21 +00:00
parent 0c144fd5a5
commit b1d1b8302c
8 changed files with 229 additions and 144 deletions

View File

@@ -156,15 +156,12 @@ already clear from its own segment does not require such evidence. No audio,
out-of-chunk context, or complete transcript is implied.
Context is serialized inside the validation item and included in the existing
payload token estimate, including the target speaker. If one enriched item exceeds
the configured limit, optional neighbors are removed from the end first, then
glossary entries from the end,
until it fits or only required candidate data remains. Required before/after text
is never truncated. Existing oversized-candidate handling still applies if that
required data does not fit. The built-in estimator reuses encoded fragment
counts for fitting and batching. Context is supplemental, not a promise that every
relevant definition or neighboring utterance always fits. This uses the existing
payload estimator, not a new guarantee about the provider's full context window.
payload token estimate, including the target speaker. Fitting measures the
required data first, then considers glossary entries followed by neighboring
segments in order. It stops at the first entry that exceeds the budget. Required
before/after text is never truncated. A candidate whose required data exceeds
the budget receives an unavailable decision. The built-in estimator reuses
encoded fragment counts for fitting and batching.
## Protected Names