An instrument for the population the swap plan under-drew - #102
Conversation
The section 02 swap was planned as six parts with two named dependents. It missed two sentences, and one of them was INSIDE the section being swapped: "We hold [122] signed resolution records that a reader on [1.0.0-rc.21] has no route to." Both of its spans updated correctly. The sentence inverted in meaning and nothing moved it. THE POPULATION THAT WOULD HAVE CAUGHT THEM IS DERIVABLE AND WAS NOT DERIVED: every sentence containing a span whose value the change moves. This derives it rather than asking anyone to keep a list. Run BEFORE a change: write the new results/, pass HEAD as the baseline, and every affected sentence prints before anything is committed. Run AFTER, with a ref from before it, to audit what was missed. IT DOES NOT DECIDE. Whether a sentence survives its span changing is a judgement about meaning and no check makes it. It prints the sentence with the old and new values beside each other so the judgement is made deliberately rather than skipped. Exit 0 always: an enumerator, not a gate. A gate that guessed at meaning would be a fourth way to be wrong about this.
✅ Deploy Preview for observerprotocol ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Closing rather than merging: master already carries this instrument, as a later version.
What master's version adds over this one: this PR derives its population from "every sentence containing a The conflict is on the added file for that reason: the path already exists on master. The failing "Published credentials verify" check is the stale base, not this change — it is green on current master ( The defect this instrument names is being recorded in CONVENTIONS in #125, so it survives the close. |
1 participant
Item 1. Not merged. It has already found a live defect — see below.
What it derives
The section 02 swap was planned as six parts with two named dependents. It missed three sentences, and one was inside the section being swapped:
Both spans updated correctly. The sentence inverted in meaning and nothing moved it.
The population that would have caught them is derivable and was not derived: every sentence containing a span whose value the change moves. This derives it rather than asking anyone to keep a list.
How it is used
Before a change: write the new
results/, passHEADas the baseline, and every affected sentence prints before anything is committed.After: pass a ref from before it, to audit what was missed.
It does not decide
Whether a sentence survives its span changing is a judgement about meaning, and no check makes it. It prints the sentence with old and new values beside each other so the judgement is made deliberately rather than skipped.
Exit 0 always — an enumerator, not a gate. A gate that guessed at meaning would be a fourth way to be wrong about this.
Run against the move that already happened
Baseline
d6d4288, the commit before the re-measurement. 12 measured values moved; 3 sentences at risk.Two were already fixed. The third was live on the swap branch and false:
rc.21 is not inside rc.9–rc.12. Fixed on the swap branch; it now reads "no longer points inside that band".
The instrument found in one run what three readings of the same section did not.