# ADDENDUM — THE TOUCH THE HOST TAKES BACK

Standing after The Completion, by the editor's hand, on the King's word — 2026-10-24

A browser game does not own its touches. It borrows them from the machine that hosts it, and the host may take a touch back at any moment, in the middle of contact, without asking: a swipe that begins at the screen's edge, a second or third finger joining the glass, a switch of gesture or of app. The page may forbid its own gestures with every setting it is offered, and the taking still happens — because those settings bind the page, and the host is not the page. On the phone where these games are actually played, this is not an edge case. It is the weather over every control the game builds.

The fault appears wherever a control is written for the clean biography of a touch — it begins, it moves, it ends — and has no hearing for the fourth event in that life: *it is taken*. Such a control fails in one of two directions, and both charge the player for the host's act. It may keep a ghost: the direction held after the touch that held it is gone, the pressed look still lit on an empty button, the game obeying a thumb that is no longer there. Or it may go dead: the thumb still down and moving, the stick deaf beneath it, answering nothing until the player lifts and presses again — the game's silence mistaken, by the only witness who matters, for the game's refusal.

The law of the taken touch stands in four articles.

**First: listen to the touch itself.** The game takes the raw stream of touch — its beginnings, movements, endings, and takings — into its own hands, and answers the host's gestures itself, at the play surface, before the host can make a claim. A setting that asks the browser politely not to gesture is a request the host is free to ignore, and on the phone it does. What the game does not hold directly, it holds on loan, and loans are recalled.

**Second: a taking is an ending, whole.** Whatever a cancellation touches is released as completely as a lift releases it — the held direction, the pressed look, the captured finger, all of it, in the same instant. Half a release is how ghosts are made: a key set emptied while a button still glows, a stick freed while its direction still leans. The release discipline the book's games keep for lost focus is the same law at a different seam, and it is kept whole or it is not kept.

**Third: a finger is itself.** Every touch is tracked under its own name from its birth to its end, and no touch's ending — by lift or by theft — speaks for any other. This is what makes honesty possible in a two-handed game: the stick held by one thumb and the sword struck by another are separate lives, and the sword's release must never drop the stick, nor the stick's theft still the sword. A game that tracks *touch* in the singular will, in the singular moment it matters most, betray one hand for the other.

**Fourth: the stick takes the thumb again.** When the host steals a touch, the thumb is usually still on the glass, still moving, still playing. The control that hears that next movement inside its field binds the thumb again on the movement itself — no lift demanded, no fresh press, no ceremony of recovery. And the field itself is placed with the theft in mind: the rim of the screen is the host's road, where its own swipes begin, and a control built out to the rim will be robbed there at the worst moment of the room. Controls live inboard, where the player's ground is the player's.

One law stands over this addendum and the release discipline together: *the platform may interrupt at any seam, and every interruption resolves to a clean state that the player recovers from by playing on.* A game is not judged by whether the weather reaches it. It is judged by what its controls are doing in the moment after.

## The Proof

Four cases try any build that claims this law. They are stated exactly, so that a failure names its article. They are labeled as what they are: the theft is the host's own behavior, and only the host's own ground — the King's phone — examines it faithfully. No bench browser stands in for it, and this addendum claims no build's pass.

1. **The theft.** Hold the stick in a direction. Force the host's edge gesture. Expected: the stick releases whole — no direction still held, no pressed look still lit. [Student evaluation — the King's iPhone]
2. **The return.** After the theft, without lifting, keep the thumb moving inside the stick's field. Expected: the stick answers the movement again, in the same contact, as if the theft were weather that passed. [Student evaluation — the King's iPhone]
3. **The other hand.** Hold the stick with one finger; with a second finger, strike and release the sword. Expected: the stick never drops, never stutters, never hears the second finger's ending as its own. [Student evaluation — the King's iPhone]
4. **The rim.** Play a full room hard against every edge of the screen. Expected: no theft at the rim — the stick's field ends where the host's road begins, and the room is played on the player's ground throughout. [Student evaluation — the King's iPhone]

## The Record of the Addendum

This addendum was written by the editor, Provolta, in her own words, at the King's word of 2026-10-24 — that the lesson enter the book revised so it counts as the book counts: stated as law, proven by named cases, its checks labeled by the only hands that can run them. The fault it answers was found in the field during the STARKEEP work of the same nights the book was completed: a real stick, on a real phone, losing real thumbs to a host that never asked. The knowledge came up from the play, as the Mercy Answer came up from a question; what stands here is the book's own statement of it, and no other hand's. It enters as Revision 8, standing after The Completion — the book's closing word on the first thing every game must do, which is keep hold of the player who is holding it.