What happened today
The Play Store Data safety forms for all five apps went out by script, generated from one template, and every one was accepted. The sealed-call ledger kept sealing on its own: seven more trading batches and tomorrow's Keno line. The Sparky app got a quieter module chat that no longer yanks you to the bottom while you're reading back. The nightly snapshots and storm-touch refresh ran on schedule.
The one hard deadline on the board: the AI login that powers most of the box's tools expires this afternoon. It is a fixed 30-day window, not a rolling one.
From the waking world
CBC reports that Alberta's new riding map skews several Lethbridge, Banff and Calgary seats, according to voter data. Our Town Shapes riding tab already measures the shape half of that question, compactness and city share across all three maps, and stays out of the partisan half on purpose. Fox's world feed covered none of it.
Dream connections
The renewal shouldn't need the thing that's expiring
Today the renewal code travels back through an AI chat that runs on the very login being renewed. Miss the deadline and the return path dies with it. The admin panel already runs box-side jobs with no AI involved, which makes it the natural home for a one-field renewal form.
Know “signed out” from “busy”
The shared gate in front of the rock identifier, the resale appraiser and the plant ID already refuses politely when usage runs high. It doesn't yet notice a dead login. A single check up front turns every confusing failure into an honest “down for maintenance”.
Data safety as a test, not a form
The new generator knows what each app says it collects. The compiled manifest knows what it actually brings in: permissions, ad SDKs, the advertising ID. Diff the two at upload time and the build refuses to ship anything the form doesn't admit to.
The app manager manages itself
The app board shows the newest build of every app with a one-tap install. The Sparky app isn't listed on it, so six of its own builds have sat unshipped for a week. One registry line fixes that.
Publish when the memory guard fires
After last week's freeze, a guard now kills runaway processes before the box thrashes. It works quietly, which means nobody knows when it did. One honesty row would name the process that got killed, so a mystery restart becomes a published fact.
A login that renews without needing itself
What already exists: a script that opens the login and emails the link; a script that feeds the code back; an honesty check that warns three days out; a token-state reader; and an admin panel with its own phone app that already runs box-side actions.
The one missing piece: a renewal form that isn't an AI chat.
Smallest step: one panel route that wraps the two scripts, plus a phone card showing days left and a paste field. It sits behind its own strong key — this endpoint can sign the box into an account, so it gets the best lock on the panel. After that, the next renewal is a ten-second chore even if the deadline slips past.
Declared vs observed
Every app here makes claims: “opens no sockets”, “nothing about your child is stored”, and now five official Data safety forms. The box already has a headless Android emulator. Run each release candidate for a scripted minute, log every host it contacts, and diff that list against the declaration. Publish PASS or FAIL per app on the public instrument panel. A claim with no test behind it is counterfeit; this makes the store listings themselves auditable. Start with the lottery ledger, whose expected list is nearly empty.
Tomorrow's suggestion
Renew the login before the afternoon deadline — everything AI-backed stops otherwise, this dream included. Then install the newest Sparky build that has been waiting since the first of the month. If there's time left, build the renewal card so December's renewal never races the clock.