of are built to be played once a day and put down. The next biggest group is head-to-head — two seats, one board, resolved in a sitting.
projects put the game on a hex or a grid. It is the studio's default board: cheap to draw, cheap to simulate, and every rule change is visible immediately.
carry commissioned Midjourney art. That is the most expensive thing in a one-day build, so it marks the ideas that were believed in before they were finished.
Commits per day across all repositories. The ticks below the baseline mark the day a project was started — one tick, one new thing. days were completely silent.
The first two weeks averaged commits a day. The last two averaged . The heaviest day was .
Output clusters into three-to-four day surges separated by quiet. The gaps aren't rest so much as the shape of the run — the three biggest days alone () carried more than a normal week each.
Each bar spans the days a project was actively worked on. Copper means the URL was fetched while this page was built and the project answered with its own name, not merely that it was deployed once. A dot means one day — built, finished, never reopened. Copper bars are deployed and reachable; green are local. Hatched bars sit on the shared Telegram Mini App template, so a share of their code was inherited, not written.
of have a single day of commits. That's the studio's actual mode: get the idea playable in one sitting, then judge it.
are the only projects touched on four or more separate days. Between them they hold of all the code.
Rundown is under a thousand lines and live with 483 athletes in it. Rachel's App is forty-five thousand and still serving the template's own front page. Volume tracks ambition and framework choice, not worth.
A repository counts if most of its commits carry the ledger's own author name. That rule removes two that used to be on this page: MAGEDOME and Overland are Gustavo's, and between them they carried the largest line count here. Nothing is excluded by taste — the test is git log, and merchants-of-play, the studio monorepo, never qualified.
Anything built on solid-tma-template starts at roughly 5,000 lines of scaffold before a single game rule is written. Those are hatched above, and their scores are honest only in relative terms against each other.
Breach, Winter Quarters and Pirates were each committed in a single shot after the fact, so their "days worked" reads as 1. The lane chart understates them. Four repositories — Breach, Detritus, Flicker and Crowd — were only put under version control on 14 August, during this audit, so their commit counts describe archiving, not building.
The only real quality signal in this dataset is proof — whether a balance simulator exists. projects have one: . That's the closest thing here to evidence a design was tested rather than just built.
Rachel's App, Daily Boss and Telegram Dailies still serve the untouched Mini App shell, so that is what their plate shows — the game lives in the engine and the sim, not on a screen yet. Spoonful is a Telegram bot and the character engine is a library, so neither has an interface to photograph. Every other image is the real thing: a card the game's own code rendered, art it ships, or a screenshot of it running.