Files
gcp_solution_architecture_a…/skills/scoping/SKILL.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

2.3 KiB

name, description, metadata
name description metadata
scoping The scope spec: the structured statement of what a customer wants and the facts a solution architecture depends on, with the catalogue of its fields. Use when reading a scope spec in your context, to know what a field means, whether the customer stated it or left it to you, and what binds your Deliverable.
scope
every Deliverable

Scoping

A scope spec is a YAML file the customer's architect supplies, complete or partly filled. It sits beside the Intent, which stays in the customer's words. assets/catalogue.yaml lists every field it may hold: its type, when it must be settled, the question to ask for it, and guidance for a default.

What a field says

In the spec Meaning
a value The customer states this. It is theirs: use it as given.
ask, or left out Not known yet.
decide The customer leaves the choice to you. Choose, and record it as an assumption with what it affects.
not_applicable It does not apply. Ask nothing and assume nothing.

Rules for every Specialist

  • A stated value binds you. A region, a topology, a product, a setting or a number the spec states is the customer's decision. Honour it. If you believe it is wrong, say so with needs_input; do not quietly replace it.
  • A stated choice is not yours to generalise. The rule that requirements name no products is about what you introduce. What the customer wrote stays as they wrote it.
  • Build nothing the customer excluded. intent.exclusions is out of scope for every Deliverable.
  • The customer's own requirements carry their ids. Each entry in intent.requirements must be met. When your work serves one, name its id.
  • Do not fill a gap silently. A field under to_ask is unknown: ask for it when you may ask the user, and otherwise assume a default and say so. A field under to_decide is yours to choose: record the choice as an assumption.

The kinds of engagement

engagement.kind is workload (an application), platform_foundation (a landing zone or shared platform that workloads will later run on) or migration. A platform foundation has no users or response times of its own: its subject is the organisation's structure, shared networking, identity, environments and guardrails.