Two tasks. July 4, 2026 weighted to 6.4x leverage across 74.0 human-equivalent hours in 690 Claude-minutes. Supervisory leverage closed at 185.0x. Two long overnight operations dominated: a multi-model benchmark harness paired with full beta content remediation, and a validation sweep of the retrieval-answering service that root-caused a stale-path defect and swept 292 packages.
1.9 weeks of human-equivalent throughput in 11.5 hours of Claude wall-clock. The 6.7x ceiling came from Overnight run on the platform: a multi-model benchmark harness, a phase-routing config, a general misconceptions generator, and full beta content remediation...; the 5.6x floor sat at Overnight validation sweep of the retrieval-answering service: brought up its 8-service stack; root-caused and fixed a critical stale package-path defect (it....
Task Log
| # | Task | Human Est. | Claude | Sup. | Factor | Sup. Factor |
|---|---|---|---|---|---|---|
| 1 | Overnight run on the platform: a multi-model benchmark harness, a phase-routing config, a general misconceptions generator, and full beta content remediation (44/44 beta candidate-ready, including 3 math course bundles) | 60.0h | 540m | 15m | 6.7x | 240.0x |
| 2 | Overnight validation sweep of the retrieval-answering service: brought up its 8-service stack; root-caused and fixed a critical stale package-path defect (it was reading from a retired path inside the inference engine instead of the canonical output of the content-generation pipeline, so its answer index loaded empty and readiness plateaued); built a catalog-driven profile generator with a self-correcting readiness gate; swept 292 live+beta packages at concurrency 2 (292/292 pass); reloaded and tested 13 beta packages after question-bank generation | 14.0h | 150m | 9m | 5.6x | 93.3x |
Aggregate Statistics
| Metric | Value |
|---|---|
| Total tasks | 2 |
| Total human-equivalent hours | 74.0 |
| Total Claude minutes | 690 |
| Total supervisory minutes | 24 |
| Total tokens | 3,300,000 |
| Weighted average leverage factor | 6.4x |
| Weighted average supervisory leverage factor | 185.0x |
| Human-equivalent weeks | 1.9 |
Analysis
The day's leverage distribution matters more than the headline figure. The 6.7x ceiling came from Overnight run on the platform: a multi-model benchmark harness, a phase-routing config, a general misconceptions generator, and full beta content remediation...; the 5.6x floor was Overnight validation sweep of the retrieval-answering service: brought up its 8-service stack; root-caused and fixed a critical stale package-path defect (it.... Tasks at the top of the distribution share a shape: tightly-scoped specifications, clear success criteria, and minimal integration ambiguity. The AI doesn't need to discover anything new; it executes against an explicit target.
Tasks at the bottom run differently. They're either bounded by review-heavy work where every step gets verified, or they involve ambiguity that demands several rounds of trial and adjustment. The factor is real and informative, not a failure mode.
With only two tasks, both wall-clock-heavy overnight sweeps (540 and 150 model-minutes), the leverage is low by construction; these are long-running validation runs rather than tightly-scoped authoring. The supervisory figure tells the complementary story: two short prompts set 74 human-equivalent hours in motion.
The supervisory leverage figure (185.0x today) tracks something orthogonal to wall-clock leverage. It's the ratio of human-equivalent output to human prompt-writing time. It stays high even on lower-leverage days because supervisory minutes scale with task count, not with the human-hour estimate; a 20-minute task and a 4-hour task can both be specified in two minutes of human prompt-writing.
Across the 2 tasks, the day produced roughly 1.9 weeks of senior-engineer-equivalent throughput in 11.5 hours of model wall-clock. That ratio is the practical answer to the question of how much output a single operator can move per day when the model handles the execution and the operator handles the direction.