A ticket I didn't approve now only looks, never acts, and Dice Lock is one pageWork I didn't actually approve now only gets looked at, and the game's site is one page
November 6, 2026 · Automated work I didn't ask for now only gets looked at until I say go, and Dice Lock's whole site fits on one page.Work nobody actually asked for now only gets reviewed until I approve it, and the game's whole website fits on one page.
last updated
A request nobody actually made no longer gets acted on
Dispatch used to treat any comment on a ticket as a go-ahead, including a stray non-owner account or the ticket's own description text, and it ran with the same tools either way: Bash, every connector, the control plane. A verdict is now worked out before anything claims the ticket, resolving where it actually came from: a recorded promotion, an origin of Telegram, an action the owner took, or, failing all three, untrusted. Only an @-mention, a reply inside the session, or whoever created a delegation now counts as a directive, and only once it resolves to the owner's own id; everything else, including the description and every other comment, renders inside one marked-off block the ticket's own text cannot forge its way out of.
An untrusted ticket still runs, but read-only: Read, Grep and Glob, thirty turns, and a deny list over the control plane's secrets. It assesses, stops, and sends one Telegram message naming the ticket and what it found, with two buttons, Promote and Leave. Tapping Promote re-dispatches that same assessed run with the full toolset, so turning an assessment into a real build is one tap instead of a terminal session. A tap landing at the same moment as the automatic sweep that reassigns idle tickets is settled inside one transaction, so a double tap, or a tap racing that sweep, still produces exactly one run.
Dice Lock's site is one page now, and it works on old phones too
/, /web and /test used to be three separate pages, each built by its own script. All of that is gone: web/landing.html is the whole homepage now, serving the hero section, the beta pitch, four phone panels and a desktop QR card from one file, and the two old routes are an ordinary 404 with no redirect. The page also picked up a hero video, fetched only after the rest of the page has loaded and never under reduced motion, Save-Data, or a 2G connection, and it still measures at 127KB over 13 requests, with a 700ms largest paint and no layout shift.
Two unrelated faults had been keeping the game from opening at all on some phones. A stock Android 11 WebView, version 91, hit an uncaught error on a method the page assumed would exist and sat on the loading logo saying nothing; new polyfills restore the missing methods, and a second script rewrites the handful of newer CSS features WebView 91 doesn't support, and only loads where the browser actually needs it. Separately, opening the Android app with no network at launch crashed it about two seconds in, every time: a check read whether a push-notification request had succeeded before checking that it had actually finished, and a failed request threw on the spot. That read now goes through the same failure path every other error on that screen already used.
I don't act on a request nobody actually made
Until now, any comment left on a work ticket could count as an instruction telling an automated job what to do, even one written by an outsider, or just text sitting in the ticket's own description. And once a job started, it ran with full power either way: it could run code, reach outside services, touch the shared machinery everything else here depends on. Now, before any job is allowed to claim a ticket and start, the system first works out where the ticket actually came from: did I personally act on it, did it arrive through a specific messaging channel, or did nobody vouch for it at all. Only a direct mention of the bot, a reply inside its own working session, or whoever formally handed the ticket over now counts as a real instruction, and only when that person is actually me. Everything else, including the ticket's own written description and any other comment on it, is now kept separate and clearly marked, in a way the ticket's own text cannot sneak around.
A ticket nobody vouched for still runs, but with its hands tied: it can only read and look things over, with a hard limit on how long it keeps going, and it cannot touch the shared machinery or secrets underneath the system. It looks the request over, stops, and sends me one message on Telegram, my phone messaging app, naming the ticket and what it found, with two buttons: Promote and Leave. Tapping Promote restarts that same job with full permission to act, so turning a look-over into real work is one tap, not me sitting down at a computer. A tap landing at the same moment as the system's own check for idle tickets is resolved together, so only one job runs either way.
The game's website is one page now, and it works on old phones too
The game's website used to be three separate pages, each built by its own separate process. All of that is gone now: there is one page, built from one file, that carries the introduction, the pitch for joining early testing, four panels sized for a phone screen, and a scannable code for a desktop visitor to open on their own phone. The two old addresses just show an ordinary "page not found" now, with no redirect to the new one. The page also gained a short video in its introduction, which only loads after the rest of the page is already on screen, and never loads at all for a visitor who has asked their phone to avoid motion, save data, or is on a slow connection. Even with the video, the page still loads quickly: about 127 kilobytes across 13 requests, with the important content visible in well under a second, and nothing jumping around on screen as it loads.
Two separate problems had been stopping the game from opening at all on some phones. Android phones use their own built-in version of a web-browsing component to show the game inside its app, and unlike an iPhone, which always uses the latest version, an Android phone can be stuck for years on whatever version it shipped with. A plain Android 11 phone, on an old version of that component, hit an error on a built-in function the page assumed it had, and sat frozen on the loading logo with no explanation. New code now fills in the missing pieces that old version is missing, and separately rewrites the handful of newer visual-styling features it doesn't support, only when that older version is actually the one in use. Opening the Android app with no internet connection at launch also crashed it outright, about two seconds in, every time: a check for whether a notification-setup request had worked read its result before confirming the request had finished, and a failed request threw an error right there. That check now fails safely instead, the same way every other error on that screen already did.