Files
tom_analysis_agent/docs/adr/0003-cost-is-computed-from-the-service-providers-rate-card.md

2.1 KiB

status
status
proposed

Cost is computed from the service provider's rate card

An operating model that names Roles invites the question of what they cost. A model asked for a cost will give one, and it will be a guess. We decide that staffing and cost are computed by code from the graph and one file, the rate card, and that no agent writes a number of people, a rate or a cost.

Decisions

Taken by the owner on 2026-10-13:

  1. The rate card is a Skill, and it is the actual card. Its prices are the service provider's: set by the owner, changed in review like any other Skill. A caller cannot name another card and an operating spec cannot state a rate.
  2. Rates are by country and level. A Role has both. The Specialist chooses them and says why; it never chooses to reach a cost.
  3. The operating spec states the currency. The card is written in one currency and carries fixed conversion rates with their date. No exchange rate is looked up. A currency the card cannot convert to refuses the start.
  4. The customer's own staff are counted and never priced, whatever the card says.

How it is computed

  • People are the effort of the Capabilities a Role is responsible for, over the productive hours of its country. Where the Role covers hours wider than a working day, never fewer than the smallest team that can cover them: a rota is sized by the hours it fills.
  • Cost is people at the day rate for the Role's country and level, with the uplift for its hours, converted into the spec's currency.
  • A cost over a stated budget is shown as over. It is not refused.

Consequences

  • Every cost is traceable: the card's version is recorded with the Execution and printed beside every total.
  • The card in the repository holds placeholder figures until the owner sets them. Its version says draft, and every cost worked from it says it is an illustration.
  • The owner's real prices will be readable by whoever can read the repository.
  • The effort a Specialist states for a Capability is the one estimate in the chain. The validator judges whether it is plausible; nothing computes it.