feat: start an Execution from a scope spec (ADR-0008, iteration 9 step 1)
Some checks failed
validation / verify (push) Failing after 10s

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>
This commit is contained in:
2026-10-11 17:53:00 +01:00
parent a48468d477
commit afe78640f8
27 changed files with 2122 additions and 8 deletions

View File

@@ -57,6 +57,17 @@ role_skills:
# once it holds lessons for that Specialist's Deliverable.
lessons_skill: google-cloud-lessons
# The scope spec (ADR-0008). `skill` holds its catalogue, which names no Cloud
# provider. `values` are what this provider allows for the fields the catalogue
# leaves to a provider, in this provider's own terms.
scope:
skill: scoping
values:
estate.cloud_provider: [gcp]
compliance.encryption.type: [cmek, cmek_hsm]
networking.topology: [single_vpc, shared_vpc, shared_vpc_hub_and_spoke]
networking.hybrid_connectivity.type: [cloud_vpn, cloud_interconnect, partner_interconnect]
# One advisor per architecture-framework pillar; each loads only its pillar's Skill.
pillar_skills:
security: google-cloud-waf-security