feat: the solution architecture agent on the shared Execution engine

The reference agent's subject, cloud solution architecture, as an agent in
the operating model agent's pattern: the Execution engine (from
orchestration_engine) and one Workflow in app/solution_architecture,
built for the settings and provider bundle by assembly.workflow_for.

Copied from gcp_solution_architecture_agent at 8b397cd without its own
engine: its role files, Skills, provider bundle, ADRs, vocabulary, scripts
and evaluation datasets. The image takes the engine from a named build
context and installs Terraform. It is called through the Orchestration
engine, and its files are what the operating model agent digests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-21 19:49:28 +01:00
commit c84dbdea20
127 changed files with 14672 additions and 0 deletions

View File

@@ -0,0 +1,345 @@
# The scope spec's catalogue: every field a scope spec may hold.
#
# A field is a dotted path. `type` is one of: string, text, integer, number, boolean,
# date, list, enum, records. `tier` says when it must be settled: essential (always,
# before any work), important (asked when someone is present) or optional. A tier
# may differ by the kind of engagement. `question` is what to ask the customer for
# it. `default` guides the choice when the customer says "decide". `affects` says
# what a wrong assumption would change. `binds: true` marks a choice a design must
# honour: stated by the customer, it has to reach a requirement and its Checks.
#
# This catalogue names no Cloud provider. A provider's bundle adds allowed values
# for the fields marked `provider_values`.
schema_version: 1
kinds: [workload, platform_foundation, migration]
fields:
metadata.customer_case:
type: string
tier: essential
aliases: [metadata.engagement_id]
question: What short reference identifies this engagement?
metadata.engagement_reference:
type: string
metadata.client_name:
type: string
metadata.author:
type: string
metadata.revision:
type: string
engagement.kind:
type: enum
values: [workload, platform_foundation, migration]
tier: essential
question: >-
Is this an application workload, a platform foundation such as a landing zone,
or a migration of existing systems?
intent.statement:
type: text
tier: essential
question: In the customer's own words, what do they want?
intent.requirements:
type: records
keys: [id, statement]
optional_keys: [category]
question: Which requirements has the customer stated outright?
intent.exclusions:
type: list
tier: important
question: What has the customer said is out of scope?
default: Nothing is excluded beyond what the statement implies.
affects: what is designed and planned
intent.success_criteria:
type: list
question: How will the customer judge this a success?
default: The stated requirements are met.
estate.cloud_provider:
type: enum
provider_values: true
tier: essential
question: Which Cloud provider is this for?
estate.mode:
type: enum
values: [greenfield, brownfield_expansion, migration]
tier: essential
question: Is this a new estate, an extension of an existing one, or a migration?
estate.regions.primary:
binds: true
type: string
tier: essential
question: Which region should it run in?
estate.regions.secondary:
binds: true
type: string
question: Is there a second region, and which?
default: None, unless availability or recovery targets need one.
affects: resilience design and cost
estate.regions.resiliency_tier:
binds: true
type: enum
values: [single_region, warm_standby, active_active]
tier: important
question: How should it survive the loss of a region?
default: single_region
affects: resilience design and cost
estate.data_residency:
binds: true
type: string
tier: essential
question: Where must data stay?
estate.existing_systems:
type: text
tier: {migration: essential, platform_foundation: important, workload: important}
question: What exists today that this replaces, extends or must connect to?
default: Nothing exists today.
affects: connectivity, migration work and the plan
workload.users.who:
type: enum
values: [employees, customers, partners, public, systems]
tier: {workload: essential, migration: essential}
question: Who uses it?
workload.users.count:
type: integer
tier: {workload: essential, migration: essential}
question: How many users?
workload.users.peak_concurrent:
type: integer
tier: {workload: important, migration: important}
question: How many use it at once at peak?
default: A tenth of the user count.
affects: scaling limits and cost
workload.availability.target:
binds: true
type: string
tier: {workload: essential, migration: essential, platform_foundation: important}
question: What availability is required, as a percentage?
default: "99.9%"
affects: resilience design and cost
workload.availability.hours:
type: enum
values: [business_hours, extended, always]
tier: important
question: During which hours must it be available?
default: always
affects: scaling to zero and support
workload.availability.recovery_time:
binds: true
type: string
tier: important
question: How quickly must it recover from a failure?
default: 4 hours
affects: backup and standby design
workload.availability.recovery_point:
binds: true
type: string
tier: important
question: How much recent data may be lost in a failure?
default: 1 hour
affects: backup frequency
compliance.industry:
type: string
question: "Which industry is the customer in?"
compliance.frameworks:
binds: true
type: list
tier: essential
question: Which regulations or standards apply? An empty list if none.
compliance.data_classification:
binds: true
type: enum
values: [public, internal, confidential, restricted]
tier: essential
question: How sensitive is the data?
compliance.encryption.type:
binds: true
type: enum
values: [provider_managed, customer_managed]
provider_values: true
tier: important
question: Must the customer control the encryption keys?
default: provider_managed
affects: key management design
compliance.encryption.key_rotation_days:
binds: true
type: integer
question: How often must keys rotate, in days?
default: 90
compliance.audit_logging.retention_days:
binds: true
type: integer
tier: important
question: How long must audit logs be kept, in days?
default: 365
affects: storage cost and log design
compliance.audit_logging.immutable_retention_policy:
binds: true
type: boolean
question: Must audit logs be undeletable for that time?
default: false
networking.exposure:
binds: true
type: enum
values: [internal_only, internet_facing]
tier: important
question: Is it reached from the internet or only from inside?
default: internal_only
affects: perimeter design
networking.topology:
binds: true
type: enum
provider_values: true
tier: {platform_foundation: important}
question: Is a network topology already decided?
default: The simplest topology that meets the requirements.
affects: the whole network design
networking.hybrid_connectivity.enabled:
binds: true
type: boolean
tier: {platform_foundation: important, migration: important}
question: Must it connect privately to on-premises or another cloud?
default: false
affects: network design and lead time
networking.hybrid_connectivity.type:
binds: true
type: enum
provider_values: true
question: By what kind of connection?
networking.hybrid_connectivity.bandwidth_gbps:
binds: true
type: number
question: At what bandwidth, in Gbps?
networking.egress_control.model:
binds: true
type: enum
values: [direct, provider_managed, centralized_appliance]
question: How must traffic to the internet be controlled?
default: provider_managed
affects: network design and cost
networking.egress_control.appliance_vendor:
binds: true
type: string
question: Which inspection appliance, if one is mandated?
networking.cidr_allocations:
binds: true
type: text
tier: {platform_foundation: important}
question: Which IP ranges are allocated, and how large per environment?
default: Private ranges that do not overlap, sized for growth.
affects: every network resource
governance.identity_source_of_truth:
binds: true
type: string
tier: important
question: Which identity provider do people sign in with?
default: The Cloud provider's own identities.
affects: access design
governance.pipeline_authentication:
binds: true
type: string
question: How do delivery pipelines authenticate?
default: Short-lived federated credentials, no stored keys.
governance.environment_tiers:
binds: true
type: records
keys: [name]
optional_keys: [archetype]
tier: important
question: Which environments are needed?
default: development, test and production.
affects: the number of environments built and planned
operations.operating_model:
type: string
question: "Who runs the platform day to day?"
operations.support_hours:
type: enum
values: [business_hours, extended, always]
question: During which hours is it supported?
default: business_hours
operations.monitoring:
type: text
question: What monitoring and alerting is expected?
default: The Cloud provider's own monitoring, with alerts on availability and errors.
operations.change_process:
type: text
question: "How are changes approved and released?"
integrations:
type: records
keys: [name]
optional_keys: [direction, criticality]
question: Which other systems must it exchange data with?
default: None.
delivery.target_start_date:
type: date
question: "When should work start?"
delivery.window_weeks:
type: integer
tier: important
question: Is there a deadline, in weeks from the start?
default: No deadline; the plan gives the time the work needs.
affects: the plan and whether the scope fits
delivery.commercial_model:
type: enum
values: [time_and_materials, fixed_price_milestone, managed_service]
question: How is the work contracted?
delivery.iac_tooling:
type: string
question: "Which infrastructure-as-code tool?"
default: terraform
delivery.ci_cd:
type: string
question: "Which delivery pipeline tool?"
delivery.team_size:
type: integer
tier: important
question: How many engineers will build it?
default: 2
affects: the timeline
delivery.working_days_per_week:
type: integer
default: 5
cost.monthly_budget:
type: number
tier: {workload: essential, migration: essential, platform_foundation: important}
question: What is the monthly running budget?
default: No ceiling; cost is optimised within the requirements.
affects: product tiers and resilience choices
cost.currency:
type: string
default: "USD"
constraints.products_required:
binds: true
type: list
question: Which products has the customer mandated?
default: None.
constraints.products_forbidden:
binds: true
type: list
question: Which products are ruled out?
default: None.
constraints.other:
type: list
run.pre_approved:
type: boolean
default: false
run.allow_cloud_read:
type: boolean
default: false
run.overlay_skills:
type: list
default: []
run.terraform_modules:
type: boolean
default: false