Repository navigation
feat(tri): gates mutate --dir; testing a published prediction (#2492) - #2509
Conversation
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
|
Correction, one iteration later. The claim in this PR — "54 Python tools and not one declared negative control" — is literally true and its meaning is false. Retracted and measured properly in #2511. The denominator is 6, not 54: only 7 of the 54 appear in any workflow, and 6 both run in CI and can exit non-zero. And three of those six are well controlled — including one whose test docstring reads "Values, not verdicts. The structural check's flop counter returned zero for every design on earth and stayed green for weeks because the only thing its self-test asserted was pass-or-fail." I searched for |
The twelfth post claims that controls miss degenerate inputs — the empty case, the equal case, the one off the edge — because a control author plants examples of a fault, and degenerate inputs are examples of nothing. It says outright that this predicts a hole in other suites and does not measure one.
So: measure one.
tri gates mutatelearned--dir, and the campaign's own question was pointed outside its repository for the first time.The prediction could not be tested, and the reason is a finding
The second repository has 54 Python tools and not one declared negative control — no
--self-check, no--selftest, under any spelling. There is nothing to ask "did the control notice?" of. That is the state this repository was in before the campaign, and it is a larger fact than the prediction was.The only other controlled gate in reach is the one written yesterday from these lessons. Its boundary column reads
0/0— the file contains no comparison at all — so the prediction is untestable there too, honestly and for a boring reason.The run found something else
That gate — nine control cases, written with more discipline than anything else this week — had a surviving silent mutant:
main()'s no-argument branch. Every case passes a build path, so nothing ran it the way a broken caller would.It matters because of where the gate is wired. The unattended publisher calls it inside an
if !, so a lost argument reachingreturn 0reads as a passing check and the cron publishes having compared nothing. The vacuous pass, inside the guard written against the loss it exists to prevent.Beside it: the usage line was
__doc__.splitlines()[-4], which printed the--historyline rather than the usage line. A message whose content is an index into the prose above it is wrong the moment the prose is edited — and it already was.Two rulers widened to make the run possible
check_and notcheck-, so aimed elsewhere it found nothing and printed an empty table — which reads exactly like a clean suitecode()hard-codedtools/, so with--dirit would have run a different file of the same name, or noneBoth are the shape this campaign keeps meeting: an instrument that works because everything it has ever seen was arranged one way.
Safety
The gate scripts refuse a path override on purpose — a flag that aims a live gate somewhere harmless is a way to make it pass. This is the auditor, not a gate. The dirty-tree refusal follows the directory, so an interrupted run is still recoverable with
git checkoutin the right repository. Default behaviour is unchanged: verified identical output on the 13-gate suite, and 13 unit tests green.Refs #2492