Repository navigation
docs(skill): audit the skill itself; one retraction was live, one number stale (#2492) - #2497
Merged
Merged
Conversation
…ber stale (#2492) Thirty-three sections written over six days, none re-read with the question that catches a stale claim. Ran the audit on the file: ten file references, four behavioural claims, five numeric pairs. THE CONTRADICTION. Section 32 stated in the present tense the justification that section 33 retracts, and 32 comes first -- a reader stopping there gets the wrong rule with a confident explanation attached. It now carries RETRACTED at the top of the paragraph rather than a note appended after it. THE STALE NUMBER. "34 of 42 sites" was true when written and false the next day, because 33 tightened the predicate and the denominator fell to 36. Dated in place rather than updated: the sentence is about what the scanner missed at that moment, and a number that keeps being silently corrected teaches nothing about how it drifted. A NEAR-MISS. "30 of 109 rows share a citation" read false at first -- I counted 45. Both readings had to be computed: 45 rows sit in shared groups, 30 are duplicates beyond the first, which is what a uniqueness check would flag. The claim holds. Second time in three days that checking both readings prevented a false accusation. Section 34 records the general form: nothing runs prose, so nothing goes red when it rots. Refs #2492
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
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.
Yesterday's finding was a justification I had written a day earlier that sounded principled and was wrong. Thirty-three sections were written the same way, in the moment, and none had been re-read with that question.
What was checkable, and what it said
The contradiction is the finding
§32 stated, in the present tense, the justification that §33 retracts — and §32 comes first. A reader who stops there gets the wrong rule with a confident explanation attached.
It now carries
RETRACTED, see §33at the top of the paragraph, not a note appended after it. Appending is always the cheaper edit, and the reader who most needs the correction is the one who does not reach it.The stale number
"34 of 42 sites" was true when written and false the next day: §33 tightened the predicate and the denominator fell to 36, because the loose one had been counting helper functions.
Dated in place rather than corrected. The sentence is about what the scanner missed at that moment; a number silently updated each time teaches nothing about how it drifted.
A near-miss worth recording
"30 of 109 catalog rows share a citation" read false at first — I counted 45. Both readings had to be computed before saying anything:
The claim holds. Second time in three days that computing both readings prevented a false accusation against working code.
The general form, now §34
Every rule this skill has about gate output applies to the skill itself: dated measurements as standing facts, a label trusted over a property, a justification that sounds principled. The difference is that nothing runs prose, so nothing goes red when it rots.
Refs #2492