Files
Jonathan Boniface 0f80cb642f
Some checks failed
validation / verify (push) Failing after 11s
feat: a stated choice must reach a requirement, and only pinned providers (iteration 9 step 3)
Case 08 named the customer's stated topology in its design and did not build
it; every Check passed because none asked for it.

- The catalogue marks the 26 fields that bind a design. The agreed scope lists
  the ones the customer stated; what was assumed for them does not bind.
- A requirement says what it comes from. A submission of requirements is
  refused when one of the customer's own requirements, or a stated binding
  field, is named by none, or when the requirement carrying a choice is not a
  constraint with a condition. The existing chain then owes it a Check.
- Generated code may use only the providers the bundle pins: a resource or a
  required_providers entry of any other is refused before Terraform runs.
- The guide opens with how much of the design the customer stated, how much
  was assumed and how much is unknown.

Not run with real models.

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

2.1 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: steps 1, 2, 3 and 6 built on 2026-10-11; steps 1 and 2 ran in cases 03 and 08; step 3 not run; steps 4 and 5 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 built 2026-10-11 (steps/step-2.md); not run with real models
3 Requirements traced to the customer's requirement ids and to spec fields, in requirements.json, with a stated choice refused unless a requirement carries it; readiness in the solution guide built 2026-10-11 (steps/step-3.md); not run with real models
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 built with step 2

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.