requirements-capturelisted

# DO-254 Hardware Requirements Capture (avionics/do254/requirements-capture) Use when the task is DO-254 hardware requirements capture: checking requirement characteristics, identifying derived requirements, and gating the requirements review for airborne electronic hardware. ## Domain quick reference - DO-254 hardware requirements must be complete, correct, and verifiable, with unique identifiers and trace links. - Derived requirements: added during design or safety analysis with no direct higher-level source; they must be identified and justified, and they count as requirements for verification. - Allocated requirements trace upward to a system requirement; derived requirements do not. - Vague wording (suitable, adequate, approximately, and similar) fails the verifiability test at the requirements review. ## Workflow 1. Collect each hardware requirement with its identifier, text, and trace status. 2. Run the characteristic check with req_issues. 3. Classify each requirement as derived or allocated with classify_derived. 4. Score capture readiness with capture_readiness. 5. Gate the requirements review on the issue list and readiness. ## Pitfalls - Accepting vague wording because the design intent is clear. - Missing trace links on allocated requirements. - Letting derived requirements appear without a justification note. ## Behavior contract (gate 3) The requirement-characteristic, classification, and readiness logic is exercised by the gate 3 contr