Repository navigation
docs(findings): H1 reproduced on air; explorer reaches #43, #45, #48 - #90
Merged
Merged
Conversation
#48 Adds the on-air reproduction of hypothesis H1 (a station stranded in Timer Recovery when the clearing acknowledgement arrives on an I frame): M0LTE (axcall 0.2.27) to GB7RDG (LinBPQ 6.0.25.23) on 40 m QPSK 3600 on 10 September 2026, with the KISS tee dropping exactly one of our I frames. After the recovery the stranded station sent no keepalive poll in 290 s; the identical control run polled at +120 s and +240 s. The decoded transcripts, axcall output and the run script are checked in verbatim under docs/evidence/h1-timer-recovery-2026-09-10/. Also folds in packet-net/ax25sdl#90: with flow-control moves and a v2.0 stub peer the explorer now reaches #43, #45 and #48 unprompted (seven of the nine live defects), and one of the brief's assumptions is corrected: from a cold connect #44 masks #45, because figc4.2 swallows the FRMR and retries with SABM. The H3 note (the DL-FLOW-OFF/ON busy arms emit RNR/RR with no N(r) staging) is recorded under limits. Next steps now lead with filing H1. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014qyx5dT8rmRTb8szT4SpEQ
This was referenced Sep 10, 2026
M0LTE
added a commit
that referenced
this pull request
Sep 10, 2026
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.
Two updates to the findings report.
H1 reproduced on air. M0LTE (axcall 0.2.27, the packet.net stack) to GB7RDG (LinBPQ 6.0.25.23) on 40 m QPSK 3600, 10 September 2026. The KISS tee dropped exactly one of our I frames; T1 polled, GB7RDG answered F=1 with a partial N(r), we retransmitted, and the clearing acknowledgement came back on GB7RDG's reply I frames. From that point the station sent no keepalive poll in 290 s. The identical control run, nothing dropped, polled at +120 s and +240 s. Transcripts, axcall output and the run script are checked in verbatim under
docs/evidence/h1-timer-recovery-2026-09-10/. The report's H1 section now carries the decoded exchange and says what the transcript does and does not show (LinBPQ itself is not stranded, and is not expected to be).Explorer reach. With packet-net/ax25sdl#90 the two-station explorer has flow-control moves and a hand-written v2.0 peer, and reaches #43, #45 and #48 without being told where to look, seven of the nine live defects. One assumption in the brief is corrected: from a cold connect #44 masks #45, since figc4.2 swallows the FRMR and retries with SABM. The calibration table, the reading paragraph, the limits (a new H3 note on the busy arms' missing N(r) staging) and the next steps are updated; filing H1 is now the first item.
🤖 Generated with Claude Code
https://claude.ai/code/session_014qyx5dT8rmRTb8szT4SpEQ