fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

port: make the documented control sweep executable; it was prose

Browse Source 
AUDIO-VERIFICATION.md calls its six-file sweep 'the tool's real specification'
and nothing ran it -- in a tool whose own history is two invented thresholds
caught only by controls. The same document states the principle it was breaking:
a control that does not execute is not a control.

tools/port/check-capture-controls rebuilds five of the six and asserts their
verdicts. The starved capture is gone and is reported MISSING rather than
omitted, and deliberately not synthesised from its published statistics -- a
control fitted to the answer it must give is not a control.

Two things the sweep had to learn to be honest about. check-capture emits TWO
verdicts and the doc's table compresses them; the voice control is PASS on
channels and UNJUDGED on starvation by design, so the sweep asserts the pair. And
a starved file short-circuits before the channel check, recorded as n/a rather
than FAIL -- the check did not run and the check failed are different facts.

My first 'real music bed' control was -ac 6 from a stereo source and FAILED
correctly: an upmix leaves channels silent and byte-identical, which is what the
provenance check exists to catch. The control was wrong, not the tool. Rebuilt
from six non-overlapping spans of real audio. A second attempt used aloop=-1 and
hung ffmpeg indefinitely.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
This commit is contained in:
Sylpheed port agent
2026-08-30 04:26:07 +00:00
parent 77e217807a
commit 952c856da5
2 changed files with 109 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/port/AUDIO-VERIFICATION.md
View File

@@ -260,6 +260,12 @@ actually decides the sample layout; a float tee is 32-bit and is still caught.
### The control sweep, which is the tool's real specification
**Run it: `tools/port/check-capture-controls`.** 🔴 Until 2026-08-30 this table was prose — the specification existed and nothing executed it, so a regression in `check-capture` or a drifting threshold would have gone unremarked in a tool whose own history is *two invented thresholds that were both wrong and were caught only by controls*. This document states the principle it was breaking: **"a control that does not execute is not a control."**
⚠️ The verdicts below are **compressed**. `check-capture` emits two — one for channel provenance, one for starvation — and the sweep asserts the pair, because the voice control is `PASS` on channels and `UNJUDGED` on starvation *by design* and a single word cannot say that. A starved file **short-circuits** before the channel check, which the sweep records as `n/a` rather than as a failure: *the check did not run* and *the check failed* are different facts.
⚠️ The **starved capture cannot be rebuilt** — that artifact was transient and is gone. The sweep reports it `MISSING` rather than omitting it, and deliberately does not synthesise one from the statistics published above: a control fitted to the answer it must give is not a control either.
| file | verdict |
|---|---|
| real music+SFX bed | `PASS` |