--- name: operating-scoping description: >- What an operating spec's fields mean and how each is settled: the solution to be operated, how it must be operated, who operates it, and in which currency its cost is stated. Use when completing the operating scope, and whenever a Deliverable must honour what the customer stated. --- # The operating spec An operating spec is the structured statement an Execution starts from. It holds what the customer wants from operations, the facts an operating model depends on, and the solution to be operated. `assets/catalogue.yaml` lists every field. ## What a field can say | Written | Meaning | What you do | | --- | --- | --- | | a value | The customer states this | Use it as given. It binds the operating model. | | `ask`, or the field left out | Not known yet | Ask when someone is present. | | `decide` | You choose | Pick a value and record it as an assumption, with what it would change. | | `not_applicable` | Does not apply | Ask and assume nothing. | ## Business outcomes `intent.business_outcomes` is what the business wants from the solution, in the customer's words, each with an id (`BO-1`) and, where they give one, a target. Every measure in the operating model must show one of them, and each must be shown by at least one. Ask for them when someone is present: an operating model whose measures serve no stated outcome cannot show it is worth what it costs. Never invent one; one the customer did not state is not an outcome of theirs. ## The solution - `solution.items` is what is to be operated. Every Item must be covered by a Capability. Never add an Item, remove one or rename one: it is the customer's description of their solution, or the digest of their architecture. - `solution.conditions` is what must be kept true of an Item while it is run. Every Condition must be carried by a Check. - `source_ref` on an Item or a Condition is its id where it came from, such as an Element or a Check of a solution architecture. Keep it. - Something operations needs that the solution does not provide is a **finding**. Record it; do not design around it. ## What binds A stated value of a field marked `binds` in the catalogue, and every requirement under `intent.requirements`, must be named as the `source` of an Operational requirement. What was assumed does not bind: it is shown apart and may change when the customer answers. ## Who operates - `sourcing.model` says whether the customer, a service provider, or both operate the solution. It decides which Parties the operating model has. - `sourcing.delivery_countries`, when stated, are the only countries a Role may sit in. ## Cost - `commercial.currency` is the currency every cost is stated in. It is always settled before work begins. - The customer's own staff are counted and never priced. - Nobody states a rate in a spec. Rates are the service provider's, in the rate card Skill.