Source: c62 visibility-stream — iteration III, executing II's pairs-catalog backlog
Two granularity firsts this round: message-grain data (the busiest day under a microscope) and a deliberately empty chart (the north star). Two small API extensions: commits now carry files + hour; ai-usage serves the microscope. Everything else is the same real data, paired new ways.
The governance ratio
x = week · y = commits, split by how they landed: merged PR vs direct push. This is the thesis metric applied to ourselves — how much of the work passed review. The honest answer: 0% via PR overall, and the split differs sharply by repo.
per-repo PR share: design 0% — the product repo reviews; the design repos push direct. That's a policy choice made visible, which is precisely what a governance surface is for.
Verbosity
x = messages per session (log) · y = output tokens (log) · color = model. The diagonals are tokens-per-message guides. Same effort can be terse or chatty — and whether that differs by model is now a lookable-up fact, not a vibe.
0 sessions · hover for model, tokens-per-message, date
Commit shape
x = files touched (log) · y = lines changed (log) · one dot = one commit. Below the guides: wide-and-shallow (renames, sweeps, generated output). Above: narrow-and-deep (dense logic in few files — the commits that deserve review time).
1 commits · generated-output sweeps sit far right — the shape itself flags what a reviewer can skim vs must read
Claims vs evidence
x = words in a digest story · y = evidence citations it carries · one dot = one story. Our own honesty discipline, measured: longer claims should carry more receipts. A dot drifting right without rising is marketing creep — the chart exists so we'd see it.
11 stories across 3 issues · darker = more recent issue · labeled dots are the extremes
The promise tracker
Every "in flight" item ever published, arced to its fate: landed in a later issue, still moving, or went quiet. Quiet isn't dead — it's a debt the next digest owes. Matching is automatic (word overlap against later shipped stories), so the tracker can't be quietly edited.
fates are status-colored (status palette, reserved for status) · with three issues the n is small — the point is the mechanism: promises become data the moment they're published
Two clocks
Two radial 24-hour dials: when the AI generates (left) vs when code lands (right). The org has two circadian rhythms; whether they beat together or the AI runs ahead into the night is now a picture.
petal length = log volume (tokens left, commits right) · UTC · the AI dial's evening reach past the code dial is the "AI keeps working after the humans stop pushing" gap
The microscope
The busiest day in the window — … — at message grain: x = time of day, one lane per session, one mark per active minute, sized by output. The far end of the granularity dial: 0 marks for a single day, and the day's shape (parallel morning sessions, the evening tail) is legible with zero reading.
0 sessions that day, 2.2M output tokens · every mark is a real minute of generation · this is the grain llm.usage gives you for an entire org
The north star (empty on purpose)
x = cumulative AI tokens spent · y = sharp edges closed. The ultimate pair — expenditure against the honesty ledger actually shrinking. It has no marks because nothing has flipped to fixed yet. Publishing the empty chart is the commitment device: the first closure draws the first mark.
15 edges open · 4 mitigating · 0 fixed — the registry was designed with a closure state nothing has earned yet. An empty chart that everyone wants to see filled is alignment, rendered.
Iteration III's lesson
The strongest charts this round measure our own discipline, not our output: the governance ratio, claims-vs-evidence, the promise tracker, the empty north star. Progress metrics impress; accountability metrics convert — they're the ones a partner can't get from any vendor who hasn't built visibility into their own workflow. The microscope closes the granularity arc: from 3 weekly issues → 152 commits → 91 sessions → 333 minutes of a single day, every level a projection of the same observable stream.