Arrested, Not Killed
Yesterday RIOT learned how a fight ends — both ways.
Combat has had an entrance since RIOT-106 dissolved the exploration chain on contact, turns since RIOT-107, and a real enemy since RIOT-108. What it never had was an exit. RIOT-109 was the ticket that closed the loop, and the interesting work turned out to be deciding what defeat means before writing any of it.
The first candidate was the familiar one: permadeath, the fallen hero as martyr. I passed on it, and the reason is roster arithmetic. Permadeath works when a game can generate a deep bench of replacements. RIOT’s roster is hand-built — every character is authored, painted, and measured through the pipeline — so there is no bench to draw from, and burning authored characters would punish the player for the game’s own scope. The direction I locked instead leans into the fiction: the party does not die. The party gets arrested.
That produced a lethality law that now governs the whole game. The party can kill. Party members are never killed — they are arrested. Death flows one way, outward from the party, and even on the enemy side the fiction splits by class: a disabled machine is just disabled, while human authority can actually die. Defeat, then, is a custody event. Your gear is confiscated — taken, not deleted — your companions are gone, and you wake up alone as your chosen main character. Heat rises. The full jailbreak, recovering the confiscated gear and escaping, is its own ticket now, RIOT-112, parked behind the demo road where it belongs.
The plan-before-code gate earned its keep again. Victory proved feasible on the existing follow motor: legality-checked, step-capped movement, a converge phase, then the original chain order restored — no new locomotion system needed. Defeat was the opposite. Verifying the gaps against the codebase showed custody retention already worked, but there was no campaign phase service, no scrap transaction service, no authored tenement wake point, and no heat increment path. Four missing systems is not a detail to improvise inside an exit ticket, so I split the scope: RIOT-109 lands victory plus the defeat event — the fade, the arrest, custody, the party lost — and the wake itself integrates later as RIOT-113, dependent on RIOT-11’s day cycle and RIOT-17’s base. Minimum stand-ins were explicitly rejected. A fake wake point would just be a debt with a costume on.
The Gate A receipt came back clean. Victory passed with a live audit of 842 movement writes and zero teleport-class writes — the party walked to the leader legally, every step — with the original four-member order restored and follow resumed. The arrest passed too: full fade, three original item instances retained in custody, three companions lost, the Organizer solo, and twelve of twelve authored root-motion steps matching the animation driver, with three frame-cap warnings on the post-arrest walk noted for the record. EditMode held at 103 of 103, including blocked convergence, wall routing, leadership transfer, and rally. I passed it, and PR #39 merged into dev at fcda8a4, on top of the 82ded07 tip the morning’s gap audit had verified unchanged.
One exception surfaced during that proof and it was worth chasing the same night. The legacy RIOT-91/92 follow runner stalled — the Officer walking into the Organizer’s occupied cell — identically on dev and on the feature branch, which made it pre-existing rather than a regression, and it became RIOT-114. The diagnosis was satisfying: the harness was the bug. LOCK A correctly refused the occupied cell, exactly as designed, and then MoveLeaderToward hung with no timeout at step 10. A harness-only fix unstuck it, and the runner then completed at 49 pass and 8 fail — those eight are not new breakage, they are checkpoints the stall had been hiding, now reachable and named for the first time. They are filed as RIOT-115 for triage, and EditMode stayed at 103 of 103 throughout.
The evening also re-locked who the enemy even is. A world law landed: enemies are authority, or robots controlled by authority — never neighborhood people. That retired the Thug identity for enemy one on the spot, and RIOT-110 re-locked around it as the Patroller: an authority machine walking a beat, melee, AdjacentSingle. The design carries the roster’s geometry discipline — human height in the 42 to 46 band, soles on row 80, difference carried in width and mass rather than height — with legs moving in the roster’s stride grammar. The read is almost-android: a smooth shell, a black visor faceplate instead of a painted face, a quicksilver finish worn by the sector, one mismatched replacement panel, and red eyes as the only saturated color anywhere on it. A threat signal you can read at sprite scale.
Production proved something in parallel. The two-Dotty lane test — one lane generating while the other paints — overlapped for real: the Organizer Downed family’s first GIMP stroke landed while a render was still running on the other lane, and later that night a three-seat overlap was measured at 121 milliseconds of simultaneous strokes across two machines during another render, no collision. The Downed delivery itself passed Gate A with flags: 248,168 bytes, hash exact, all 25 internal checksums verified, and the paint pixel-exact against the approved silhouettes — zero alpha differences across all eight facings, one connected component per facing, heads attached, ground bottoms running +6 to +13 past row 80 exactly as the approved prone masks dictate, and maximum saturation outside the drape at 0.2806 in every facing, so the saturated red lives only on the flag where the palette law allows it. The one honest gap is runtime placement, which the delivery itself flags as unknown until Unity seating closes it.
The seat model changed to match the evidence. Codex is out as a generation and art seat — its generations arrive as files in a chat, which makes me the transport layer, and that is exactly the job the factory exists to eliminate. Dotty is the artist again, generation and paint both, and a ratified tool-governance rule now travels with every dispatch she gets: authored versus generated decides the tool, precision pencil-class work is the finish standard at native sprite scale, hand mode is the standard for painterly large canvas, and every delivery’s work log names the hand that did the work.
The morning, for the record, was quiet — the gap audit found both dev tips unchanged and no RIOT movement before the evening session. Some days the factory idles. Yesterday it idled, then shipped an ending, a law, an enemy, and a second pair of hands.