Catalog
Working
Reviewed vendors, immutable booth codes, one offer per booth assignmentLive project · Vocaloid events
Mirai Guide
A trilingual, offline-first companion for Vocaloid concert events — venue goods, crowd-reported stock and queues, maps, and a day plan computed backwards from what you want.
MIRAI GUIDE / CAPABILITY BOARDLIVE AT EVENTS
Venue maps
Working
Normalized booth anchors across pages, floors, and map revisionsOffline PWA
Working
Installable, loginless, and usable from the published bundle inside the venueLive reports
Working
Trust-weighted consensus with a 15-minute recency half-life and restock recoveryObtainability
Working
One survival curve drives the route, the live headline, and the leave timeCommunity globe
Working
A third keypair and ~100 km cells snapped before signing; presence counts onlyDay planner
In active development
Wake-up time derived backwards from sellout risk, rendered as rangesWalkable navigation
Research
Color-segmented navigation grids from the map raster, with hand-authored portalsAttendees stay loginless and the app keeps working offline inside the venue. It answers the questions a fan actually has: what is here, is it still in stock, how long is the line, and what time do I need to get up.
The repository holds no event facts; the database starts empty. Approved sources are extracted into typed proposals, and a human reviews every one before a row exists. Booth codes are immutable — corrections supersede rather than edit.
- Two Workers · attendee PWA and an isolated ingestion pipeline
- D1 · reviewed structure, live state, append-only audit history
- R2 · immutable published bundles and reviewed product images
- Vision inputs · transient; only hashes and normalized coordinates persist
The community globe uses a third keypair and snaps location to ~100 km cells before signing, so a dot means “somewhere in this cell” even if the table leaks. The telemetry disclosure is a release gate, not a footnote.
Technical notes
Written from the thing that actually runs.
Mirai Guide: planning a day backwards from the thing you want
A wake-up time derived right-to-left from sellout risk, and the historical corpus that calibrates it.
↗Mirai Guide: a globe of where people came from, without tracking anyone
Three separate device identities, ~100 km cells snapped before signing, and a telemetry disclosure that gates the deploy.
↗Mirai Guide: serving an event crowd on one SQLite database
D1 is a single-primary SQLite with a serial write queue. The architecture question was never how to make it faster — it was how to make sure almost nothing ever talks to it.
↗Inside Mirai Guide: an offline-first event companion
How a loginless PWA, two Workers, and a hard binding-data rule keep a fan-run event guide trustworthy.
↗Mirai Guide: reading walkable floors from the map raster
Why booth-gap inference failed, and how color segmentation of the venue map yields a navigation grid for A*.
↗Mirai Guide: turning crowd reports into a stock signal
Trust-weighted consensus with a recency half-life, and the stale-sold-out death spiral it exists to prevent.
↗Mirai Guide: one survival curve behind every answer
Collapsing three disagreeing shopping orders into a single function of time, so the route, the headline, and the leave time finally agree.
↗Mirai Guide: extraction with a human veto
The ingestion pipeline that turns approved public sources into reviewed structure — and why booth codes are immutable.
↗Mirai Guide: three languages without a translation CMS
UI catalogs that fail loudly, i18n columns for structure, and reviewed model translation for the catalog.
↗Mirai Guide: anchoring booths to venue maps
Vision-assisted map review that stores normalized coordinates and hashes — never the uploaded bytes.
↗Mirai Guide: modeling the goods queue
A three-phase queue model where the sellout clock, not register counts, reveals booth throughput.
↗