Skip to content

Correct six numbers an audit found wrong, at their sources - #3254

Merged
gHashTag merged 1 commit into
masterfrom
w106d-my-own-numbers-were-wrong
Sep 5, 2026
Merged

gHashTag merged 1 commit into
masterfrom
w106d-my-own-numbers-were-wrong

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

Every figure published during the #3229 / #3232 / #3237 pass was re-measured on
master by five independent readers using their own commands, with a third
reading on each disagreement.

10 CONFIRMED · 3 stale-but-were-true · 6 WRONG. Full accounting in #3253.

Fixed here

competitors.rs — the comment justified the anchor by claiming
pub fn beta_competitor is production code below the first test module (line
567). It is at line 696, inside the raw string const TWO which opens at
681 and closes at 705 — fixture text inside mod tests. The file has no
production item below the cut.
A column-0 ^pub fn regex counted a string
literal as code.

The anchor stays: the count assertion and the absence assertion genuinely differ
in kind — a call site leaving the slice makes the count read 1 and fail loudly,
while a reintroduced subtraction below the cut would simply not be found. Only
the stated reason was false.

prose.rs and SKILL.md — "10 of 46 files have production items after
their first #[cfg(test)], 130 items in all" reproduces under no definition:

definition files items
split on the string #[cfg(test)] 13 160
split on the bare attribute line 11 140
…and reject matches inside string literals 9 133
published 10 130

The 46 is right by three independent instruments, and gates.rs holding
79 is right. The file count is now given with its three matchers instead of
as one number.

mutate.rs — "SIX doc comments before the attribute" was five: lines
216, 355, 358, 371, 375; twelve in the file; attribute at 487. History shows it
was never six.

Corrected in the issues, not in code

Why this is a defect report and not a typo fix

Four of the six are a population mismatch, not an arithmetic error: string
literals counted as code, a matcher left unstated, a minimum reported as a
central value, coq/ where coq/**/*.v was meant.

That is the same class the pass was hunting — #3229 was a tally whose classes
did not cover its population, #3237 an assertion evaluated over a region that
need not contain its subject. Every one of the six had already been "checked",
by me, with the instrument that produced it.

Adds a ci-gates section recording the audit and its three lessons.

cargo test -p tri --bin tri: 776 passed, 0 failed.

Refs #3253

Every figure published during this pass was re-measured on master by five
independent readers using their own commands, with a third reading on each
disagreement: 10 CONFIRMED, 3 stale-but-were-true, 6 WRONG.

competitors.rs: the comment claimed `pub fn beta_competitor` is production code
below the first test module and used that to justify the anchor. It is at line
696, INSIDE the raw string `const TWO` which opens at 681 and closes at 705 --
fixture text inside `mod tests`. The file has no production item below the cut.
A column-0 `^pub fn ` regex counted a string literal as code. The anchor stays,
because the count and absence assertions differ in kind, but its stated reason
was false.

prose.rs and SKILL.md: "10 of 46 files, 130 items" reproduces under no
definition -- 13/160 splitting on the string, 11/140 on the bare attribute
line, 9/133 additionally rejecting string literals. The 46 is right; gates.rs
holding 79 is right. The file count is now given with its three matchers rather
than as one number, because a figure that moves with the matcher carries the
matcher.

mutate.rs: "SIX doc comments before the attribute" was five -- 216, 355, 358,
371, 375, twelve in the file, attribute at 487. History shows it was never six.

Also corrected in the issues, not here: "each push triggers 28 check-runs" was
the MINIMUM of a sample whose range is 28-43, median 41 (#3236, where it priced
an argument it now strengthens); and "zero Admitted anywhere under coq/" is one,
in coq/README.md -- zero in `.v` files, the population the gate reads.

Four of the six are a population mismatch rather than an arithmetic error:
literals counted as code, a matcher left unstated, a minimum reported as a
central value, and `coq/` where `coq/**/*.v` was meant. Same class the pass was
hunting.

Refs #3253

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag
gHashTag merged commit 0784be5 into master Sep 5, 2026
32 of 34 checks passed
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-05 08:05:16 UTC

Summary

Status Count
Total Open PRs 12
PRs with Failing Checks 10
PRs with All Checks Green 2
READY 0
FAILING 10
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=de6cd4b1b116 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag deleted the w106d-my-own-numbers-were-wrong branch October 26, 2026 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant