Repository navigation
rational: the streaming ratchet rows re-recorded, with the reason (A1) - #80
Merged
Merged
Conversation
The thirteen streaming rows of rational/bench/baselines.json were the 2026-10-02 record (v0.10); three commits since moved them inside the ±3 % gate without re-recording, so the gate measured from a tree other than the one it guards. Re-recorded on all three targets from main at c120bc9 (arm-none-eabi-gcc 13.2.1, CodeLinaro 19.1.5, qemu 8.2.2 with the tree's plugin: the toolchains that reproduce the committed rows to the instruction, and bridge's twelve and async's eight rows --exact on M33, M55 and Hexagon, so only rational moves). The construct row, recorded 2026-10-10, is unchanged. The reason, traced by rebuilding the M55 workloads at every commit from 4eb1180 to e71d0b1: ab8fea3 (v0.11, the power-of-two row gain for the Q15 mixed ratios going down) is the one visible move, ratio23_q15_eco +355,117 on the M55 (+1.93 %, stated as +1.9 % in its commit), +7,346 on the M33 and -224 on Hexagon; d4fff5c (v0.13, the mirror-exact designer, the stage.h snap removed) added a construction-side constant per workload (M55 +76 by-2, +112 by-3 and 2/3, +196 transparent, +128 the chain; M33 +192 / +158 / +545 / +1,102; Hexagon +52 / +69 / +132 / +2,201); the DspTap bump to tap/DspTap#57 (82cd646) added +798 to the chain's construction on the M55. Every other commit re-measures identically; the sweep also shows #72's S1 sitting +3.5 ... +8.8 % until 391145d took it back, as that commit records. rational/PLAN.md carries the record (v0.15) beside the hand-kept table; the README table is regenerated. bridge/CLAUDE.md's ratchet sentence now says "beyond tolerance", the family rule in the root CLAUDE.md: a count that moves inside the gate is re-recorded when the record is corrected, as here, not on every change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016GKzq1VSdcMYCRMhddiMaf
tap
pushed a commit
that referenced
this pull request
Oct 12, 2026
Q1: the bench is USB asynchronous mode, with the Pico 2 as the asynchronous-mode device on its own crystal (its USB audio firmware joins A11), and it runs twice, so the timestamp servo is a 1.0 item (B3, C1, the verdict rule). Q2: no outside consumer links a C ABI; MAJOR is the ABI; FetchContent and add_subdirectory are the only supported consumption at 1.0 (C3). Q3: as landed in A1 (#80). Q4: DspTap tagged independently, the minimum asserted (A9). Q5: probably our own Pico 2 firmware, by the maintainer's recollection, unconfirmed; A3 landed regardless (#81). Q6: the host ratchet is a hard gate at ±3 % (A8). Each question stays as asked, with its decision beneath it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016GKzq1VSdcMYCRMhddiMaf
tap
pushed a commit
that referenced
this pull request
Oct 12, 2026
Q1: the bench is USB asynchronous mode, with the Pico 2 as the asynchronous-mode device on its own crystal (its USB audio firmware joins A11), and it runs twice, so the timestamp servo is a 1.0 item (B3, C1, the verdict rule). Q2: no outside consumer links a C ABI; MAJOR is the ABI; FetchContent and add_subdirectory are the only supported consumption at 1.0 (C3). Q3: as landed in A1 (#80). Q4: DspTap tagged independently, the minimum asserted (A9). Q5: probably our own Pico 2 firmware, by the maintainer's recollection, unconfirmed; A3 landed regardless (#81). Q6: the host ratchet is a hard gate at ±3 % (A8). Each question stays as asked, with its decision beneath it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016GKzq1VSdcMYCRMhddiMaf
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
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.
What this changes
Re-records
rational's thirteen streaming ratchet rows on M33, M55 and Hexagon (rational/bench/baselines.json; the README table regenerated;rational/PLAN.mdv0.15 carries the record beside its hand-kept table).bridge/CLAUDE.md's ratchet sentence now says "beyond tolerance", the family rule in the rootCLAUDE.md. The roadmap's A1 entry is marked landed. Block A's first item (docs/ROADMAP.md A1).Why
The rows were the 2026-10-02 record, and three commits since moved them inside the ±3 % gate without re-recording, so the gate measured from a tree other than the one it guards (the one M55 row at +1.93 % left the gate 1.07 % of headroom for a real regression). The precedent for an in-band re-record with a stated reason is
bridge/PLAN.mdM7e andasync/docs/PERFORMANCE.md"Hexagon harness isolation". Re-recordingrationalalone follows the roadmap's Q3 recommendation; it is also what the measurements say, sincebridgeandasyncre-measure exact.Verification
ci.yml's pins). They reproduce every committed row:bridge's twelve andasync's eight rows pass--exacton all three targets, andrational's construct row is +0 everywhere.ratio23_q15_ecomove (+355,117 on the M55, +1.93 %, stated as +1.9 % in its commit; +7,346 on the M33, −224 on Hexagon). d4fff5c (v0.13) adds a construction-side constant per workload (M55 +76 by-2, +112 by-3 and 2/3, +196 transparent, +128 the chain; M33 +192 / +158 / +545 / +1,102; Hexagon +52 / +69 / +132 / +2,201). The DspTap bump to chain: stages reset at construction and read-only through the chain DspTap#57 (82cd646) adds +798 to the chain's construction on the M55. Every other commit re-measures identically; the sweep also shows The 2026-10 adversarial audit and its response: S0 to S5, family version 0.6.0 #72's S1 sitting +3.5 to +8.8 % until 391145d took it back, as that commit records.scripts/check_retired_words.pyclean. Prose and JSON only: no C++ changed, so no build.Notes for the reviewer
🤖 Generated with Claude Code
https://claude.ai/code/session_016GKzq1VSdcMYCRMhddiMaf
Generated by Claude Code