Skip to content

[conformance] Promote gf10 and gf256 to bitexact_selfconsistent (WP-34) - #4763

Merged
gHashTag merged 2 commits into
masterfrom
queen-1215
Sep 24, 2026
Merged

gHashTag merged 2 commits into
masterfrom
queen-1215

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #1215

Written by a bee on queen-1215 and published by tools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.

2 files changed, 3 insertions(+), 3 deletions(-)

🤖 Generated with Claude Code

Agent and others added 2 commits September 24, 2026 04:13
The turn ended with these files edited and never committed. Uncommitted
work is invisible to the review - it reads the branch - so the attempt
would have been released as empty and the next bee would have started
beside this work rather than from it.

This commit is not a claim that the work is correct. It is the bee's
work, committed on its behalf, and it is judged exactly like any other:
the adversarial reviewer reads it, the compiler runs on it, and the
issue's own criteria are measured against it.

Issue: #1215
Turn: c99e278f-8779-4ef2-af4e-4dc886638d58
Ending: finished (the turn closed)
Committed: 2 path(s)
Left uncommitted: 0 path(s) outside the declared boundary
A pull request must add exactly one docs/now entry and a bee has no way
to know that: its brief names a boundary file and acceptance criteria,
and docs/now/ is neither. The publisher adds it rather than failing the
gate.

Closes #1215

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

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

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

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-24 04:29:38 UTC

Summary

Status Count
Total Open PRs 36
PRs with Failing Checks 33
PRs with All Checks Green 3
READY 3
FAILING 33
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=403499176a5d != 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 merged commit e91cb7e into master Sep 24, 2026
28 of 38 checks passed
gHashTag added a commit that referenced this pull request Oct 7, 2026
…ks (Closes #7457) (#7458)

b5b852f (#4730) made gf16's infinities strict-JSON strings and e91cb7e
(#4763) hand-edited the gf10 and gf256 prose; neither updated the sha256 in
INDEX_all_formats.json, so WP-18 check C went red on master.

Regenerated with gen_all_formats.py from the committed SSOT rather than
editing hashes by hand: gf10's notes return to the generator's text, the
gf16 and gf256 digests are recorded, and tnf16 picks up the catalog's
phi_distance 0.0417 from 2e4093d (#4795). All 21 gf16 rows decode under
gf16.t27 (S1E6M9, bias 31) to their recorded decoded_f64_hex. The WP-18
gate is CLEAN.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

[conformance] Promote gf10 and gf256 to bitexact_selfconsistent (WP-34)

2 participants