ungovr.providers.sgit.ai / Four decks, from the vault
Four decks, from the vault
Four presentations, 39 slides, written as ordinary markdown in the vault and rendered here as real 16:9 slides — and as PDFs you can send to somebody. They read as documents in the vault browser, as slides in the vault's app, and as slides here; if they ever disagree, the markdown is right.
Prose from the government-graph vault dkeclt5r @ obj-cas-imm-a6f0269b0967, 9 September 2026. Republished byte for byte from decks/ in the vault; check_site.py verifies every file against a recorded sha256, so a copy that drifted would fail the build. When the vault moves ahead, this page is behind — and says so rather than guessing.
| # | Deck | What it covers | Slides | |
|---|---|---|---|---|
| 01 | What we learned about UnGovr | Eight findings from 76 hashed requests: the 0-of-49, why nobody can census it, the 96.6% that is one hop away, and the licence split | 10 | ⇓ 1522 KB |
| 02 | What we built on the site | The provider report, the argument for admitting an open-data provider at all, and the checks that make its promises enforceable | 9 | ⇓ 1538 KB |
| 03 | How this composes | What this vault contributes to Risk Mandate, Licence to Operate and the AIUC-1 conformance layer — and what it took from them | 10 | ⇓ 1138 KB |
| 04 | What we plan to build | The security-standards dev pack: the 95 crosswalks that point at law, the vocabulary we forked by accident, and the blocker that would kill the thesis | 10 | ⇓ 1079 KB |
Start with 01 if you have never met the data, and 04 if you have. verified 9 Sep 2026
The PDFs are the point
Each deck prints to a 16:9 PDF at the estate's deck geometry — 1200×675, one slide per page, no cropping and no second page for a stray footer. verified 9 Sep 2026 They are generated from the same markup the page renders, so a slide cannot look one way here and another in the file somebody forwards.
Every screenshot in them is of this site, captured from a real build rather than mocked, and every slide that has one carries a link back to the page it shows — absolute, so they resolve wherever the PDF is opened. verified 9 Sep 2026 That is what makes them worth sending: a reader who never visits the site still sees what it does, and a reader who wants more has the URL in front of them.
The screenshots and the links are the site's addition, not the vault's. The words on every slide are the vault's, republished byte for byte. data/deck-extras.json holds the mapping and says so at the top of the file.
How to read them
Every slide is stacked on the page, numbered, with its speaker notes visible — it is a document first. Present shows one slide at a time with ← and →, Esc leaves. Hide notes strips the notes for a cleaner read or a cleaner print. A link to #s7 opens that slide.
None of it needs JavaScript to read: the enhancement is present mode and the toggle, and everything else is in the HTML.
Why these are rendered rather than read live
sgit.ai's decks-from-a-vault brief describes a live viewer: the host fetches deck sources from the vault with a read key, runs them in a sandboxed opaque-origin frame, and renders the slide markup in a second frame with scripting off entirely.
This site does it differently, and the reason is its own contract. Every page here is static and contacts nothing, with exactly two named exceptions. A live deck viewer would have made every deck page a third, and would have needed a vault reader and two sandboxed frames to do safely what a build step does for free. verified 9 Sep 2026
What that costs is liveness. When the vault moves ahead of this site, this site is behind — and says so rather than guessing. The live decks are one click away: they are the Decks view of the vault's own app, which runs on the vault page and on the estate page, and they move the moment the vault does.
What carries over from that brief unchanged is the part that matters most: the raw markdown is always available for every deck, the viewer is an addition rather than a replacement, and every rendered slide is one click from the file it was rendered from — 01 · 02 · 03 · 04.
Markdown is the source, and that is the whole point
A slide is an ## heading and everything under it, split on a --- rule. A blockquote opening **Notes.** is speaker notes. Front matter carries the title, subtitle and date. That is the entire format.
The site's parser is a port of the vault app's, so both render the same slides from the same bytes. It is the same reason the estate's book is generated from its site's markdown rather than authored twice: a presentation that is a projection of a document cannot drift from it.