Two of my own commands disagreed about the same population - #2928
Merged
Conversation
`tri prose report` said "107 specs that do not parse". `tri unparsed report`
said 76. Both are mine and both walk the same corpus.
The gap is 21 files under `fixtures/`, broken ON PURPOSE as detector inputs,
and 10 specs that parse and fail at a later stage -- the same two rules added to
`report`, then to `locate` after finding they had not travelled, and which never
reached the third sibling.
A third instance of one lesson is evidence the cure was wrong, so this one is
structural. The scope now lives in ONE function:
unparsed::parse_failures(root, t27c) -> Scope
failures the parse-stage failures, with the compiler's output
fixtures set aside, counted, named in the output
other_stage parse fine, fail later
tracked
Both commands call it. Disagreement is impossible rather than tested for.
tri unparsed report refused at PARSE 76 · fixtures 21
tri prose report refused at PARSE 76 · fixtures 21
AND THE PREMISE OF THE ITERATION WAS STALE. I opened it to bridge the two --
"the census abstains on ten and prose answers six of them". Prose answers ZERO:
earlier repairs closed those specs. The sentence was true when written and never
re-measured. An option list is a claim with a date on it.
`bootstrap/src/compiler.rs` untouched; FROZEN_HASH does not move. The 10
`never used` warnings are pre-existing -- 10 on master too, none in the two
files touched here.
Refs #2864
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
August 30, 2026 00:22
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
2 participants
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.
tri prose reportsaid 107 specs that do not parse.tri unparsed reportsaid 76. Both are mine, both walk the same corpus, and neither had any claim
to be believed over the other.
The gap
fixtures/, broken on purpose as detector inputsExactly the two rules added to
report, then tolocateafter finding they hadnot travelled — and which never reached the third sibling.
A third instance means the cure was wrong
The same lesson was already written down twice, so this fix is structural rather
than another patch. The scope now lives in one function:
Both commands call it. Disagreement is impossible rather than tested for.
The premise of this iteration was stale
I opened it to bridge the two: "the census abstains on ten, and
tri prose reportanswers six of them." It answers zero — earlier repairs closedthose specs. The sentence was true when written and never re-measured.
An option list is a claim with a date on it. Re-measuring took one command
and would have saved picking it at all.
Gates, run locally
specs generate 0 · verilog widths 0 · specs parse 0 · conflict markers 0 ·
seal coverage 0 · seals fresh 0 · types ratchet 0 · skill check 0 ·
unparsed probe 0 · prose report 0 · ledgers audit 0 ·
cargo test -p tri0 ·rustfmt --checkon both touched files 0.bootstrap/src/compiler.rsis untouched, soFROZEN_HASHdoes not move. The 10never usedwarnings are pre-existing — 10 on master too, none in the two filestouched here.
Refs #2864