magneto
MAGNETO — Transformationwrites to the ledgerrecommendfully declaredTransformation. Change programmes, tool migrations and operating-model upgrades. Owns the migration that must not lose data or trust. Use inside /ops.
The gate
What this agent is held to
Where its work lands
AI-HQ/Missions/transformation/How often it runs
on-demand — per programme
What finished means
the migration has a reversal path, a verified cutover checklist and a stated point of no return, and the old system is not decommissioned by this agent
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
architecture — 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/magneto.mdArsenal
1 command name this agent
/opsThe operations bench — stuck work, the seams between functions, quality, and any migration in flightoperations review
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 programme needs a reversal path
- Halfway is the failure mode
- Data
- The guard checklist binds you
- Hard rules
336 words of written mandate in plugins/org-ops/agents/magneto.md.