fix: what only the provider publishes is outside code, not a condition

A requirement for a "low-carbon region" was written as a condition for code
to meet, and came back in at least five runs as a gap, an unverifiable Check
or review noise. The requirements-chain Skill and the two roles that write
conditions now put a carbon rating or a service level under outside_code;
the condition is the choice configuration can show, such as the region set.

Records the first runs with lessons L-07 to L-09: the faults they name did
not recur, and Revisions did not fall.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-10 13:31:48 +01:00
parent 5feaaa6271
commit 81ac135cd9
4 changed files with 27 additions and 3 deletions

View File

@@ -33,7 +33,7 @@ A list. Number functional requirements `FR-1`, `FR-2` and non-functional ones `N
]
```
Every non-functional requirement lists its `conditions`: one entry for each separate thing that must be true for it to be met and that infrastructure configuration can show. What it asks for that configuration cannot show goes under `outside_code`: an outcome measured in operation, behaviour of the application's own code, or a process people follow. A requirement has at least one entry between the two; one that is entirely outside code has `"conditions": []`. Write each so it can be checked on its own, and so that together they say everything the text says. The Target architecture needs a Check for each one.
Every non-functional requirement lists its `conditions`: one entry for each separate thing that must be true for it to be met and that infrastructure configuration can show. What it asks for that configuration cannot show goes under `outside_code`: an outcome measured in operation, behaviour of the application's own code, a process people follow, or a property of a region or product that only its provider publishes, such as a region's carbon rating or a product's service level. For those, the condition is the choice that configuration can show: "every resource is in the one agreed region" is a condition, and "that region has a high carbon-free energy score" is `outside_code`. A requirement has at least one entry between the two; one that is entirely outside code has `"conditions": []`. Write each so it can be checked on its own, and so that together they say everything the text says. The Target architecture needs a Check for each one.
`kind` is `functional` or `non_functional`. Write one requirement per entry, so each can be checked on its own.