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:
@@ -14,11 +14,16 @@ phases:
|
||||
input: [requirements, technical_decomposition]
|
||||
deliverables:
|
||||
- product_selection
|
||||
- architecture_diagram
|
||||
- architecture_description
|
||||
- design_recommendations
|
||||
- target_architecture
|
||||
attachments: [target-architecture.json, architecture.mmd]
|
||||
approval: required # the Target architecture is approved before any code is written
|
||||
- id: solution_implementation
|
||||
input: [target_architecture]
|
||||
deliverables:
|
||||
- architecture_description
|
||||
- deployment_guidance
|
||||
attachments: [architecture.mmd, terraform/main.tf, terraform/variables.tf]
|
||||
attachments: [terraform/main.tf, terraform/variables.tf, implementation.json]
|
||||
approval: required
|
||||
- id: solution_validation
|
||||
input: [deployment_guidance]
|
||||
@@ -34,7 +39,7 @@ verification:
|
||||
- step: 4
|
||||
check: solution-architecture-guide.md exists and is non-empty
|
||||
- step: 5
|
||||
check: workflow.yaml covers the four Phases and required artifacts exist
|
||||
check: workflow.yaml covers the five Phases and required artifacts exist
|
||||
- step: 6
|
||||
check: committed revision is published
|
||||
- step: 7
|
||||
|
||||
Reference in New Issue
Block a user