Files
tom_analysis_agent/docs/adr/0001-the-target-operating-model-is-an-explicit-graph.md

28 lines
2.6 KiB
Markdown

---
status: proposed
---
# The Target operating model is an explicit graph, and the solution is never changed here
An operating model written as prose cannot be checked: nobody can say whether every part of the solution has someone to run it, or whether anyone is answerable when it fails at night. We decide that the **Target operating model** is one explicit graph, held as data: Parties, Roles, the Responsibilities between Roles and Capabilities, and the Checks each must meet. It is established and approved before anything is written from it, and what is written from it is a view of it.
This follows the solution architecture agent's ADR-0005, applied to a different subject.
## What follows
- **Completeness is a submission rule.** The graph is refused while a Capability has no single accountable Role, or nobody responsible at the hours it is needed, or while something the customer said must be kept true is carried by no Check.
- **Views are written by code.** The responsibility matrix, the organisation chart, and staffing and cost are rendered or computed from the graph. No model draws or counts.
- **Validation is a verdict per Check,** with scenario walk-throughs in place of a dry run: events generated from the graph and traced through it by code.
- **The solution is never changed.** The Items to be operated and the Conditions on them are the customer's description, or the digest of their architecture. Something operations needs that the solution does not provide is a **finding**: it is recorded, a Check that depends on it waits on it, and it goes back to whoever owns the design. Where the spec was digested from a solution architecture, the findings are drafted as a Change request to that agent.
## Considered Options
- **Repair gaps in the solution while designing its operations:** rejected. Two agents would then hold different versions of one design, and the architecture's own Checks would no longer describe what is run.
- **Refuse to proceed while a gap exists:** rejected. Most operating models can be designed around a known, stated gap, and the customer is better served by a model with its findings listed than by none.
- **Hold Capabilities inside the graph:** rejected for now. The capability model is its own Deliverable, so that what must be done is agreed apart from who does it, and a failed Check can reopen one without the other.
## Consequences
- A finding is neither a failed Check nor a gap in the model. Nothing is revised for it, and the Execution completes with it listed.
- More is decided before detail is written. A fault in the graph costs a Revision of it and of validation.