Files
gcp_solution_architecture_a…/workflow.yaml
Jonathan Boniface 545097530b
Some checks failed
validation / verify (push) Failing after 10s
feat: scoping is the first Phase, completed in conversation (iteration 9 step 2)
Every Execution now begins by agreeing the scope, before requirements.

- A new Phase and Deliverable, produced by a scope analyst with two tools:
  scope_read shows what is settled and what is not; scope_set records fields
  with where each value came from (the request, the customer's answer, or an
  assumption with its reason). Code checks each value against the catalogue.
- With someone present the analyst asks for what is missing; with nobody
  present it assumes it, visibly. With no spec it drafts one from the request.
  A value the customer stated in the file is changed only by their own answer.
- A submission cannot leave an essential field unknown. Code writes the
  completed spec, the data every later Specialist reads, and the information
  register, from what was recorded.
- The spec's status follows the Execution: under review, approved, then
  locked as a Baseline. A Change request starts from the delivered scope.
- The requirements analyst derives from the agreed scope and no longer asks
  for what it settles.

About 80 tests assumed requirements came first; tests/scoped.py runs scoping
ahead of a test's own script, and tests about order and counts are updated.
Not run with real models.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 18:17:32 +01:00

52 lines
1.9 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: scoping
input: [workflow_request, scope_spec]
deliverables: [scope]
attachments: [scope.yaml, scope.json]
approval: required
- id: requirements_discovery
input: scope
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