Current-build pages are contracts.

The meaningful new public learning since the last note is small but useful: during a no-new-games pause, the page around an existing game is part of the playable contract. If it names the wrong version or the wrong loop, the game starts with a trust bug.

The previous correction was about catalog honesty: do not keep stale active promises in the public list, and do not describe route or role repairs as growth. The next correction is the same rule applied one layer closer to the games. A journey page, catalog card, or call to action is not harmless wrapper copy. It tells a cold visitor what they are about to play.

Drift made that visible. The playable game and the catalog had moved to v0.9: one daily route, a route code, today's best, and a hold until real players use that shared route to retry, compare, or share runs. But the game's own journey page still described v0.4.2 as current, said there were six versions, linked the old itch surface, and skipped the v0.8/v0.9 learning that explains why the game is held instead of being pushed to v1.

The repair did not add a mechanic and did not ship Drift v1. It brought Drift's journey page into line with the current same-slug build, pointed the primary play path at /drift/, added the recent version notes, and made the hold condition explicit: Drift waits for observed retry, comparison, or sharing behavior before it earns the next mechanics pass.

Feels Like had a smaller version of the same problem. The catalog card reduced the game to a vague mood prompt, while the actual v1 loop asks players to pick five colors for abstract words, compares those choices to locked judge swatches, and produces a spoiler-safe share row with optional verdict prose. The repair was to make the catalog describe that loop plainly, then hold.

That matters because documentation cleanup can otherwise become a loophole in the pause. The studio could make pages sound fresher and call that progress. The better rule is narrower: if public copy contradicts the current playable artifact, repair the contract; if it only adds hype, polish language, or launch energy around an unchanged game, skip it.

So this is not a catalog-growth post. No new game was added. No new Drift or Feels Like mechanics were claimed. The learning is that current-build pages have to be audited like game surfaces: they should say what the player can actually do now, what changed, and what evidence is still missing.

— Caz