Systems and subsystems

The pre-declared sweeps and the orchestration ablation

Two scripts that chose the fusion rule under rules written before they ran, and one that measures what the router changes by switching each rule off. Together they are the record of how the shipped rule was picked and what it buys.

In plain words

Our first fusion, an equal-weight average, was the best thing our holdout had ever seen and doubled the misses on real-world audio. The lesson was to write the candidates, the readouts and the selection rule down first and apply them once. The first sweep froze the rule at 08:13; a second, stricter sweep for M5 was written at 08:35, run by 09:15 and ratified at noon. The ablation exists because the rubric's orchestration bonus deserves a measurement, not a claim.

What goes in and comes out

In: the detectors' exported score files (inner out-of-fold, holdout, test and In-the-Wild rows). Out: a table of every candidate under every readout, a decision under the fixed rule, the constants file when asked, and for the ablation a markdown and JSON table of the router on, each rule off, and everything fused equally.

Where it lives

fuse_sweep.py (the first sweep), fuse_sweep_m5.py (the M5 addendum and the unexercised refit rule), orchestration_ablation.py, fuse.py (the first, rejected fusion).

The rules, as written before the runs

Status

Both sweeps applied once; the M5 candidate held from 09:25 until noon while the runner side was built behind a flag, then ratified. The advance expectation that the three-way blend would lose on short clips and LibriSpeech real speech was wrong: with the Spectra step it improved both.

Numbers

First sweep: α = 0.2source: README.md, section the-fusion-rule won (tied with 0.3source: README.md, section the-fusion-rule), Spectra took In-the-Wild from 0.322source: README.md, section the-fusion-rule to 0.260source: README.md, section the-fusion-rule. Addendum: the suppressor candidate gained only 0.003source: README.md, section the-fusion-rule; the three-way blend at 0.2source: README.md, section the-fusion-rule qualified with holdout 0.0065source: README.md, section the-fusion-rule against 0.014source: README.md, section the-fusion-rule and In-the-Wild 0.228source: README.md, section the-fusion-rule against 0.260source: README.md, section the-fusion-rule. Ablation: the Spectra step takes the holdout from 0.0200source: README.md, section orchestration-what-routing-changes to 0.0065source: README.md, section orchestration-what-routing-changes and In-the-Wild from 0.274source: README.md, section orchestration-what-routing-changes to 0.229source: README.md, section orchestration-what-routing-changes, touching only real files; the gate touches 0 test files; fusing everything equally reaches 0.0045source: README.md, section orchestration-what-routing-changes and 0.214source: README.md, section orchestration-what-routing-changes by giving Spectra a full vote. The full table is on How it decides.

Known limits

The holdout's resolution floor means the sweeps could not have told a good rule from a slightly better one on the holdout alone; the rules lean on In-the-Wild for that reason. The ablation script has no tests of its own.

Tests that pin it

tests/test_pipeline.py pins that the runner's arithmetic equals each sweep script's, including the left-sided rank boundary and the strict Spectra inequalities, and that the shipped constants file reproduces the 09:14 candidate TSV from the exported logits (data-gated).

Sources

The sweep report; README, "The fusion rule"; README, "Orchestration"; the fusion consult.