docs: record case 06 passing after the verdict and naming fixes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-10 15:23:34 +01:00
parent c4c8a1f94e
commit 7ee7054523
2 changed files with 7 additions and 1 deletions

View File

@@ -45,3 +45,9 @@ Changed, not yet run:
- The IaC author is told what to do when a Check failed and the code already meets its words: change nothing, keep the implementation entry, name the Check it disputes, and not record it as unimplementable.
An overlay also makes a design larger: this run ended with over 120 Checks, against 50 to 90 for the same request without one.
## Case 06 again, with the fixes (2026-10-10)
`20261010T134034Z`: completed, 100%, 45 minutes, about $5.43, 126 Checks, all passed. `code_follows_standards` passed. Two Revisions of the Target architecture, both ordinary: locations the validator wanted checked (L-10's subject, the persistence regions of a topic, among them), and two Checks on one secret that contradicted each other.
No Check was failed for something it does not say, and none was disputed, so the two new instructions were not put to the test: the run shows they do no harm, not that they work.