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>
2.4 KiB
2.4 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. |
|
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.exclusionsis out of scope for every Deliverable. - The customer's own requirements carry their ids. Each entry in
intent.requirementsmust be met. When your work serves one, name its id. - An assumption is not the customer's decision. A field under
assumedwas chosen for them, with the reason given. Work from it, and say so where your Deliverable depends on it: it may change when they answer. - Do not fill a gap silently. A field under
to_askis still unknown. When your Deliverable needs it, assume a default and say that you did.
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.