--- name: scoping description: >- 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. metadata: 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.