Play / About / How this site is built

How this site is built

Static files on GitHub Pages. No server, no database, no analytics. Every page exists once, as content, in admin/build/build_pages.py; nothing under the site root is hand-edited.

python3 admin/build/build_pages.py   # pages, .md twins, llms.txt, sitemap
node admin/build/validate.js          # the gate CI will run

The game is embedded, not copied

assets/vault-app-embed.js opens the vault over the SG/Vault embed protocol: it loads the vault host in an iframe, waits for that frame to say it is ready, and then hands over the read key by postMessage with the target origin pinned. The key never appears in a URL, so it is never in browser history, a Referer header, or a server log.

It is the sgit.ai component with the vault-browser surface suppressed, so a player gets a game rather than a file manager. Using the real host rather than the smaller read-only one is what keeps the game's chat panel and its telemetry lane working — the smaller host serves file reads only.

The gate

The house checks — version agreement, internal links, canonical host, and a key-leak tripwire — plus one that matters more here than anywhere: a page that mounts the game must carry the telemetry disclosure. Mechanical, and deliberately so. The vault this game lives in once shipped two pages saying nothing sent on the same screen as events being sent; the notice is not something to rely on remembering.

Two checks were added on 9 September 2026, each for something that had already gone wrong once: the packs registry must resolve (every entry in data/packs.json carries a block the build read from the pack's own manifest, and a pack on this site hashes to what it says), and the site must say what the vault does (/what-we-learn/ states the same signals value the game's vault carries, read from a clone into admin/build/vault-facts.json and dated).

The drain

admin/proposals/drain.py closes the loop from the map vault: it opens each sealed proposal with the lane's key, applies it to data/ as a patch, runs this gate, commits on a branch, opens the pull request with the reasoning as its body and nobody named, and writes data/proposals.json — what is open and merged per row — which the vault reads. A proposal the gate refuses is reported, not skipped; a counter-example above the ceiling is put to a maintainer rather than patched.

Full engineering notes are on the sibling site: games.sgit.ai/admin.