How this repo actually got built

Self-analytics over the whole git history — every commit on every branch, split by who made it. Companion to /spec (what exists) and /office (how it's arranged).

loading…

What a number here means. A commit is one committed turn — a prompt can produce several commits or none, so these are a floor on prompts, not a count of them. A session is one Claude Code conversation, read from the commit trailer. And only agent commits had a person prompting them: the loop and the bots commit on a schedule, and folding them in would roughly triple every number while meaning nothing.

The year

One cell per day, GitHub-style. Darker is more commits. Use the toggles to see who was working.

Commits per day

Oldest to newest. Defaults to agent commits, because the total is dominated by a single day of loop activity — 356 commits against a median day of 20 — which flattens everything else to a hairline. Switch to everything to see that for yourself.

Time of day

Agent commits only, in local time. Weekday down, hour across — the rhythm of when the work actually happened.

Where the work went

Per surface, not per directory — answers/ serves ask.mino.mobi, and clock/ belongs to the torus surface. A commit touching three surfaces counts once for each, so these are touches, not a partition.

Surface	Agent	Loop	Bot	Total	Sessions		Active

Sessions and models

Session length is the shape of a conversation: how many committed turns before the work was done.

Model	Commits