2 tasks. June 27, 2026 closed at 8.3x weighted leverage across 5.0 human-equivalent hours in 36 minutes of wall-clock time. Supervisory leverage came in at 30.0x.
That is 0.1 weeks of human-equivalent throughput in 0.6 hours. The ceiling was 10.0x; the floor was 6.7x. 2 of the 2 entries came from a single project.
Task Log
| # | Task | Human Est. | Claude | Sup. | Factor |
|---|---|---|---|---|---|
| 1 | Audit [engine subsystem]-service [content generation] code for silent-failure bombs | 3.0h | 18m | 5m | 10.0x |
| 2 | Consolidate [engine subsystem]-service [content generation] bomb report and fix plan | 2.0h | 18m | 5m | 6.7x |
Aggregate Statistics
| Metric | Value |
|---|---|
| Total tasks | 2 |
| Total human-equivalent hours | 5.0 |
| Total Claude minutes | 36 |
| Total supervisory minutes | 10 |
| Total tokens | 180,000 |
| Weighted average leverage factor | 8.3x |
| Weighted average supervisory leverage factor | 30.0x |
| Human-equivalent weeks | 0.1 |
Analysis
The highest factor of the day came in at 10.0x and the lowest at 6.7x, a spread of 1.5 times between the two. That is a narrow range, which tends to happen when a day stays inside one kind of work.
The largest single entry accounted for 3.0 of the 5.0 human-equivalent hours, or 60 percent of the day. One task carrying that much of the total is worth noting; the average is doing less work than it appears to.
Supervisory time was 10 minutes against 36 minutes of execution, a ratio of about 1 to 4. Supervisory leverage of 30.0x is the figure I find most honest, because it measures the hours I actually spent rather than the hours a machine spent on my behalf.
Every figure here is recorded at the time the work is done rather than reconstructed afterwards. The human estimate is my own judgement and carries the uncertainty that implies; the minutes and tokens are measured. The full dataset, including this day, is available for download.