# L-06: Do Not Mark Requirements as Not Applicable Status: ready-for-agent Deliverable: target_architecture Evidence-key: cd5ae98124 Proposed: 2026-10-09 Published: 2026-10-09 ## Rule Do not list Requirements in the not applicable field, as this field is strictly for Design Recommendations. Ensure every Requirement has at least one Check. ## Why The submission tool will reject the deliverable if a Requirement lacks a Check or is incorrectly marked as not applicable. ## Evidence Seen in 2 of 21 Executions, 2 times in all: submit_deliverable refused: Not submitted. The Deliverable is missing: Requirement … has no Check; Requirement … has no Check; Requirement. ## Proof Evaluation without lessons: `20261009T195603Z`; with: `20261009T195607Z`. | Case | Score | Revisions | Minutes | Tokens (M) | | --- | --- | --- | --- | --- | | case-03-internal-web-app | 1.00 → 1.00 | 1 → 0 | 28 → 22 | 3.00 → 2.32 | Quality held and revisions, seconds, tokens fell: kept. This compares every published lesson together, on one run each way. Runs of the same case vary, so one pair suggests a direction and does not settle it. ## Comments Approved by the owner on 2026-10-09.