twins.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. How the pipeline works →
| Version | Date | What shipped |
|---|---|---|
| v0.1.0 | 25 Aug 2026 | The site, first release. The twin primitive published as a reference site, built from the v0.33.62 brief pack. Twelve pages in the commissioned build order: the primitive in full, the discipline of reality with the tracked air gap and the coverage measure, what is built led by the S3-compatible container, the nine-application map with owners, twins as actors, the execution broker with both of its costs published, the naming ruling, the simulation layer labelled as design, the built-and-designed table unsoftened, gaps and open questions, the network boundaries and the participant disclosure. Two of the pack's six gaps close with this release: G1, the naming ruling, and G6, the name-watch, which now runs in the release gate and fails the build on any unruled sense of the word. The brief pack is published verbatim with eight reader pages, marked vendored locally so the site has no external runtime dependency. Pipeline, gate and chrome tooling ported from the PKI site and the graphs site: validate, tag, publish, with licence stamps and the name-watch added to the gate. |
Versioning
The scheme is v{release}.{major}.{minor}. Every push to dev is a minor bump; CI enforces that the new tag is the next minor after the previous one, or a deliberate major. A version may not be reused: if the tag already exists on an earlier commit, the release fails rather than moving the tag.