Requirements Traceability Matrix

Req-ID → issues → PRs → commits → test evidence → approval (CH-5, #9733). Requirement IDs are declared on issues as a req:<id> label or a Req-ID: body line, carried into plan comments, PR bodies, and commit trailers. Sources: Req-ID: lines in the last ≤500 PR-merge commits reachable from HEAD, plus Req-ID: references in test docstrings under tests/. Enforcement is a ratchet, not a gate: Req-IDs are mandatory only for the regulated change class (HydraFlowConfig.regulated_labels, default empty).

Section 1: Requirements

(no requirement IDs threaded yet — declare one with a req:<id> label or a Req-ID: line in an issue body)

Section 2: Untraced changes

Adoption ratchet: the fraction of window commits carrying no Req-ID: line. Pinned by the traceability disturbance dimension (disturbance/baselines/traceability.yaml) — it may only shrink. Raw counts are omitted on purpose; see the module docstring.

Scope	Untraced
(untraced) — PR-merge commits in the window (≤500) without a Req-ID: line	100%