# The homepage is a vault: what changed in v1.1.0, sgit.ai > The changes to the article "The homepage is a vault" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · 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) / [The homepage is a vault](../../the-homepage-is-a-vault.md) / [Versions](../the-homepage-is-a-vault.md) / v1.1.0 # The homepage is a vault: what changed in v1.1.0 From v1.0.0 (2026-10-15, `abd6663ae`) to v1.1.0 (2026-10-18, this release), paragraph by paragraph. 0 paragraphs added, 0 removed, 2 changed in place, 52 unchanged. About 2 words added and 1 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../the-homepage-is-a-vault.md) 1 unchanged paragraph Summary: The homepage of this site has to be fresh every day, and today it changes only when someone releases the site. I wantwould like a job that runs every morning at about 05:45, reads the latest articles, the wires and what is happening in the industry, and writes a new edition of the homepage. And I want that homepage toshould be a vault. Every edition a commit with a signed tag and its own version line; every edition carrying the links it showed and why, a screenshot of itself and the release note that explains it; any past homepage one commit id away; variants side by side for A/B tests; and anyone who wants their own homepage, in another language or for another audience, forks the vault. The encrypted objects can be served as plain files from S3, a CDN or GitHub Pages, read in the browser with a published read key. I had two facts wrong: this site is not served by a Lambda, it is on GitHub Pages; the Lambda is the vault API the wire reads through, and that is where the time goes, at 317 milliseconds a request against 44 for a static file. This site's agent built the homepage vault locally: three editions, three signed tags, a static export, and a browser that rendered today's edition in four requests, yesterday's in three, and nothing at all inside two minutes. A stats lane took 300 page-load beacons. This is the design, the measurements, and the brief. 11 unchanged paragraphs, under In short {#in-short}, Why the homepage needs this {#why} The homepage is the page that most needs to be fresh and the one that changes least. Today it is generated when the site is released, so it moves when I publish and stands still when I do not. What I wanthave in mind is an edition: every morning, a job that looks at the latest articles, the wires, and what is happening in the industry we write about, and decides what leads, what follows and what rotates out. The structure, the highlights and the selections are the edition. Parts of the page can stay dynamic: the wire and the full list of articles load live, from their own sources, as they do now. 40 unchanged paragraphs, under Correcting the memo {#correction}, Plain files are enough {#static}, The demo {#demo}… [all versions](../the-homepage-is-a-vault.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/the-homepage-is-a-vault/v1.1.0.html)*