pki.sgit.ai / packs

Dev packs

Implementation-plan packs, captured verbatim and presented the same way as the site's documents: a hub per pack, and a reader page per document with a summary, key concepts, key ideas and the full markdown (diagrams rendered). The treatment follows nhi.sgit.ai's packs section; a pack here carries its architecture, its diagrams, its change control and its tabletop exercise as first-class documents.

PackDate · statusIn one line
The Registry MVP: Open Data, A Single Operator, LLM Sessions First20 Aug 2026 · draft + change controlA public key registry on vaults — open data, one operator, and LLM sessions as the first users on both sides. 15 documents and four appendixes — a PR/FAQ, a PEP-style specification, and change control — and one of them is built. Downloadable as a briefing pack.
Map Your Case: The Grant–Mandate Delta, Mapped By Its Owner21 Aug 2026 · draft + change controlThe dev pack for the assessment — the one thing on this site that is built rather than specified. Thirteen documents and a change-control appendix: the principles each purchased with a mistake, the library, the model, the two 20 August programmes (levels × variants, and synthetic readers behind a screenshot boundary), sharing by fragment, four Wardley maps, and the honest record of the first MVP.
Grant and Mandate: Reality Before Risk, The Library In The Registry, The Instance In The Risk Product26 Aug 2026 · draft + change controlBuilding blocks for the RiskMandate product: a grant measured, a mandate authored, the delta between them, and a library of measured grants. Ten documents plus change control, two measured library entries, a component stylesheet with a gallery rendering real data, and build-order step 1 built: a push refused by git, not by the agent. Document 08 is the build record — what shipped, and what is still only written down. The registry holds the library (no personal data ever); the risk product holds the instance, storing references not copies.
The Insurance Ecosystem: A Session Told The Rules, Handed A Policy, Measured, And Refused By Something That Is Not Itself3 Sep 2026 · draft-1, step 1 builtAn end-to-end ecosystem on vaults: three vaults, a policy object generic on unit, a ledger that is only ever added to, git hooks as the enforcement point, Claude hooks as instrumentation, and a room of five cards. Eleven documents plus change control; an evaluator, two hooks, a token meter and a room builder in tools/; and step 1 built and run — a 400 KB commit refused by git, the eleventh commit of the day recorded as a draw, a push outside the mandate refused. The room renders from the run.
Adding a pack. Sources land under packs/<name>/src/ verbatim; the pages are one entry in admin/build/gen_packs.py, then chrome.py applies the shared nav and footer.