Files
gcp_solution_architecture_a…/workflow.yaml
Jonathan Boniface e9246828b3 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>
2026-10-07 13:59:09 +01:00

47 lines
1.8 KiB
YAML

name: gcp-solution-architecture-workflow
source_template: https://github.com/workflow_agent/template
repository: gcp_solution_architecture_agent
# Phases and their Deliverables mirror app/workflows/deliverables.py, the single source
# for the dependency graph. A Phase completes when every Deliverable is submitted and the
# user grants its Approval. Outputs are written to deliverables/executions/<execution_id>/.
phases:
- id: requirements_discovery
input: workflow_request
deliverables: [requirements, technical_decomposition]
product_selection_deferred: true
approval: required
- id: solution_architecture
input: [requirements, technical_decomposition]
deliverables:
- product_selection
- 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: [terraform/main.tf, terraform/variables.tf, implementation.json]
approval: required
- id: solution_validation
input: [deployment_guidance]
deliverables: [validation_results]
deploy_resources: false
approval: required
- id: packaging
input: [validation_results]
deliverables: [solution_guide]
output: solution-architecture-guide.md
approval: required
verification:
- step: 4
check: solution-architecture-guide.md exists and is non-empty
- step: 5
check: workflow.yaml covers the five Phases and required artifacts exist
- step: 6
check: committed revision is published
- step: 7
check: remote revision contains workflow.yaml and solution-architecture-guide.md