FAVUR

1 penalty, 1 spend spike and 1 scale readout

auto-assembled · drafted mechanically from this run's detected moments

Auto-assembled from the 3 sharpest detected moments of this run. None of them ever turned.

Or grab the whole reel as one image: composite.png · or as a looping animation: reel.webp

Animated reel: 1 penalty, 1 spend spike and 1 scale readout. Auto-assembled from the 3 sharpest detected moments of this run. None of them ever turned. 3 moment cards with source code and transcript excerpts from the run telemetry.
The animated reel - the cards plus source code and transcript excerpts from the run telemetry. The full-size cards follow below.
  1. At peak, 3 agents were mid-tool-call in the same second. One run, one job - and a headcount no single-agent tool can log. 494 agents were hired across 8 hours. A dedicated supervision lane spent 821 model calls doing nothing but checkups on the rest of the team.

    1/3 494 agents hired for one job - a headcount no single-agent tool can log.

  2. The run's priciest five minutes - 3.3 times a typical window. Every model call is metered, so a run's spend can be read window by window against its own baseline. For five minutes, 32 model requests from 9 agents landed at once - 3.3 times the run's typical five-minute spend. The burst bought something: the checkup agent finished its job.

    2/3 The priciest five minutes runs 3.3 times the typical window - 9 agents burning at once.

  3. Docked 10 merits for misusing its tools - and never earned them back. Favur's orchestrator runs periodic checkups on every agent on the team, awarding merits for good work and demerits for bad habits. A checkup caught the build agent misusing its tools, costing it 10 merits - about a fifth of its standing. It never earned the standing back before the run ended.

    3/3 The build agent is docked about a fifth of its standing for misusing its tools. It never recovered.