sg-compute.sgit.ai / admin / versions

Release history

Every push to dev is a minor release. The version is owned by admin/build/version.txt, must appear in the release commit's subject, and is tagged by CI once validation passes — so every row below corresponds to a tag on a commit that was gated. The pipeline →

VersionDateWhat changed
v0.2.0 25 Aug 2026 The refocus: lead with what shipped. The site's first release led with the audit; this one leads with the platform — requested by the project lead, with the audit kept in full one click away. The front page now opens on the launch-work-terminate lifecycle, the generated ten-verb CLIs, the 71,000-line AWS operator toolkit with its interactive REPL/TUI, the 25-verb sequence language, and the built-in web consoles — every claim still measured from the tree. /shipped/ now opens with the working surface before the ledger, and the ledger items are framed as the contributor's map. Nav group “The audit” renamed to “Shipped”; stage pill moved from audit draft to early access; index.md and llms.txt rewritten to match.
v0.1.1 24 Aug 2026 The release gate was not in the release. The repository's Python .gitignore carries build/, which silently swallowed admin/build/ — so every generator and validate.js passed locally and were absent from the checkout, and v0.1.0's validate job died on a missing file before it could check anything. Added the !admin/build/ negation the sibling repositories carry. Also: fixed a mobile overflow on /specs/, where an unbreakable module path pushed the page 100px wide at 390px.
v0.1.0 24 Aug 2026 First release. The site, built from the v0.33.62 brief pack. CI pipeline (validate → auto-tag → deploy) with the generator drift check and the live-infrastructure leak tripwire; the front page leading with the four-character guard bug; the two ephemeral layers; the spec catalogue generated from data, 17 pages; the serverless argument; the measured numbers including the seven capacity failures; the rename scored against its nine criteria; the unsoftened ledger; the machine surface with the auth correction; isolation and the EC2-tag trade-off; eight questions published unresolved; the twelve source documents, two redacted under their own rule.