# Green does not mean live: what changed in v1.1.0, sgit.ai > The changes to the article "Green does not mean live" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.40 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [Green does not mean live](../../green-does-not-mean-live.md) / [Versions](../green-does-not-mean-live.md) / v1.1.0 # Green does not mean live: what changed in v1.1.0 From v1.0.0 (2026-08-19, `dbfd422f0`) to v1.1.0 (2026-09-20, `8b46d2853`), paragraph by paragraph. 0 paragraphs added, 0 removed, 7 changed in place, 29 unchanged. About 0 words added and 7 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../green-does-not-mean-live.md) · [v1.2.0 →](v1.2.0.md) 2 unchanged paragraphs Two consecutive releases of this site pushed cleanly, verified themselves against both remotes, printed **"both remotes in sync —sync, done"**, and never reached anybody. The site served a two-release-old page for forty minutes. It was noticed by a human on a phone, who looked at the version badge and said *"is this the latest version?"* 3 unchanged paragraphs, under What the release actually verified 1. Build the site from source. 2. Run the validator —validator, structure, links, markdown twins, orphan pages, and a tripwire that scans every tracked file for a vault key. 3. Commit and push the encrypted vault; confirm `sgit status` reports in sync. 4. Commit and push the git mirror; confirm `HEAD == origin/dev`. Step 4 is where the confidence came from, and it is genuinely a strong check —check, it compares hashes, not hopes. The problem is what it means. It means **the bytes arrived at GitHub**. It does not mean anybody can read them. 5 unchanged paragraphs, under The gap, named, What actually failed Not our code. Not the content. The deploy job died in **"Set up job"** —job"**: before running a single step of its own: 7 unchanged paragraphs, under The fix is one question, asked at the end The cost is real: up to eight minutes of waiting on every release. We took it, because the alternative had already been demonstrated twice in one afternoon —afternoon, telling somebody a fix was live when it was not, twice, in writing. 2 unchanged paragraphs, under The rule underneath • **A page nothing links to is unpublished.** The build fails on an orphan page —page, it happened once, a brief that was written, built and pushed while nothing linked to it. • **A page the machine index omits is unpublished.** The build fails if any page would be missing from `llms.txt` —`llms.txt`, that happened too, a whole section silently absent. 10 unchanged paragraphs, under What this does not fix [all versions](../green-does-not-mean-live.md) · [v1.2.0 →](v1.2.0.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/green-does-not-mean-live/v1.1.0.html)*