Taxonomy without complementarity: a necessary precondition for routing monitor ensembles
AI safety teams use trusted models to flag harmful behavior by more capable agents. A reasoning monitor reads the agent’s chain of thought (CoT), while an action monitor reads its tool calls. A production router could choose the best monitor for each task, improving detection while avoiding the cost of running every monitor. This works only when the monitors catch different failures.
I tested this idea in a pilot study of 130 AgentDojo episodes, a benchmark of prompt-injection attacks against tool-using agents. The reasoning monitor achieved 0.99 AUROC, where 1.0 means perfect separation between benign and attack runs. It outperformed the tool-use monitor on both subtle and overt attacks. Routing between them reduced detection because the tool-use monitor added too little coverage. Even simple attacks designed to conceal suspicious reasoning left the reasoning monitor at the benchmark ceiling. Funding will move the test to harder settings, where reasoning reveals less and tool use carries more evidence.
The minimum scope ($25,000 over three months at half-time) will:
- Test reasoning and action monitors in two harder ControlArena settings with richer action traces and less revealing reasoning.
- Have independent annotators label attack type and monitor correctness for at least 100 episodes.
- Release a package that measures whether monitors catch different failures and whether routing or score blending improves detection.
The results will tell researchers whether to use one dominant monitor, build a router, or develop a new monitoring channel.
The ideal scope ($90,000 over six months at full-time) adds a third setting, at least 300 annotated episodes, more model families, and adaptive attacks trained or selected to hide suspicious reasoning while completing a harmful side task.
I will publish the hypotheses and stopping rules before the main experiments. Both scopes include an open-source package, a public dataset, and a reproducibility report. The ideal scope also includes a paper submission.
The two budgets fund different scopes of the same project. Both use a lead researcher rate of $7,000 per full-time month. Each amount below is the total for that funding level.
Ideal ask: $90,000 over six months
The ideal budget funds six months of full-time research across three settings, plus labeling for at least 300 episodes, additional model-family tests, and adaptive-policy training or selection. It also covers the tool, public dataset, reproducibility report, and paper submission.
Lead researcher, full-time for six months: $42,000
Part-time research engineering and contract support for experiments, tool development, and documentation: $24,000
Compute and API costs for pilots, agent rollouts, monitoring, and adaptive-policy training: $12,000
Human annotation, at least 300 episodes with multiple annotators: $4,000
Tooling, continuous integration, and dataset hosting: $2,000
Workshop or conference submission and travel: $3,000
Contingency for compute overruns or one replacement setting: $3,000
Minimum ask: $25,000 over three months
The minimum budget funds three months of half-time research across two harder settings, trace inspection, and multiple-annotator labeling for at least 100 episodes. It also covers the tool release, public dataset, and reproducibility report. A paper submission, third setting, additional model families, and adaptive-policy work require the ideal budget.
Lead researcher, half-time for three months: $10,500
Contract research engineering for experiments, tool development, and documentation: $6,000
Compute and API costs for pilots, agent rollouts, and monitoring: $5,500
Human annotation, at least 100 episodes with multiple annotators: $2,000
Tooling, hosting, and publication costs: $1,000
Private comment. Only shown to approved funders and grant reviewers.