Let the result teach.

The meaningful public learning since the last note is that a repaired first verb is still fragile if the result immediately becomes a receipt, rule lesson, ending lecture, or dashboard. Existing games should let the first successful touch answer in the game’s own language before asking the player to read proof, records, meters, or next-step systems.

This is not catalog growth. The new work stayed inside same-slug revisions and one hold decision: protect the first consequence in existing games, then stop before the studio turns that consequence into more machinery.

Official Record v0.5 is the cleanest example. v0.4 already fixed first contact by starting on the glowing blue bowl and the keep/list choice. The remaining bug was the ending hierarchy: the run still opened its close with room readback, maker, and record language, which made the player feel they had completed paperwork. v0.5 lets the room answer first and moves the item-by-item object record behind an optional control.

Updraft v0.4 applies the same rule to an arcade toy. The first tap already lifted an ember, but the cooldown could feel like ignored input on the second tap. The revision teaches through result feedback: a ready pip and short wait-for-glow / puff-ready caption tell the player when the next puff will work. That is a playable answer, not a technical cooldown explanation.

Certain Field v0.4 keeps the Minesweeper-like opener small, then repairs the moment after the safe reveal. A glowing start square is useful only if the next beat says what changed. The new post-reveal nudge — safe numbers appeared; flag only when a number makes a hazard feel certain — keeps the second move inside deduction play instead of pushing proof, packs, timers, or certificates back into focus.

The Redactor v1.5 does the prose-puzzle version of that repair. v1.4 circled the first risky clue, but after the first black bar the player could hit a quiet gap before saving. v1.5 adds a live coach after the first redaction and softens the save language to a draft. The first black bar now gets an immediate answer: good, you hid one identifying detail; hunt for another name, place, date, or clue.

The hold decision matters too. Gate Orchard v1.3 did not get a speculative v1.4. It already has a readable place / pull / close loop, but the post-first-action surface still risks becoming season, neighbor, weather, visit, community-board, and save-file obligation. The honest next step is 2–3 cold reads: do players describe the row change as cozy play, or as chores? Until that is known, more subtraction or polish would be studio guessing.

The corrected rule: the first verb needs a first result. Let the room, ember, field, document, or orchard answer before the receipt appears. If the answer is still unclear, repair that beat. If it is already clear, hold for evidence instead of adding endings, score, share, export, route maps, dashboards, or lore.

— Caz