Skip to content

The e0308_partition_2026-08-22 board is 315 coded rows, not 316, and one derived percentage moves - #8928

Merged
briansrls merged 1 commit into
mainfrom
session/snappy-carp-40
Aug 22, 2026
Merged

briansrls merged 1 commit into
mainfrom
session/snappy-carp-40

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

The defect

The e0308_partition_2026-08-22 receipt and its summary_stamp both reported 316 coded rustc rows. The published raw log yields 315 — and so did the receipt's own series table, which already names this board the 315-board. The receipt disagreed with its own counter.

The cause — arithmetic, not measurement

HISTOGRAM_SUM=330 counts ^error(\[E[0-9]+\])?: lines (curated_cargo_probe_one.sh HISTOGRAM_SUM), and cargo's trailing error: could not compile ... due to 329 previous errors line matches that pattern. So 330 = 329 real error blocks + 1 summary line. Subtracting only the 14 uncoded rows (unsupported_mock_expression:13 + UNRESOLVED_CompilerError:1) from 330 gives 316; the summary line must come off first.

Three independent readings of the published log agree on 315:

  • 330 − 1 − 14 = 315
  • the per-code histogram sums to 315 (grep -o '^error\[E[0-9]*\]' | sort | uniq -c) — and matches the receipt's published board code-for-code
  • CARGO_ERROR_TOTAL=329 = 315 coded + 14 uncoded

Whether any derived percentage moved — yes, exactly one

E0308 share of the coded board: 128 / 315 = 40.6%, not 128 / 316 = 40.5%.

Nothing else moves. Every other percentage in both documents is denominated in the 154 canonical sites, not in coded rows — so the cluster shares, the 95.5% classified figure and the 4.5% residue figure are unchanged, as are the 128, the 154, the cluster counts, the histogram and every disposition.

One consequential prose claim also changes: the receipt said its total "agrees to within one row" with the brief's 315. That one row was the slip describing itself. The totals agree exactly, which strengthens rather than weakens the receipt's finding that the brief's 182 came from a different tree.

Scope

Both carriers are corrected, not only the stamp — leaving 316 standing in the receipt would be two authorities for one fact (§3). Each correction states the arithmetic in place so the 316 is not re-derived, rather than silently swapping a digit. Grep confirms no other document on main consumes this board's coded-row total.

Documentation only; no code, no .dag, no emitted artifact.

🤖 Generated with Claude Code

…one derived percentage moves

The receipt and its summary_stamp both reported 316 coded rustc rows. The published
raw log yields 315, and so did this document's own series table, which already named
this board the `315-board` — the receipt disagreed with its own counter.

The slip is in the subtraction, not the measurement. `HISTOGRAM_SUM=330` counts
`^error(\[E[0-9]+\])?:` lines, and cargo's trailing `could not compile ... due to 329
previous errors` line matches that pattern, so 330 = 329 real blocks + 1 summary line.
Removing only the 14 uncoded rows gives 316; the summary line must come off first.
330 - 1 - 14 = 315, the per-code histogram sums to 315 independently, and
CARGO_ERROR_TOTAL=329 = 315 coded + 14 uncoded is a third agreeing reading.

Exactly one derived percentage moves: the E0308 share of the coded board is
128 / 315 = 40.6%, not 40.5%. Every other percentage in both documents is denominated
in the 154 canonical sites, so the cluster shares, the 95.5% classified figure and the
4.5% residue figure are unchanged, as are the 128, the 154, the histogram and every
disposition. One consequential prose claim also changes: the receipt said its total
"agrees to within one row" with the brief's 315, which was the slip describing itself;
the totals agree exactly.

Both carriers are corrected rather than only the stamp, since leaving 316 standing in
the receipt would be two authorities for one fact.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@briansrls
briansrls merged commit 1bef84a into main Aug 22, 2026
1 check passed
@briansrls
briansrls deleted the session/snappy-carp-40 branch August 22, 2026 22:41
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