Retract 323 MHz, and gate it so it cannot come back - #2178
Merged
Conversation
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
323 MHz was established on 2026-08-05 to be the toggle rate of a 20-stage LUT1
ring oscillator clocking a 23-bit counter -- not a path through any GF16
arithmetic. Four independent checks, each sufficient alone:
fpga/vivado/gf16_matmul4x4_top.v:22 is the design's ONLY sequential statement,
always @(posedge osc) on a counter, where osc = chain[19] is the ring output
grep -c posedge over gf16_{mul,add,dot4,matmul4x4}.v returns 0, 0, 0, 0
gf16_matmul4x4_top.xdc contains no create_clock, so 'PASS at 100 MHz' is a
default target on an auto-inferred domain holding only the counter
the synthesised design module in target/gf16-build/*.json holds 55 logic cells
-- LUT1 19, FDRE 23, CARRY4 6, BUFG 1, INV 4, OBUF 2 -- which is exactly the
ring, the counter, its carry chain and the LEDs. GF16 contributes zero cells
and zero DSP48E1 against 64 claimed, because the wrapper feeds it constants
A tell needed none of that: three designs whose claimed sizes differ by 62x
reported 330 / 322 / 323 MHz, a 2.5% spread. A real critical path cannot be
invariant to a 62x change in size.
Corrected in the three documents that state it as a live result -- the arXiv
draft, its .tex, and NUMERIC_FORMATS_SSOT.md -- covering the title, abstract,
resource table, timing section, throughput table and the sentence claiming all
of it came 'from actual FPGA hardware runs'. No replacement frequency is given,
because none was measured. The four dated WAVE_LOOP reports are left alone: a
record of what was believed on a date is not a live claim.
The retraction is registered in docs/nona-03-manifest/RESEARCH_CLAIMS.md, which
already carries the repository's rule that every strong statement appears there
with an ID or is downgraded.
Why a gate and not just an edit: the withdrawal was recorded in research notes on
2026-08-05 and 2026-08-08 and never reached the papers -- they still carried it
ten days later, through an intervening honesty pass over the same file that was
looking at a different sentence. tools/check_withdrawn_live.py now fails CI if a
withdrawn number appears in a live document, with the withdrawn list as data
(tools/withdrawn.txt) rather than code, and a --self-check negative control that
plants a hit and proves the scan fires. The gate found two places in the .tex
that this commit's own first pass had missed.
Closes #2179
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gHashTag
force-pushed
the
loop/t27-improve-2026-08-18
branch
from
August 18, 2026 10:00
4456035 to
e975a95
Compare
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-18 10:00:37 UTC
Summary
Seal Status
|
The gate fired on its own change: the NOW.md entry this PR adds states 323 MHz while explaining the retraction, and NOW.md is a live document. Baselining (file, pattern) would have silenced it, and would also have silenced every FUTURE occurrence in that file. NOW.md is append-only, so that hole would widen with each entry -- a gate that stops catching is worse than no gate, because it reads as coverage. The baseline is now keyed (path, pattern, sha1 of the normalised line). Text about a withdrawal passes; a new line stating the number does not, in the same file. Editing a baselined line re-opens the gate on it, which is the behaviour we want. Closes #2179 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-18 10:02:34 UTC
Summary
Seal Status
|
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
1 participant
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.
323 MHzis the toggle rate of a 20-stage ring oscillator clocking a 23-bit counter, on a netlist whose synthesised design module holds 55 logic cells — the ring, the counter, its carry chain and two LED drivers — and zero of the GF16 arithmetic being claimed, because the wrapper feeds the DUT literal constants. Four independent checks are in the commit message and in the registry entry.A tell needed none of them: three designs whose claimed sizes differ by 62× reported 330 / 322 / 323 MHz, a 2.5 % spread.
What this changes
.tex,NUMERIC_FORMATS_SSOT.md) — title, abstract, resource table, timing section, throughput table, and the "from actual FPGA hardware runs" sentencedocs/nona-03-manifest/RESEARCH_CLAIMS.mdWAVE_LOOP_*reports alone: a record of what was believed on a date is not a live claimWhy a gate
The withdrawal was recorded in research notes on 2026-08-05 and 2026-08-08 and never reached the papers — ten days, through an intervening honesty pass over the same file.
tools/check_withdrawn_live.pynow fails CI if a withdrawn number appears in a live document. The withdrawn list is data (tools/withdrawn.txt), and--self-checkis a negative control that plants a hit and proves the scan fires.It earned its keep immediately: it caught two places in the
.texthat this PR's own first pass had missed.🤖 Generated with Claude Code
Closes #2179