Files
gcp_solution_architecture_a…/.agents/plans/iter-09-scoping/MAP.md
Jonathan Boniface afe78640f8
Some checks failed
validation / verify (push) Failing after 10s
feat: start an Execution from a scope spec (ADR-0008, iteration 9 step 1)
A scope spec is a YAML file of what the customer wants and the facts a design
depends on, complete or partly filled. It sits beside the Intent, which stays
in the customer's words.

- skills/scoping holds a provider-neutral catalogue of 63 fields; the Cloud
  provider's bundle supplies the values it allows for the fields left to it.
- app/scope.py reads a spec against the catalogue with no model: it refuses an
  unknown field or a value of the wrong type, and yields what is stated, what
  is left to the agent, what is unknown and how pressing each gap is. A field
  may say ask, decide or not_applicable.
- ExecutionEngine.start(scope=...), /generate, A2A metadata and evaluation
  cases accept one. Its statement is the request, its engagement reference
  names the Customer case, and its run options apply. A pre-approved start is
  refused when an essential field is not settled.
- The spec as supplied is kept unaltered beside a completed copy with
  assumptions, gaps, provenance, readiness and a status.
- Every Specialist is shown the spec and given the Skill: a stated choice
  binds, exclusions are out of scope.
- Covers workloads and platform foundations; case-08-landing-zone starts from
  a benchmark spec.

Plans for scoping (iteration 9) and the work breakdown structure (iteration
10, nothing built), and the design spec they come from. Not run with real
models.

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

1.9 KiB

Plan Map

Iteration: 9, Scoping Intent: Scope an engagement from a scope spec: a structured file that may arrive complete, partly filled or not at all, completed in conversation and approved by the customer before requirements begin. So that a design's quality no longer rests on what the agents had to assume. Status: step 1 built on 2026-10-11, not run with real models; steps 2 to 6 planned This directory covers: steps 1 to 6

Sources of truth

  • docs/adr/0008-scoping-starts-from-a-scope-spec.md: the decisions.
  • .scratch/scoping-and-work-breakdown/spec.md: the design, including the draft spec, the owner's own example and how the two were combined.
  • skills/scoping/assets/catalogue.yaml: every field a scope spec may hold.

Status

Step What Status
1 The catalogue, reading and validating a spec, the gap list, the two files beside the Intent, run options from the spec, the spec shown to every Specialist built 2026-10-11 (steps/step-1.md); not run with real models
2 The conversation that fills gaps and writes answers into the completed copy; scoping as a Phase with its Deliverable and Approval; a spec drafted from a sentence planned
3 Requirements traced to the customer's requirement ids and to spec fields, in requirements.json; readiness in the solution guide planned
4 An edited spec as a Change request, compared field by field planned
5 Evaluation cases as specs, replacing answers matched by pattern planned; case-08-landing-zone is the first
6 The status BASELINE_LOCKED set when the Execution completes planned

Dependency graph

  • Step 1: no dependencies
  • Step 2: depends on step 1
  • Step 3: depends on step 1
  • Step 4: depends on step 1, iteration 7
  • Step 5: depends on step 1
  • Step 6: depends on step 2

The work breakdown structure is iteration 10 and uses the spec's delivery section from step 1.