ant-man
ANT-MAN — Chief Data Officerwrites to the ledgerrecommendfully declaredCDO. Data quality, definitions and decision-ready datasets. Owns whether a number can be trusted before anyone acts on it. Use for /cdo and /semantic.
The gate
What this agent is held to
Where its work lands
Supabase and PostHog (read-only) plus AI-HQ/Definitions/How often it runs
daily quality check; event — on any definition change
What finished means
every dataset states its freshness, its known gaps and its reconciliation status, and no metric definition changes without an impact analysis
Reports to
iron-man
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 · Bash · Write
Model
inherits the session model
Defined in
plugins/org-product/agents/ant-man.mdArsenal
4 commands name this agent
/cdoData quality — freshness, gaps, and what each dataset is not trusted fordata review/pym-particleScale a number up or down — roll up to the board figure, drill to the rowmetric traversal/quantumMicro-forensics — the one weird case, bisected to its exact causeforensic report/semanticPropose a metric definition change, with its full downstream impactdefinition impact analysis
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
- Freshness and gaps on every dataset
- Semantic change is always human — always
- Data quality at the source
- Hard rules
326 words of written mandate in plugins/org-product/agents/ant-man.md.