Normalize nested intervals and build merges incrementally

This commit is contained in:
2026-11-16 03:59:44 +00:00
parent f465496dd8
commit 27f494d4e4
6 changed files with 173 additions and 229 deletions

View File

@@ -7,8 +7,9 @@ formats; [configuration](../config.md) owns settings; the
1. CLI loads resolved configuration and transcript input. Preflight checks all
selected glossary views and roles before the output session prepares resources.
Transcript segments then enter canonical normalization.
2. Normalization sorts and merges segments using configured time and token
limits, reassigning IDs where needed.
2. Normalization sorts segments by start time and preserves input order for
ties. It evaluates merge limits using the later end time and the same token
estimate as chunking, then reassigns IDs where needed.
3. The runner partitions the normalized transcript exactly once before its
module loop. Initial section identity, segment membership, and token
estimates stay fixed while text evolves.

View File

@@ -245,6 +245,13 @@ Audit #17, #21, #35, #53, #59, #62 (merge helper).
nested intervals, ties, joiners, category ordering, and exact estimates.
Compare allocations or growth on a representative run of same-speaker merges.
**Complete.** Verified stable start-time ties, nested intervals, exact joiner
and token behavior, and category order. The merge uses incremental text,
categories, and the shared token estimator. On synthetic same-speaker runs
(Go 1.27.3, three iterations each), allocations fell from 238.1 MB to 0.42 MB
per operation for 2,000 segments and from 960.1 MB to 0.85 MB for 4,000. The
CLI build and full offline suite passed.
## Stage 7 — Make feasible explicit section targets succeed
Audit #20 and the infeasibility portion of #24.