# The homepage is a vault: what changed in v1.2.0, sgit.ai

> The changes to the article "The homepage is a vault" in v1.2.0, paragraph by paragraph.

*Source: <https://newsroom.sgit.ai/articles/versions/the-homepage-is-a-vault/v1.2.0.html> · 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.2.0

# The homepage is a vault: what changed in v1.2.0

From v1.1.0 (2026-10-19, `d303ce0f1`) to v1.2.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph.

0 paragraphs added, 0 removed, 4 changed in place, 50 unchanged. About 0 words added and 132 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.

[← v1.1.0](v1.1.0.md) · [all versions](../the-homepage-is-a-vault.md)

2 unchanged paragraphs

!shot hm-architecture.webp | images/ | The homepage as a vault: athe morning job writes an edition and tags it, the encrypted objects go to plainjob, static hosting, a small shell onthe GitHub Pages carries the read key and a snapshot for search engines,shell and the browser readsreading the edition. A stats lane and a daily run of synthetic users feed the next morning's edition. Dashed boxes are proposed. | architecture

18 unchanged paragraphs, under In short {#in-short}, Why the homepage needs this {#why}, Correcting the memo {#correction}…

!shot hm-editions.webp | images/ | Three editions of the demo homepage vault, each a commit with a signed tag, carrying its page, the links it showed and why, both variants, its release note and a screenshot of itself. Any edition opens again from its commit id.tag. | comparison

8 unchanged paragraphs, under Who loads what {#sequence}

!shot hm-sequence.webp | images/ | One page load: the shell from GitHub Pages, then four chained requests to the static host for the ref, the commit, the treehost, and the page, decrypted in the browser; the dynamic slots load from their own vaults; a beacon goes to the stats lane. Each step waits for the one before, so where the bytes come from decides the time. | architecture

5 unchanged paragraphs, under History, variants and forks {#history}, Stats, and the readers who do not exist {#stats}

!shot hm-numbers.webp | images/ | WhatThethe measurements say: themeasurements: live numbers from this sandbox to newsroom.sgit.ainewsroom.sgit.ai, and its vault API, and the vault numbers from a local static server and a local vault server, which count requests and bytes, not network time.servers. | comparison

17 unchanged paragraphs, under What has to be handled {#handled}, A brief for the agent {#brief}, What this does not claim {#limits}…

[← v1.1.0](v1.1.0.md) · [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.2.0.html)*
