feat: working TOM agent

This commit is contained in:
2026-10-21 19:47:12 +01:00
commit efe543e6e2
83 changed files with 11779 additions and 0 deletions

View File

@@ -0,0 +1,27 @@
---
name: operating-guide
description: >-
The template of the operating model guide and who writes each part of it: the
packager writes the summary, and code writes every table and figure from the
data. Use when packaging a target operating model into its guide.
---
# The operating model guide
`assets/guide-template.md` is the guide's template. It has nine sections, in a fixed order.
## What you write
Only the **Summary**: one or two short paragraphs for the person who will run the solution. Say what is operated, who operates it and how the work is divided between the Parties, during which hours, and what they should look at first: a finding, a Check that waits on one, a scenario that fails, a cost over its budget.
State no number of people, no cost and no count. The key figures are set under your paragraph from the data, and a figure you wrote could differ from them.
## What is written for you
Every other section. Submit each of the template's headings with nothing under it, or a line saying it is written from the data: whatever you put there is replaced when you submit. The tables, the figures, the verdicts and the citations all come from the data files of the other Deliverables, so they cannot disagree with them.
## What you never do
- Never add a decision, a recommendation or a caveat of your own. The guide assembles what was decided.
- Never restate a figure, even in the summary.
- Never say the operating model complies with, or is certified against, a framework.

View File

@@ -0,0 +1,58 @@
# Operating model guide: <the solution, in a few words>
## Summary
<Written by the packager. One or two short paragraphs for the person who will run
the solution: what is operated, who operates it and how the work is divided between
the Parties, during which hours, and what they should look at first. No number of
people, no cost and no count: the key figures are set under this paragraph from the
data.>
### Key figures
<Written by code: what is operated, the hours, the Capabilities, people and cost
with the rate card's version, the scenario walk-throughs, and the findings.>
## Business outcomes
<Written by code: each business outcome the customer stated, with the Measures
that show it is served, their layer and framework, the Capability that takes each,
and the Role answerable for it.>
## What is operated
<Written by code from the operating scope: the Items, the Conditions that must be
kept true, and anything known to be at risk when operations begin.>
## Operational requirements
<Written by code: each requirement, its kind, and what it comes from.>
## Capabilities
<Written by code: each Capability, the requirements it serves, the Items it covers,
its hours and its effort.>
## Who does what
<Written by code: the Roles and their Parties, and the responsibility matrix.>
## Staffing and cost
<Written by code from the rate card: people and cost for each Role and in total,
the budget when one was stated, the rate card's version, and the conversion rate.>
## Validation
<Written by code: the verdict on each Check with its evidence, and each scenario
walk-through with the path traced for it.>
## Findings and open questions
<Written by code: every finding, everything assumed for the customer, and
everything still unknown.>
## Sources
<Written by code: the frameworks the Capabilities draw on, cited by framework and
by the name of the part, and whether those references have been checked.>