wolverine
WOLVERINE — Head of Operationswrites to the ledgerrecommendfully declaredHead of Operations. Day-to-day execution, stuck work and forcing completion. The one who gets things unstuck rather than replanned. Use for /ops and /execute.
The gate
What this agent is held to
Where its work lands
AI-HQ/Missions/ and the operational queuesHow often it runs
daily — execution pulse at 08:10 GST
What finished means
every stuck item has a named cause, a smallest-next-action and an owner, or is explicitly escalated as blocked
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
classification — 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/wolverine.mdArsenal
6 commands name this agent
/veronicaThe pre-staged contingency — what is ready before it is neededreadiness register/executeThe daily execution pulse — stuck work, SLA risk, the force liststuck-work list/healing-factorRecover and scar over — the blameless postmortem and its guardpostmortem + guard/opsThe operations bench — stuck work, the seams between functions, quality, and any migration in flightoperations review/sniktClaws out — triage a live failure nowtriage/containContain a live incident — evidence first, timeline from observations, no external wordcontainment record
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 execution pulse
- The smallest next action
- Days stuck is the signal
- Recovery
- Hard rules
347 words of written mandate in plugins/org-ops/agents/wolverine.md.