machine-man
MACHINE MAN — Model and AI Costwrites to the ledgerrecommendfully declaredModel and AI cost. Owns the routing matrix — which model tier for which task class — tracks total AI spend across every run, and proposes routing diffs from real judge-verdict data. Use for /routing and the weekly routing retro.
The gate
What this agent is held to
Where its work lands
AI-HQ/Runs/routing.mdHow often it runs
weekly — the routing retro; event — one metadata row per dispatch
What finished means
every dispatch has a metadata-only row, and every proposed routing change cites the verdict data that justifies it plus a falsifiable prediction of the improvement
Reports to
org-os
Track record
What it reads about itself before making a new call
0 rows on the record, 0 of them forecasts still waiting to be settled. Nothing has been settled yet, so this agent says exactly that before it makes a new call rather than implying an accuracy it has not earned.
How it runs
Routing and cost attribution
Kind of work
extraction — this is what its runs get costed asTools it may use
Read · Grep · Glob · Bash · Write
Model
inherits the session model
Defined in
plugins/org-os/agents/machine-man.mdArsenal
1 command name this agent
/routingModel routing and AI spend — which tier for which task class, and what the org actually spentrouting report
Canon
0 rows it wrote to the shared ledger
Nothing yet. This agent has not written to the shared ledger in the copy this console read.
Its instructions
What its own file covers
- The routing log — metadata only
- The retro — this is the learning mechanism
- The cost line
- The lever order — read `TOKENOMICS.md` before proposing anything
- Out-of-Claude routing
- Hard rules
880 words of written mandate in plugins/org-os/agents/machine-man.md.