Changelog
Firing log
Potters keep one: what went in, what schedule it ran, what came out. This is the line’s — every stage that landed, every part that entered the register, every firing that came off the rack.
3D and voxel generation modules land beside the art stage
Mesh and multiview tasks run on a dedicated worker with a licence check as the last build layer — the image refuses to build if a restricted dependency is present, and re-checks at boot. Voxel is specified and not yet wired.
Both fire paths answer the pipeline's questions the same way
A game fired from the desktop and a game fired headlessly over MCP now open the same workflow record, so every firing is tracked identically whichever way it was started. The one deliberate asymmetry: design sign-off blocks the headless path outright, because an agent driving the line has nobody in the room.
The canon line is written down once, and only once
Two drafts each described one stage and neither described the whole. There is now a single record of what the line is, which stages are agentic and which are programmatic, and which gates block versus warn.
The fun gate learns to score only what was measured
The feel mean is now taken over the axes an evaluator actually scored rather than over all seven, and an unmeasured time-to-first-fun is carried as null instead of being filled in from the threshold. Every number the gate reports is now a number somebody produced.
Hollow Reign cleared the gate in nine seconds
Fastest time to first fun of any firing so far, and it holds. Feel 7.2 over five of seven axes, ten of ten planned parts placed, twelve of twelve screens built. Playable in a browser today.