§0 The Operator's Log

How these are counted

Every number in the telemetry strip follows the same rule: counted, not estimated. Here's what each one means and where it comes from.

← The Operator's Log

Leverage: Fleet hours divided by operator hours. The number I'm trying to move. It isn't a productivity claim, just a ratio of two counted figures you can check below.
Fleet hours: Wall-clock time agents spent working, summed from the timestamps on their own turns across every tool the fleet runs on: Claude Code, Codex, and Hive's own session records. Idle time doesn't count. Parallel agents count separately: five agents working one hour is five fleet hours.
Operator hours: My time steering the fleet that week, counted the same way as the fleet's hours but from the timestamps on my own prompts, across Claude Code and Codex. The difference: fleet hours sum across agents working in parallel, mine can't. There's one of me, so two sessions I ran in the same hour are one hour, not two. Counted to wall-clock, not added up.
Shipped: Work merged to the default branch that week, counted across every venture: one pull request, one count. Merged means it passed the gate and went live, not that someone opened it. Drafts don't count. Open branches don't count. Releases are the artifacts this work rolls up into, and they're named in the entry itself.
Fuel: What the fleet cost to run that week in US dollars: model tokens plus tool subscriptions, straight off the bills. My own time isn't in this number. It's right there in operator hours.

One exception: the foundation entry predates this discipline. Its shipped count comes from real records, and its fleet hours were recounted by the engine after the fact; its operator hours and fuel are estimates, and the strip says so. Everything after it is counted as it happens.