Repository navigation
feat(tri): gates mutate --invert, the third axis (#2492) - #2499
Merged
Merged
Conversation
Two operators ask whether a gate can still reach its verdicts. This asks whether it reaches the RIGHT one: a gate that fires FAIL on a healthy tree and OK on a broken one satisfies both of the others. `if C:` becomes `if not (C):` on conditions whose body carries a verdict. Thirteen gates, ONE survivor -- check_elab_ratchet's no-baseline branch, the same one both other operators leave, declared UNCOVERED with its reason. Three axes now converge on one line. The scoping is the design. Inverting a loop guard or a plumbing check makes the gate CRASH, and a control that reds on a traceback would score that as a kill for the wrong reason. Only conditions whose body holds a `return 1..4`, a `raise SystemExit(N)` or a FAIL print are sites. Measured over 19 mutations on four gates: 19 killed by MESSAGE, zero tracebacks. My verification probe was broken twice before it worked -- it mutated inside the control functions, which the Rust implementation excludes and the probe did not, and its label conflated "not killed" with "killed by a crash". The first output looked like a finding about the tool. Refs #2492
…nd nothing (#2492) --invert asks whether a gate reaches the RIGHT verdict, not whether it can still reach one. Thirteen gates, one survivor: the branch both other operators leave, declared uncovered. That is the first new instrument here to find nothing, and it is worth as much as the ones that found plenty -- controls written against two questions held against a third. Plus: scope an operator by what its kills would MEAN, and then measure that the scoping worked. 19 mutations, 19 killed by message, zero tracebacks. And: the probe that checks a tool gets less care than the tool. Mine was broken twice in one run and its first output read as a finding about the tool. The throwaway scripts account for most of the seven broken instruments in this campaign. Refs #2492
Contributor
PR DashboardGenerated at: 2026-08-23 04:27:06 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
The note was dated 2026-08-25 and check-now-freshness rejected it. The real UTC date is 2026-08-23. I had been inferring the passage of days from the number of iterations rather than reading a clock, and two earlier notes carry the same invented drift. Mechanism 8.2 inside out: the world did not move and I recorded that it had. The gate caught it, which is the gate doing precisely its job, and the first time in this campaign that an existing gate caught ME. Refs #2492
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-23 04:37:29 UTC
Summary
Seal Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two operators ask whether a gate can still reach its verdicts. This asks whether it reaches the right one.
A gate that fires its FAIL branch on a healthy tree and its OK branch on a broken one satisfies both return operators, and neither is looking at that.
Result
if C:→if not (C):on conditions whose body carries a verdict. Thirteen gates, one survivor:check_elab_ratchet's no-baseline branch — the same one both other operators leave, declaredUNCOVEREDwith its reason.Three axes now converge on one line. This is the first new instrument in this campaign to find nothing, and that is worth as much as the ones that found plenty: controls written over a week against two questions held against a third they were not written for.
The scoping is the design
Inverting a loop guard or a plumbing check makes the gate crash, and a control that reds on a traceback would score that as a kill — for the wrong reason, which is the mistake this command exists to catch.
Only conditions whose body holds a
return 1..4, araise SystemExit(N)or a FAIL print are sites. Measured over 19 mutations on four gates:My verification probe was broken twice before it worked
It mutated inside the control functions — which the Rust implementation excludes and the throwaway Python probe did not — and its verdict label conflated not killed with killed by a crash, printing
killed by crashfor a mutant that had survived.Both wrong in the same run, and the first output read as a finding about the tool. The probe written to verify a careful tool inherits none of its care, and is trusted anyway because it is short.
Six unit tests on the site selector, including the three exclusions: a body that only prints, a body that returns success, and anything inside a control function.
Refs #2492