fix(trace): REQ-PTT-01's statement was a paraphrase; add REQ-PTT-04 (#1411)

[dc0sk]

REQ-PTT-01's yaml statement restored to its ratified prose and re-pointed covered_by: CAP-74 → CAP-59; new REQ-PTT-04 (enforced, CAP-59) for the keying property that had no id; three // VERIFIES: REQ-PTT-04 bindings; the kiss keying test added to CAP-59's tests:; prose added to requirements.md.

The issue half-dissolved, and the reason is a registry defect

#1411 claimed no requirement states the PTT keying property. True for one half, false for the other — my sweep searched the yaml statement: fields, and the ratified prose says something else:

requirements.md:398-402 — Every PTT-keyed transmit scope shall release the transmitter deterministically on scope exit — including on an early return or a panic/unwind — via an RAII guard … (REQ-PTT-01)

The yaml carries PTT assert/release within 50 ms. Provenance by git log -S:

commit	what it did
f4c10467 (#872)	created REQ-PTT-01 as the RAII release guard
daa1676e (#1098)	wrote a traceability-matrix row paraphrasing it as the 50 ms clause, citing the wrong test
1da27abd (#1117)	imported that row into requirements.yaml as the statement

The importer was later deleted (#1223), so the yaml became source of truth carrying the paraphrase. The code agrees with the prose, not the yaml — shared_ptt.rs:221,413,869 all cite REQ-PTT-01 for the RAII guard. Nothing checks a yaml statement against its prose.

Consequence: the stuck-key failure mode was registered all along, and several trailers #1402 called "defensible but pointing at a timing requirement" are simply right.

A live #1405 instance, fixed here

REQ-PTT-01 was covered_by: [CAP-74] ("PTT backends"), which does not own shared_ptt.rs — the file its own acceptance test lives in, owned by CAP-59. Its coverage was bound to the paraphrase's evidence rather than to its requirement.

What was genuinely missing → REQ-PTT-04

REQ-PHY-07/08 say which PTT backends must exist; nothing said the configured one is used on every emission. Swept unkeyed|stuck key|keys the transmitter|every emission|dead RF|jammed across requirements.md, regulatory.md, the 1.0 criteria, AGENTS.md and the roadmap: zero hits (positive control: 3 in CLAUDE.md). It shipped broken independently in three front-ends with the same silent symptom, which is why the binding sits in each front-end rather than only at the seam.

Capability: CAP-59, not a new one

A "keying discipline" capability owning bridge.rs would recreate precisely what #1399's maintainer decision measured and rejected — extending CAP-59 into its importers turned two ARDOP/KISS receive mislabels into passes, because file-level overlap cannot separate two concerns in one file — and would rebuild the CAP-68 shape flagged the day before. CAP-59 is the registry's own precedent (these tests were twice added to CAP-59.tests) and mirrors REQ-SEC-13/CAP-77: the capability owns the seam, source scans hold the sites.

Two of my arguments were dropped

• Atomicity was imported. I proposed splitting on iterative-delivery's "requirements must be atomic". Compound statements are this registry's norm (CTL-02, SEC-14, CTL-04, DISC-04, QRM-01). The split stands instead on provenance, evidence tier and mechanism.
• "Externally observable" was worthless as a criterion — every defect is observable as silence. What survives is the hole between two existing ids.

Corrections to #1411's text

Ten commits carry Implements: REQ-PTT-01, not eight; "PTT-01 is the only PTT requirement" is false (PTT-02/03, PHY-05/07/08); and CLAUDE.md's 50 ms row names REQ-PHY-05 only, so the "control-path and audio-path halves" pairing was mine, not the repo's.

Verification

GATE: PASS 0e42ea2f9d843dd2ebc5f231f4dee45f18bc767d clean 20260919T095255Z

All eleven steps. Run fresh on this exact commit deliberately: the new enforced binding's evidence should not rest on a verdict from an earlier tree.

Implements: REQ-PTT-04

Review: docs/dev/reviews/review-1411-keying-requirement.md

🤖 Generated with Claude Code

https://claude.ai/code/session_0188ATCj6DZ9aRVQ2vSirua6