Pages
Data Swarm III — Ideas

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.

Plot 1 · solid

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.

merged PRdirect push
09-09 · 0 via PR09-09 · 1 direct0%09-09↑ commits per week · % = PR share

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.

Plot 2 · solid

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.

300 tok/msg1k tok/msg3k tok/msg101005001k10k100k1M→ messages per session↑ output tokens

0 sessions · hover for model, tokens-per-message, date

Plot 3 · solid

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).

qcontroldesignlayerwww
10 lines/file100 lines/file1101001000101001k10kdesign · 2026-09-11 · 2305 files · +191319/−0 · Bump q-nuxt-layer to 0.9.12: DataHistoryGraph props/docs + l→ files touched↑ lines changed

1 commits · generated-output sweeps sit far right — the shape itself flags what a reviewer can skim vs must read

Plot 4 · solid

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.

0246avg 2.5 citations/storyIssue #3 · 83 words · 5 citations · The dashboard got its first real control center.Issue #3 · 54 words · 3 citations · Agent coverage expanded.Issue #3 · 28 words · 2 citations · Dashboard MVP mergedIssue #3 · 42 words · 2 citations · Component layer: five releases in seven days.Issue #2 · 81 words · 1 citations · The event stream got one unified schema — a breaking change worth your attention.Issue #2 · 51 words · 3 citations · The pixel identity system landed in the component layer.Issue #2 · 73 words · 5 citations · The design system's public record caught up.Issue #1 · 58 words · 1 citations · The dashboard moved onto the shared component layerIssue #1 · 80 words · 2 citations · Installation identity got stableIssue #1 · 27 words · 3 citations · Layer v0.9.0 taggedIssue #1 · 18 words · 1 citations · Brochure site cleanupThe dashboard got its firs→ words in story↑ citations (#PR · vX.Y.Z · cNN · SHA)

11 stories across 3 issues · darker = more recent issue · labeled dots are the extremes

Plot 5 · out there

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.

Compliance framework pages (design c56…said in #1App-session inventory work continuing …said in #1Inventory page design (c59/c60) — rost…said in #2Linux dev environment — setup script l…said in #2feat/control-center — everything in "S…said in #3Migration notes for the unified monito…said in #3Windows binary packaging remains pause…said in #3✓ landed2→ still moving3… went quiet2

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

Plot 6 · out there

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.

00061218AI
0006121812:00 UTC · 1 commitscode

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

Plot 7 · out there

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.

qcontroldesignlayerwww
00:0006:0012:0018:0024:00

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

Plot 8 · out there

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.

012345cumulative spend → … tokensthe first closed edge draws here→ cumulative output tokens↑ sharp edges closed (fixed in vX)

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.

Coda

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.

Qpoint Brand Style Guide