# Step 5 — Implementation Detail `chain_gaps` in `app/workflows/target_architecture.py` lists every place the Requirements chain stops; `check_target_architecture` runs it at submission, so a Target architecture with a gap is refused with each gap named. A gap is: - a component with no Element; - a non-functional requirement that is the source of no Check; - a functional requirement that is the source of no Check and is served by no component with an Element; - a selected product that does not appear on its component's Element; - a recommendation that is the source of no Check and is not listed under `not_applicable` with a reason; - a Check whose `source` is not a requirement or recommendation, or an Element that realises something that is not a component. Recommendations marked not applicable are carried in the graph's summary and shown to the user at the design Approval. The rule checks that each link exists, not that it is right. A vague Check passes here and is caught later as `not_verifiable`, or by the user at Approval. Tests: `tests/execution/test_requirements_chain.py`, "the Requirements chain has no gap", including one through `submit_deliverable`.