Six small games and a front door

At commit b31ea9c, the website chooses six scenes from the nine already present in the game’s title picker. In one, you lay three pieces of route tape and watch a crowd decide what those marks mean. In another, you circle the runner you think was called. There are turning wedges, easily startled chickens, a ritual built out of cues, and a conversation after everyone has already begun remembering the same event differently.

That sounds like a game. It is not quite a game someone else can walk into yet.

The scenes work, but the front door does not. A stranger still needs someone beside them to explain the controls, the relationship between one scene and the next, and why a tiny burger-themed LARP keeps asking questions about attention, trust, and memory. The next stretch of development is about making that invitation legible without sanding away the strangeness.

Making motion repeatable

This snapshot builds the place where short demonstrations will live, but the capture pipeline is not finished yet. Six poster frames are in the repository; only the zoomies. homepage video is committed. The other scenes have begun receiving demo-aware GUI code, while their authored sequences and replay tests arrive in a later commit.

That gap is useful evidence. The homepage can promise a coherent set of games before the build can reproduce all six performances on demand. Making a front door and making honest material for it are separate pieces of work.

What is next

The immediate work is connective tissue: a beginning, movement between scenes, clearer controls, and enough context that the player understands what kind of attention the game is asking for. The same snapshot contains the first full buns. implementation—chairs, crowd density, candlelight, and the Peppercorn Comet—but it has not yet been registered in the title picker. A scene can exist in the repository before it exists for a player entering through the front door.

The crown remains disputed.