vwemirror/TeslaRel410
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

RC1 acceptance PASS: E0000305 after check — edit 6 verified on both paths

Browse Source 
Over-threshold check exchange repaints and re-renders a live E0 readout
(not the stale 04000000). The +2 drift in $3184 among 65 status frames
refines the counter model: $3184 = started timeout-retry sequences
(give-ups are the exhausted subset); timeout-recovered cycles exit via
the success teardown, NAK-recovered ones via $DA2F ($3185). All
observations from both bench sessions fit. Mash spot-check remains
before christening RIO 4.3.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Cyd
2026-07-19 16:46:53 -05:00
co-authored by Claude Fable 5
parent dd78d323f3
commit e7869a6d04
1 changed files with 14 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RIOv4_2-ANALYSIS.md
+14 -4
View File
@@ -531,8 +531,18 @@ first counter event — `04000000` flashes momentarily, then `E000000x`
as errors accrue and the reply-latch wedge trips under load. The wedge as errors accrue and the reply-latch wedge trips under load. The wedge
fix plus the E0 threshold gate are what exposed the stale frame. fix plus the E0 threshold gate are what exposed the stale frame.
**RC1 first-light (burned 2026-07-19): PASS on the below-threshold **RC1 acceptance (burned 2026-07-19): PASS on both edit-6 paths.**
path** — a version+check exchange now leaves the display at `F0000000`. Below threshold: a version+check exchange leaves the display at
Remaining for the RIO 4.3 christening: over-threshold check repaint `F0000000`. Over threshold: the full `--e0test` sequence reproduced the
(must re-render the E0 readout), `--e0test` regression, mash certified behavior (held `F0000000` through four sub-threshold events,
flipped at the 5th teardown), and the closing CheckRequest — 65 status
frames — left the display at **`E0000305`**: repaint + live E0
re-render, not the stale `04000000`. The `$3184`=03 (vs predicted 01)
pins down the counter semantics one notch further: two of the 65 check
frames hit a timeout-retry that our late ACK then rescued — so
**`$3184` counts started timeout-retry sequences** (give-ups are the
subset that exhaust all 5 retransmits), and a timeout-recovered cycle
exits via the success teardown (no `$3185`), while NAK-recovered cycles
tear down through `$DA2F` (`$3185`). Every observation from both bench
sessions fits this model. Remaining for the RIO 4.3 christening: mash
spot-check. spot-check.