Files
gcp_solution_architecture_a…/.scratch/lessons/issues/06-do-not-mark-requirements-as-not-applicable.md
Jonathan Boniface a7bc5310f3 feat: the lessons loop, and six lessons approved and published
Capture, distil, review, publish, retire (ADR-0004). Lesson candidates of
past Executions are grouped into what recurred; a lesson-curator role,
outside any Execution, proposes a lesson per group worth one; each proposal
is an issue file a person approves or rejects; an approved lesson is
written into the provider's lessons Skill, which a Specialist is given only
once it holds lessons for that Specialist's Deliverable. LESSONS_ENABLED
off runs without them, for an evaluation with and without.

The curator proposed six lessons from 21 Executions. The owner approved all
six on 2026-10-09 and they are published: five for the target architect,
one for the IaC author. None is proved by an evaluation yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 15:19:32 +01:00

758 B

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

Not yet measured.

Comments

Approved by the owner on 2026-10-09.