docs(cat-tx-ptt): rescope hardware-acceptance gates to what an operator can actually verify#75
Merged
Merged
Conversation
…or can actually verify 14.1 asked the operator to judge PTT lead/tail timing by eye against a millisecond threshold — not something a human can reliably do without lab equipment (oscilloscope, logic analyzer), which isn't assumed to be available. Reworded to a decode-based check instead: a monitoring receiver, second SDR, or the far station copying the transmitted message in full is sufficient evidence the timing didn't clip the signal, matching the evidence standard already accepted for Gate 16's two-way QSO. 14.3/15.4 (force the PttWatchdog failsafe and confirm automatic unkey) asked the operator to reconfigure an internal timing knob and orchestrate a component-level failure through the Settings UI — including, at one point, a suggested value that violated the form's own min="1000" constraint. Retired as manual hardware gates entirely: PttWatchdogTests.cs already deterministically covers PttWatchdog's fire/callback/Error-log behaviour in isolation, and ForceReleaseAsync/KeyUpAsync in both PTT controllers call the identical SetLine(line, asserted: false) primitive already proven correct on real hardware repeatedly (2026-07-12, 2026-07-14 field sessions). No manual step adds real confidence beyond what's already covered. Also records 2026-07-14 field evidence (logs/openswfz-20260714T184808Z.log): further reinforcement of 15.1 (RTS key/unkey via the PTT-test button and multiple QSO cycles), plus a real unprompted automatic PTT release — correctly identified as tx.WatchdogMinutes (the QSO-level give-up timer), not the PttWatchdog failsafe, so it does not satisfy the now-retired 15.4. Genuinely still outstanding, real hardware required: 14.1, 14.2, 14.4, 15.2, 15.3 — tracked as a running backlog in issue #74 since further items are expected as hardware-facing features grow. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Owner
Author
|
QA sign-off. Documentation-only change to OpenSpec artifacts (`tasks.md`/`hardware-acceptance.md`) — no code, tests, or CI surface touched, confirmed by the diff and by every `Build & Test` / `Gate G9` check passing unaffected. Content already walked through with the Captain in full before this PR was opened (gate rewording rationale, retirement of 14.3/15.4, 2026-07-14 field evidence). Merging as-is. |
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.
Summary
threshold — replaced with a decode-based check (monitor/second SDR/far-station copy in full),
matching the evidence standard already accepted for Gate 16.
PttWatchdogfailsafe) retired as manual hardware gates entirely —already covered by
PttWatchdogTests.csplus the proven-identicalSetLine(line, asserted: false)de-assert path shared with normal
KeyUpAsync, already exercised on real hardware repeatedly.logs/openswfz-20260714T184808Z.log): further reinforcement of15.1, and a real auto-unkey correctly attributed to
tx.WatchdogMinutes(notPttWatchdog), so itdoes not satisfy the now-retired 15.4.
genuinely outstanding: 14.1, 14.2, 14.4, 15.2, 15.3 — tracked as a running backlog in Hardware acceptance backlog — gates blocked on rig/wiring configuration not yet set up #74.
Test plan
closing status summary, archive-gate note) — all updated to match, not just the two checkboxes.
🤖 Generated with Claude Code