feat: establish the Target architecture as a graph before code
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>
This commit is contained in:
@@ -36,12 +36,18 @@ async def test_submission_takes_attachments_as_a_list():
|
||||
content=GUIDANCE,
|
||||
attachments=[
|
||||
{"path": "terraform/main.tf", "content": "resource {}"},
|
||||
{"path": "terraform/variables.tf", "content": ""},
|
||||
{"path": "terraform/variables.tf", "content": "variable {}"},
|
||||
{"path": "implementation.json", "content": "[]"},
|
||||
],
|
||||
)
|
||||
|
||||
assert result.outcome == Submitted(
|
||||
GUIDANCE, {"terraform/main.tf": "resource {}", "terraform/variables.tf": ""}
|
||||
GUIDANCE,
|
||||
{
|
||||
"terraform/main.tf": "resource {}",
|
||||
"terraform/variables.tf": "variable {}",
|
||||
"implementation.json": "[]",
|
||||
},
|
||||
)
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user