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

36
skills/rate-card/SKILL.md Normal file
View File

@@ -0,0 +1,36 @@
---
name: rate-card
description: >-
The service provider's rate card: day rates by country and level, the
productive days in each country, conversion rates, and the smallest team that
can cover each pattern of hours. Use when placing Roles in countries and
choosing their levels, in the Target operating model and organisation design.
metadata:
scope: the Target operating model and organisation design
owner: the service provider
---
# Rate card
`assets/rates.yaml` is the service provider's rate card. The provider sets every figure in it. Nothing else does: not a caller, not an operating spec, and not you.
While its `version` starts with `draft`, the figures are placeholders and say so wherever a total is shown.
## What you do with it
- Give every Role a `country` and a `level` that the card has. A Role in a country or at a level the card lacks is refused when you submit.
- Place Roles only in the countries the operating spec lists under `sourcing.delivery_countries`, when it lists any.
- Choose the level from what the Role's Capabilities ask of it, using the description of each level in the card. Do not choose a level to reach a cost.
- Choose the country for a reason you state: the hours the Role must cover, the language it must work in, where the data may be handled, where the customer's own teams sit.
## What you never do
- Never write a number of people, a rate or a cost. People per Role, cost per Role and every total are computed from the card when you submit, and written into your Deliverable for you.
- Never use a rate from anywhere else. A rate a customer states is a question for the provider, recorded as a customer question, and changes nothing.
- Never convert a currency. The operating spec states the currency of the result, and the conversion is made from the card's fixed rates when you submit.
## What the card decides
- A Role that covers hours wider than a working day is never sized below the card's `minimum_roster` for that cover, however little effort its Capabilities need. Covering every hour from one country needs a rota; covering it from several countries in turn needs a Role in each, each on `business` or `extended` hours.
- Work outside business hours carries the card's `uplift`.
- The customer's own staff are never priced: a Role in a customer Party is shown as people, with no cost. Of the other Parties, only the kinds the card lists under `prices` are costed.

View File

@@ -0,0 +1,56 @@
# The service provider's rate card. Its prices are set by the provider who runs
# this agent, and by nobody else: not a caller, not an operating spec, not a model.
#
# PLACEHOLDERS: while `version` below starts with `draft`, every figure here was
# drafted to build and test the arithmetic and is not a price anyone has set.
# Set each one, then change `version`.
#
# `day_rate` is what one day of one person at that level is charged at, in
# `currency`. `productive_days` is the days in a year a person works on the
# service, after leave, public holidays and training. `hours_per_day` is the
# working day. Countries are ISO 3166-1 alpha-2 codes.
schema_version: 1
name: rate-card
version: draft-2026-10-13
currency: USD # what the rates below are written in
# The operating spec states the currency of the result (`commercial.currency`).
# These are the fixed rates used to convert into it: units of that currency for
# one unit of `currency` above. Set by the provider with the prices; no rate is
# looked up. A currency not listed cannot be asked for.
conversion:
as_of: 2026-10-13
rates: {USD: 1.00, GBP: 0.79, EUR: 0.92, CAD: 1.37, AUD: 1.52, JPY: 150, INR: 84}
# Which Parties this card prices, by kind. Roles of any other Party are counted
# as people and carry no cost. The customer's own staff are never priced, and
# `customer` may not be listed here.
prices: [provider]
levels:
engineer: Runs established procedures and resolves known faults.
senior: Diagnoses unfamiliar faults, automates, and leads a shift.
lead: Accountable for a Capability; designs the way of working.
# The fewest people who can staff a Role for a pattern of hours, and what is
# added to their rate for it. A Role is never sized below `minimum_roster`,
# however little effort its Capabilities need.
cover:
business: {minimum_roster: 1, uplift: 1.00} # one working day, five days a week
extended: {minimum_roster: 3, uplift: 1.10} # about sixteen hours, five days a week
24x7: {minimum_roster: 5, uplift: 1.25} # every hour of every day, from one country
countries:
US: {name: United States, productive_days: 225, hours_per_day: 8, day_rate: {engineer: 720, senior: 960, lead: 1250}}
CA: {name: Canada, productive_days: 222, hours_per_day: 7.5, day_rate: {engineer: 600, senior: 800, lead: 1020}}
GB: {name: United Kingdom, productive_days: 220, hours_per_day: 7.5, day_rate: {engineer: 600, senior: 800, lead: 1050}}
DE: {name: Germany, productive_days: 215, hours_per_day: 8, day_rate: {engineer: 640, senior: 850, lead: 1100}}
ES: {name: Spain, productive_days: 218, hours_per_day: 8, day_rate: {engineer: 420, senior: 560, lead: 740}}
PL: {name: Poland, productive_days: 220, hours_per_day: 8, day_rate: {engineer: 340, senior: 460, lead: 620}}
HU: {name: Hungary, productive_days: 220, hours_per_day: 8, day_rate: {engineer: 320, senior: 430, lead: 580}}
IN: {name: India, productive_days: 230, hours_per_day: 8, day_rate: {engineer: 180, senior: 260, lead: 380}}
PH: {name: Philippines, productive_days: 230, hours_per_day: 8, day_rate: {engineer: 190, senior: 270, lead: 390}}
BR: {name: Brazil, productive_days: 222, hours_per_day: 8, day_rate: {engineer: 260, senior: 360, lead: 500}}
MX: {name: Mexico, productive_days: 228, hours_per_day: 8, day_rate: {engineer: 280, senior: 380, lead: 520}}
JP: {name: Japan, productive_days: 225, hours_per_day: 8, day_rate: {engineer: 620, senior: 820, lead: 1080}}
AU: {name: Australia, productive_days: 222, hours_per_day: 7.6, day_rate: {engineer: 640, senior: 850, lead: 1100}}