port: grep the corpus for the claim -- one refuted sentence was still shipping
Applying the Decoder's rule to my own corpus, on four claims refuted this fortnight. Two were properly marked. Two were not. The exported why still told readers the dropped chunk 'IS understood: the TAIL of the kept stream' -- an interpretation refuted when the resolver turned out to start 238 packets inside the first stream, so what matched end-flush was a start-truncated simultaneous stream. It was wrong twice over: S00A's dropped chunk is the SILENT one, so the sentence described a case that was not present -- the second template-message-true-only-for-one-case defect in this file, which suggests the first fix taught me nothing general. 'The port's boot is known too fast on both' was still standing unmarked. I wrote the withdrawal as a new section and left the original untouched, so a reader arriving there first got the dead answer. Annotated in place. One false positive: BLOCKED matched inside my own correction, which quotes the refuted claim to name it. Naming a refuted sentence keeps it greppable, which is the price of not deleting it, so the audit needs a read of every hit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
This commit is contained in:
@@ -1007,10 +1007,17 @@ pub fn export_voice<S: DiscSource + ?Sized>(
|
||||
String::new()
|
||||
} else {
|
||||
format!(
|
||||
" Also dropped, and this one IS understood: the leading chunk, which this \
|
||||
port measured to be the TAIL of the kept stream (sliding envelope \
|
||||
correlation r=0.998 ADV / 0.932 S00A, lag flush against that stream's \
|
||||
end, controls 1.000 self and 0.289 for a different movie): {}.",
|
||||
" Also dropped: {}. A chunk marked SILENT carries no signal and \
|
||||
contributes nothing; one of a different duration is not a \
|
||||
concurrent stream of this take. \u{1f534} THIS SENTENCE USED TO SAY \
|
||||
the leading chunk was `the TAIL of the kept stream`, on a sliding \
|
||||
envelope correlation of r=0.998. The CORRELATION was sound and the \
|
||||
INTERPRETATION was refuted: `resolve_movie_voice_region` was \
|
||||
starting 238 packets inside the first stream, so what matched \
|
||||
end-flush was a START-TRUNCATED SIMULTANEOUS stream, not a \
|
||||
duplicate tail -- which is why it aligned at the end. Fixed in \
|
||||
formats-pin-2026-08-30; that chunk is now kept at full length and \
|
||||
nothing is dropped for that reason any more.",
|
||||
dropped.join(", ")
|
||||
)
|
||||
},
|
||||
|
||||
Reference in New Issue
Block a user