nhi.sgit.ai / admin / versions
Release history
Every push to dev is a release: CI validates the site, verifies the version bump, tags the commit v{release}.{major}.{minor}, and deploys to GitHub Pages. The version is owned by admin/build/version.txt and must agree with the release commit's subject.
| Version | Date | What shipped |
|---|---|---|
| v0.1.12 | 19 Aug 2026 | Static-publishing pack refreshed to commit 2cedd9a, capturing the pack's most unusual document: an executed tabletop exercise — the maintainer's one-repo-carrying-everything scenario run for real by the dev agent with the shipped CLI (only the unbuilt publish command and GitHub's hosting simulated, marked at every appearance), producing four live findings and measured results (publish → push is a no-op; git dedupes all 17 projection copies; zero-secret CI republish from the committed read key). The document's reader page opens with an explainer for site readers on what a tabletop exercise is and why an agent executing one inside its own codebase is an uncommon use of LLMs. Also in this revision: sgit publish takes no target (one fixed folder; deployment is a separate act — doc 07 rewritten), and the loader is now cleanly separated from a vault's own index.html. |
| v0.1.11 | 19 Aug 2026 | Pack provenance made verifiable: every pack page (hub and per-document) now states the source-repo commit it was captured at, linked, with the guarantee that the raw files under src/ are byte-identical to that commit's tree — the raws stay verbatim precisely so the claim is checkable by diff. The static-publishing pack refreshed to its 18–19 Aug revision (commit 65ebfbd): three new documents from maintainer review — where a published folder may live (the publish-into-work-tree amplification loop; refusals before a byte is written), published API docs (openapi.json generated from the manifest; Swagger UI CDN-pinned with SRI, measured at 2.7× the vault it documents), and the first-party asset origin (publish-time source yes, read-time origin never) — plus the sixth rule/invariant (publishing never changes the vault), phase P4b, and ten maintainer decisions (up from six). |
| v0.1.10 | 18 Aug 2026 | Second dev pack captured: hub.sgit.ai — The Fractal Forge (18 Aug design pack, 9 documents from the SGit-AI__CLI architect-review branch) — the forge whose application layer is the browser, the hub-is-a-vault fractal, the capability audit with its two findings (the sub-vault primitive assumed by every brief does not exist; the structure key is a shipped-but-unused third access tier), permissions as key topology, commercialisation on a blind host, mockups including the live ciphertext panel, and the roadmap with the four stated absences. Sources verbatim under packs/hub-sgit-ai/src/; reader page per document. The pack generator now takes per-pack dates, origins and GitHub sources. |
| v0.1.9 | 18 Aug 2026 | New Packs section for dev brief packs, first pack captured: Static Publishing, sgit vault serve and the publishing matrix — 8 documents from the SGit-AI__CLI architect-review branch, sources verbatim under packs/static-publishing/src/, a hub with the file table and pack README, and a reader page per document (summary, key concepts, key ideas, full markdown). The in-page markdown reader now renders mermaid fences as diagrams, so the pack's sequence diagrams display natively. Packs added to the nav; section generator gen_packs.py. |
| v0.1.8 | 18 Aug 2026 | The eight corpus briefs the collection referenced on GitHub are now captured verbatim in briefs/, each with a full document page (summary, key concepts, key ideas, in-page reader, infographic slot): the hope-driven authorization brief, the catastrophic-risk board thesis, both pull-the-plug briefs, the AOMM source, the sandbox-escape incident analysis, the ambient-authority brief, and the serialised-pull-request brief. Every GitHub blob link on the collection, Hope and AOMM pages now points at the local document page instead; only the wider-corpus pointer still goes to GitHub. |
| v0.1.7 | 18 Aug 2026 | Document links routed through the reader pages: every reader-facing reference to a captured markdown document now points at its documents/ page (summary + in-page reader) instead of the raw file — raw-markdown links remain only inside the document pages themselves, as the source-of-truth reference. The reader restyled as a distinct document sheet: white paper on the cream page, bordered, with an attached label bar naming the source file. |
| v0.1.6 | 18 Aug 2026 | Two new sections. Industry: the market map grouped by which layer each product answers (discovery & governance, workload IAM, secrets & detection, machine identity, platform IdPs), 14 provider profile pages compiled from published analyses, and a SPIFFE concept page with issuance/usage/federation diagrams — concept mentions across the site now link into it. Documents: the original briefs readable in-page — each page carries a summary, key concepts, key ideas, an infographic slot, and the full markdown rendered from the raw file, which stays the source of truth. Both sections are generator-driven (admin/build/gen_industry.py, gen_documents.py). The NHI site brief captured into briefs/. |
| v0.1.5 | 18 Aug 2026 | PKI section, in preparation for pki.sgit.ai: captured the pki.sgit.ai strategy brief (v0.33.59, 16 Aug) verbatim in briefs/; built the hub, the 2019 keyserver-failure page (the three abused properties, the never-delete design goal, what the replacement gave up), and the four registry rules published before the registry exists (owner-only writes, revocation as signed append, size-bounded records, every entry signed; identity vs. mandate). PKI added to the nav; cross-linked from thesis, shared-drives research and the collection. |
| v0.1.4 | 18 Aug 2026 | Captured the shared-drives research brief (v0.33.59, 16 Aug) — source markdown verbatim in briefs/, full presentation page at research/shared-drives.html — and propagated its findings: the thesis page gains its first tested concrete instance; the Hope section gains granularity-by-segregation and attribution-from-content; method and options gain the multi-scenario framing; the collection gains a "can two agents share a working area?" question; comms gains the follow-up tests (one-account-per-agent, audit-trail behaviour) and the monthly re-verification entry. |
| v0.1.3 | 18 Aug 2026 | Comms updated: the site went live at sgit-ai.github.io/SGit-AI__Website__NHI via the one-off v0.1.2 deploy from main; N3 now records what remains (allow dev in the github-pages environment; custom domain + DNS for nhi.sgit.ai). |
| v0.1.2 | 18 Aug 2026 | Deploy from main: pushes to main now run validate → deploy with tagging skipped, so main serves as a deploy-only test/fallback while the github-pages environment still restricts dev. Tagging remains exclusive to dev. One-off test push of this release to main, requested by the project lead. |
| v0.1.1 | 18 Aug 2026 | Release-pipeline shakedown: fixed the first-release edge case in the auto-tag job (empty previous-tag list under pipefail), un-ignored admin/build/ from the stock Python .gitignore, and documented on the comms page the one remaining blocker for going live — the github-pages environment must allow deploys from dev (repo settings, admin-side). |
| v0.1.0 | 18 Aug 2026 | First MVP. The thesis page (two populations), the method (scenario + columns, published before findings), three preliminary option assessments (SPIFFE, commercial broker, do-nothing baseline), the Hope section (concepts and workflows), the collection organised by question, the AOMM promoted to a page, the participant disclosure, the infographics request list, this comms channel, and the CI pipeline with auto-tagging adapted from SGit-AI__Website. |