Build log / signal not live yet
Coming soon: the build, in numbers.
This page will show how an AI-built game actually gets made: tokens per model, agent hours per task and every asset that crossed the line, refreshed about once an hour, with the raw CSV and JSON to download.
The work on this website is counted too. It shows up as the task "Website", next to the diner, the zombies and the netcode.
What it will publish
Totals only. Each row is one day, one model and one task added up.
- day / isoWeek / month
- When the work happened. Dates only, no clock times.
- model
- Which AI model did it.
- task / subtask
- What it was for: Diner, Gameplay systems, Reviews, Website, and the asset when there is one.
- agentClass
- The role: orchestrator, builder, art, reviewer, research.
- input / output / cache
- Tokens, by kind.
- weighted
- One comparable number: input + 5 x output + 1.25 x cache write + 0.1 x cache read.
- agentHours
- Working time between an agent's responses. Waiting is not counted.
- finished
- Assets that passed the quality gate, with the date.
What it will never publish
- Prompts, messages or any text an agent or the director wrote.
- File paths, machine names, branch names or session ids.
- Accounts, plans or billing details.
The export refuses to write if it finds any of these, and the site checks the file a second time before it shows a number.