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

@@ -0,0 +1,117 @@
# A benchmark scope spec: a regulated platform foundation. A fictional customer.
schema_version: 1
metadata:
engagement_id: case-08-landing-zone
client_name: Example Payments UK
author: Evaluation
revision: "1.0.0"
engagement:
kind: platform_foundation
intent:
statement: |
We are a UK-regulated payment platform expanding into Google Cloud. We need an
enterprise-grade landing zone ready in under 10 weeks to support our core payments
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
existing on-premises systems that require private, low-latency connectivity over a
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
GitHub Actions for our delivery pipelines. Security requires that all egress
traffic flows through centralised inspection appliances before touching the public
internet, and customer data must be encrypted with keys we control.
requirements:
- id: REQ-01
category: Timeline
statement: Platform foundation must be ready for workload ingestion within 10 weeks.
- id: REQ-02
category: Compliance
statement: Must achieve DORA resiliency alignment and PCI-DSS v4.0 perimeter isolation.
- id: REQ-03
category: Networking
statement: 10Gbps on-premises hybrid connectivity; centralised inspection appliances for egress.
- id: REQ-04
category: Identity and security
statement: Workload identity federation with GitHub Actions; Entra ID single sign-on; customer-managed encryption keys.
exclusions:
- Application container deployment; workloads are managed by application squads.
- An active-active secondary region in phase 1; warm standby is acceptable.
success_criteria: decide
estate:
cloud_provider: gcp
mode: greenfield
regions:
primary: europe-west2
secondary: europe-west1
resiliency_tier: warm_standby
data_residency: United Kingdom and European Union
existing_systems: On-premises payment systems that stay in place and connect over the interconnect.
workload:
users: not_applicable
availability:
target: decide
hours: always
recovery_time: decide
recovery_point: decide
compliance:
industry: financial_services
frameworks: [DORA, ISO27001, PCI_DSS_v4]
data_classification: confidential
encryption:
type: cmek
key_rotation_days: 90
audit_logging:
retention_days: 365
immutable_retention_policy: true
networking:
exposure: internal_only
topology: shared_vpc_hub_and_spoke
hybrid_connectivity:
enabled: true
type: cloud_interconnect
bandwidth_gbps: 10
egress_control:
model: centralized_appliance
appliance_vendor: decide
cidr_allocations: decide
governance:
identity_source_of_truth: Entra ID
pipeline_authentication: workload identity federation
environment_tiers:
- {name: development, archetype: corp_workload}
- {name: staging, archetype: corp_workload}
- {name: production, archetype: pci_regulated_workload}
operations:
operating_model: central platform team brokering access for application squads
support_hours: always
monitoring: decide
change_process: decide
integrations: decide
delivery:
window_weeks: 10
commercial_model: fixed_price_milestone
iac_tooling: terraform
ci_cd: GitHub Actions
team_size: 3
working_days_per_week: 5
cost:
monthly_budget: decide
currency: GBP
constraints:
products_required: decide
products_forbidden: decide
run:
pre_approved: true
allow_cloud_read: false
terraform_modules: false