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

@@ -95,3 +95,27 @@ Over the same 32 Executions this gave 22 groups and five proposals, L-07 to L-11
A first run of `propose` before this change produced one proposal, about giving `edit_file` enough context. It was removed to run again cleanly and was not proposed the second time.
Tests: `tests/test_lessons_loop.py` (3 more).
## The three new lessons, run once (2026-10-10)
Case 03, two runs with the eight lessons (`20261010T114823Z`, `20261010T114827Z`). Both completed at 100%.
| | Run 1 | Run 2 |
|---|---|---|
| Minutes | 30 | 37 |
| Cost, about | $3.27 | $5.19 |
| Revisions of the Target architecture | 1 | 2 |
None of the three faults the new lessons name came back: no separate backup encryption key, no backend service fault. The Revisions were for other things:
- The validator proposed a Check that the service identity holds no project-wide administrative role.
- A Check asked for an encryption key and the design had no key Element for it to name.
- A Check that the region has a high carbon-free energy score could not be verified from the code.
The last is partly L-07's doing. It says to add a location Check where a requirement asks for a low-carbon location, and the architect wrote one about the carbon score, which no code can show.
Across the twelve runs of this request on 2026-10-09 and 10 the Target architecture was revised 0, 1, 1, 1, 1, 3, 1, 1, 0, 1, 1 and 2 times. Lessons have removed particular faults and not lowered the count: each run finds another.
## Fixed at its source: what only the provider publishes
The carbon-score condition came up in at least five runs, as a gap, as an unverifiable Check and as noise in two reviews. It was being written as a condition for code. The requirements-chain Skill and the two roles that write conditions now say that a property of a region or product that only its provider publishes (a carbon rating, a service level) goes under `outside_code`, and the condition is the choice configuration can show, such as which region is set. Not run.