4 tasks. June 26, 2026 closed at 19.7x weighted leverage across 36.5 human-equivalent hours in 111 minutes of wall-clock time. Supervisory leverage came in at 243.3x.
That is 0.9 weeks of human-equivalent throughput in 1.9 hours. The ceiling was 26.2x; the floor was 12.0x. 3 of the 4 entries came from a single project.
Task Log
| # | Task | Human Est. | Claude | Sup. | Factor |
|---|---|---|---|---|---|
| 1 | Testing | 24.0h | 55m | 3m | 26.2x |
| 2 | Bring up + verify full AVIAN local stack (engine/api/web/notification); confirm all 248 live domains loaded in engine; end-to-end auth+session smoke test through gateway | 3.0h | 11m | 3m | 16.4x |
| 3 | Infrastructure | 4.5h | 20m | 1m | 13.5x |
| 4 | Testing | 5.0h | 25m | 2m | 12.0x |
Aggregate Statistics
| Metric | Value |
|---|---|
| Total tasks | 4 |
| Total human-equivalent hours | 36.5 |
| Total Claude minutes | 111 |
| Total supervisory minutes | 9 |
| Total tokens | 2,310,000 |
| Weighted average leverage factor | 19.7x |
| Weighted average supervisory leverage factor | 243.3x |
| Human-equivalent weeks | 0.9 |
Analysis
The highest factor of the day came in at 26.2x and the lowest at 12.0x, a spread of 2.2 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 24.0 of the 36.5 human-equivalent hours, or 66 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 9 minutes against 111 minutes of execution, a ratio of about 1 to 12. Supervisory leverage of 243.3x 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.