Design is now approved before any infrastructure code is written (ADR-0005). A new target-architect Specialist produces one graph of Elements, Relationships and Checks; the diagram is rendered from it, deployment guidance must account for every Check, and validation gives a verdict per Check. Requirements, components, products and recommendations carry ids in data files, and a submission with a gap in the Requirements chain is refused. Also in this commit: - Customer cases group Executions, with an intent history per case - lesson candidates are captured when an Execution ends - evaluation gains chain, verdict, judged and interactive checks, and per-case thresholds - Terraform providers are cached between checks - the requirements analyst proposes defaults instead of asking - the legacy-baseline case and the checks that only read it are removed - ADR-0006 (Change requests) accepted; ADR-0004 and ADR-0007 proposed - plans for iterations 4 to 7 under .agents/plans/ Unproven with a real model: no evaluation run has completed on this design. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Step 1 — Implementation Detail
validation_resultsnow requires afindings.jsonattachment (FINDINGS_ATTACHMENTinapp/workflows/deliverables.py).check_findingsvalidates it at submission: a JSON list of objects withdeliverable(a Deliverable kind),severity(critical,high,medium,low),evidenceandrule.[]is valid and means a pass. Each problem is refused by field, for examplefindings.json[1].severity: must be one of ....agents/validator.mdtells the validator to attach it; the format and an example live inskills/iac-validation/SKILL.mdunder "Reporting findings".- The file is written with the other attachments to
deliverables/executions/<id>/findings.json.
The check was added to check_submission, not to app/tools/execution.py as planned, so every contract rule stays in one function.
Tests: tests/execution/test_deliverables.py (missing attachment, empty list, well-formed finding, malformed JSON, per-field problems).
Not verified: no real-model run has confirmed the validator produces a well-formed file on its first submission. A malformed one costs a retry inside the validator's run, not a Revision.