<!-- generated from admin/versions.html by admin/build/gen_markdown.py — do not edit by hand -->

*[open-source.sgit.ai](/index.md) · site v0.2.2 · canonical: https://open-source.sgit.ai/admin/versions.html*

> Site release history. Every push to dev is a release, validated then auto-tagged by CI against the version in admin/build/version.txt and the release commit's subject.

---

# 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 →](index.md#pipeline)

| Version | Date | What shipped |
|---|---|---|
| v0.2.2 | 6 Sep 2026 | **Q5 decided: CC BY.** The one open question that only the author could answer — whether the CC0 licence on the published-articles repository was a deliberate third layer or drift — is answered: drift. The documents layer is CC BY 4.0 throughout, and the estate has two licences across three layers: Apache-2.0 for code, CC BY 4.0 for everything written. Recorded on [the practice page](../practice/index.md#reading) (which still reports the CC0 file as it is on disk, until it is replaced), on [the roadmap](../roadmap/index.md#open), on [the comms board](../admin/comms.md) (N1 answered), in the documents divergence table, and in the README. [Thesis (d)](../agents/index.md#cc0) is reframed from "what CC0 means for machine reuse" to what CC BY means — attribution as the one obligation that survives into a synthesised output. |
| v0.2.1 | 6 Sep 2026 | **The company list, corrected by the author.** Akeia.ai removed — he has stepped down from it. [RiskMandate.ai](https://riskmandate.ai) and [VoiceDebrief.ai](https://voicedebrief.ai) added as the most recent startups. And [sgraph.ai](https://sgraph.ai) added as the place where the strategy has started to turn into revenue: the commercial home of SG/Send, and where access to SG/Vaults — hosted sgit vaults — is sold, with the code staying Apache-2.0. On [the about page](../about/index.md), the front page byline and author section, and the README. |
| v0.2.0 | 6 Sep 2026 | **The site becomes the author's position, written as one.** The first release read as an audit of its own material — a "where this site is weak" section on the front page, a "what is missing" page, a "where we lose" disclosure, a stage pill reading *first draft*, and argument pages that described the author's writing as "the corpus" arguing with itself. That framing undersold work that is, in substance, a founder's strategy backed by a shipping estate. This release keeps every counter-case and every open question, and drops the self-deprecation. **New: [Owning the code, or opening it](../founders/index.md)** — guidance for founders from a strategy session with an early-stage SaaS founder: what copying the code would actually cost an incumbent, four instincts and their counter-arguments, the explorer–villager–town-planner frame, eight steps in order, and what a week of building in the open looks like when it is counted. Released CC BY; attribution Dinis Cruz and Kate Curtis-Evans. It is the first section on the front page and the first group in the nav.**New: [About the author](../about/index.md)** — Dinis Cruz, the companies the strategy runs on (sgit.ai, MyFeeds.ai, The Cyber Boardroom), the OWASP record, the tooling lineage from the O2 Platform, and the investor materials published in the open. Interests are declared on the same page, in two paragraphs rather than a discount table. Replaces `about/participant.html`.**Folded: `shipped/index.html` into [What's next](../roadmap/index.md).** The forward-looking content — what is built, what is next in order, eight open questions — was already on the roadmap; the duplicate page that restated it as a list of failings is gone, and every link to it now lands on the corresponding item.**Reworded across the site:** the front page (byline under the hero, founders first, the weakness section replaced by what's next, the author section), the self-audit (a result and a plan rather than "we fail leg one"), the practice page (three layers with a job each, and one alignment question, rather than "an inconsistency nobody had noticed"), open-core and agents (a position that moved between two dates, rather than a contradiction), funding, OWASP, history, numbers, and the footer — which now carries the author line instead of a warning triangle. The markdown twins, `llms.txt` and `llms-full.txt` regenerate from all of it. |
| v0.1.2 | 6 Sep 2026 | **Two external sources cited, where the site had been naming sources without linking them.**[The numbers page](../history/numbers.md#88tn) now links the **HBS AI Institute** summary of working paper 24-038 — the origin of the $8.8tn figure it spends a section correcting — with its authors, its data sources, and the two concentration findings in it that are more useful than the headline. A page whose credibility position is that it checks other people's citations should carry its own. **And [the training-data thesis](../agents/index.md#training) acquires a dated instance.** Mozilla's chief executive, interviewed by **The Deep View** in August 2026, is shipping model choice in Firefox and backing **open-weight** models on lock-in grounds — making this site's standards-and-control argument, in his own words, about models rather than code. Cited with the caveat it needs: it is positioning from an interested party, and it [sharpens Q7](../roadmap/index.md#open) rather than settling it, because open weight is the category the OSI's definition excludes. |
| v0.1.1 | 25 Aug 2026 | **The build tooling was never committed.** The repository's stock Python `.gitignore` carries a bare `build/` rule, which silently swallowed the whole of `admin/build/` — `chrome.py`, `gen_markdown.py`, `validate.js` and `version.txt`. Everything passed locally, where the files exist; the first CI run failed at once, on the very first step, because they were not in the checkout. Fixed with the same `!admin/build/` negation the sibling sites carry. Recorded here rather than amended away, because [a site that publishes its own failed audit](../survivability/self-audit.md) does not get to quietly rewrite a bad release out of its history. It is also a small illustration of the pipeline working as intended: **the release that could not be validated never got a tag and was never published.** |
| v0.1.0 | 25 Aug 2026 | **First release.** The site, built from the commissioning brief pack, which is [published verbatim alongside it](../documents/index.md). **The pipeline first**, matching the sibling sites: validate → auto-tag → deploy, with the version owned by one file and verified against the release commit's subject. Validation additionally enforces the things this site's own argument depends on — **a markdown twin at every URL**, `llms-full.txt` carrying every page, and a CC BY 4.0 footer on every markdown file.**The content:**[the position](../views/index.md) with every argument carrying its counter-case; [survivability](../survivability/index.md) with [the stress test as a working tool](../survivability/stress-test.md) and [a self-audit run on the estate itself](../survivability/self-audit.md); [six corrections](../history/index.md) leading the history rather than a timeline; [the three-licence estate](../practice/index.md) and [the Apache-vs-MIT page that existed nowhere](../practice/apache-vs-mit.md); [agents](../agents/index.md); [the three funding proposals compared for the first time](../funding/index.md) and [cURL](../funding/curl.md); [the summit history](../owasp/index.md); and the build order with its open questions visible.**Two things deliberately not done:** the CC0/CC BY licensing question is [published unresolved](../practice/index.md#reading) rather than settled on the author's behalf, and the SBOM the site tells other people to publish [is first on the build order rather than shipped](../roadmap/index.md#supply-chain). Both are [recorded as divergences from the brief](../documents/index.md#divergences). |

> **Reading a version number.**`v{release}.{major}.{minor}` — every push to `dev` increments the minor. CI refuses a tag that is not the next minor (or a deliberate major), and refuses one where `version.txt` and the commit subject disagree, so the history above cannot silently skip a release.

[← Comms](comms.md)[Front page →](../index.md)

---

*This page is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).*
