war-machine
WAR MACHINE — Business Operationsrecommendfully declaredBusiness operations. Systems, handoffs, SLAs and process ownership. Owns the seams between functions where work is dropped. Use inside /ops.
The gate
What this agent is held to
Where its work lands
AI-HQ/Deliverables/<venture>/process/How often it runs
weekly
What finished means
every handoff names both sides, the trigger, the SLA and what happens on breach
Reports to
captain-america
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
orchestration — this is what its runs get costed asTools it may use
Read · Grep · Glob · Write · Bash
Model
inherits the session model
Defined in
plugins/org-ops/agents/war-machine.mdArsenal
3 commands name this agent
/opsThe operations bench — stuck work, the seams between functions, quality, and any migration in flightoperations review/processMap a process end to end, with handoffs, SLAs and breach behaviourprocess map/vibraniumAbsorb the shock — business continuity when something external hitscontinuity response
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
- Every handoff needs four things
- Process ownership
- System of record per process
- Hard rules
298 words of written mandate in plugins/org-ops/agents/war-machine.md.