My refusal to apply their weights found a defect in their decoder:
resolve_movie_voice_region starts 238 packets (487424 B) inside ctx0 for ADV, and
8 of 10 three-chunk regions start mid-stream disc-wide.
That re-reads one of my own measurements without touching it. I had the leading
chunk as 'the TAIL of the kept stream' at r=0.998, lag flush against the end, and
dropped it as a duplicate. If the streams are simultaneous and the region starts
238 packets into ctx0, the surviving fragment is ctx0's later 62%, which aligns
flush against the end -- exactly what I measured. Same number, opposite meaning:
a start-truncated simultaneous stream, not a duplicate. The port drops a real one.
I suspected the instrument first, since they had just shown envelope correlation
saturating at 0.86-0.95 across stream/channel pairs. Tested on the dialogue: r =
1.0000 at zero offset, -0.08..+0.08 elsewhere. It localises sharply; their
saturation is concurrent streams at zero lag, a different regime. So the tool was
sound and the error was entirely in the inference.
Not fixed: including chunk 0 needs their corrected span (they say do not extend
blind -- only ADV's clip is known) or an alignment decision I would be inventing,
since the chunk is missing its head.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
9739b90266