Skip to content

numeric: paper_claims.t27 no longer states the withdrawn GF16 clock in claim 10 (Closes #10418) - #10422

Merged
gHashTag merged 1 commit into
masterfrom
fix/paper-claims-withdrawn-mhz
Oct 18, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/paper-claims-withdrawn-mhz

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #10418

What

Claim 10 of specs/numeric/paper_claims.t27 (merged in #10401) quoted the GoldenFloat abstract's testbench line along with its clock frequency. docs/nona-03-manifest/RESEARCH_CLAIMS.md, Retraction 2026-08-18, withdrew that frequency: it is a ring-oscillator toggle rate, not a GF16 path. After the merge, the withdrawn-live gate failed on that line.

The claim text now reads "35 of 35 testbench vectors pass; the clock printed beside them is withdrawn (RESEARCH_CLAIMS.md, Retraction 2026-08-18)". The verdict stays not checkable, so the totals are unchanged at 34 / 8 / 3. This is a one-string change.

Checked (Railway lab, t27c 0.5.2, zig 0.16.0)

  • t27c test-report specs/numeric/paper_claims.t27: 10 pass, 0 fail, 0 of 10 vacuous
  • t27c fmt output is byte-identical to the file
  • the file no longer matches the gate's pattern

The other red checks on #10401 were already red before this change and are not touched here: count-invariant (tnf*.t27 lost former_name) and claw-sarif (a GitHub App permissions 422).

🤖 Generated with Claude Code

…k in claim 10 (Closes #10418)

The testbench row stays not checkable; its text now points at RESEARCH_CLAIMS.md, Retraction 2026-08-18.
t27c 0.5.2 test-report on the Railway lab: 10 of 10 pass, 0 vacuous; t27c fmt leaves it unchanged.

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

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 11:29:43 UTC

Summary

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != 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).

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.

paper_claims.t27 states the withdrawn 323 MHz GF16 clock in a claim text

1 participant