# The proof is two clicks behind the claim, what the homepage gets wrong, and the fix: what changed in v1.1.0, sgit.ai > The changes to the article "The proof is two clicks behind the claim, what the homepage gets wrong, and the fix" 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) / [The proof is two clicks behind the claim, what the homepage gets wrong, and the fix](../../proof-behind-the-claim.md) / [Versions](../proof-behind-the-claim.md) / v1.1.0 # The proof is two clicks behind the claim, what the homepage gets wrong, and the fix: what changed in v1.1.0 From v1.0.0 (2026-09-07, `3ff7d016e`) to v1.1.0 (2026-09-20, `8b46d2853`), paragraph by paragraph. 0 paragraphs added, 0 removed, 14 changed in place, 31 unchanged. About 0 words added and 20 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../proof-behind-the-claim.md) · [v1.1.1 →](v1.1.1.md) # The proof is two clicks behind the claim —claim, what the homepage gets wrong, and the fix Summary: Twenty-five real vaults a stranger can open in one click are the most persuasive thing on this site, and the homepage shows none of them. It leads with encryption, which cannot be seen, and buries the artefacts under a table. This is the diagnosis, with screenshots, before the rebuild —rebuild, and the second article will show what changed. 5 unchanged paragraphs, under The homepage leads with the thing you cannot see Every word of it is true, and almost none of it is *persuasive*, for one reason: **encryption is a property you cannot look at.** Zero knowledge is a property you cannot look at. The visitor is asked to take the value on faith before being shown anything —anything, and the first thing they are then shown is a terminal walking through `create`, `commit`, `history` and `clone`, which any git user has watched a thousand times. The walkthrough demonstrates *familiarity*, which is a virtue, but not *power*. 4 unchanged paragraphs, under The use cases are abstract while twenty-five concrete ones sit one level down These are categories, not examples. *"Multi-agent collaboration —collaboration, agents on their own branches, humans reviewing the merge"* is a description of a capability. Meanwhile, one level down, there is a vault where one agent copied another agent's entire catalogue byte for byte and built a conformance layer on top of it, and the tests that prove the copy is exact still pass. That is the same idea, except you can open it. 5 unchanged paragraphs, under The proof is a table, two clicks away !shot before-vaults-table.webp | images/ | The published vaults, as of this week: sortable, categorised, and still a table —table, the right shape for finding a vault, the wrong shape for being convinced by one. To be fair to the table, it was rebuilt this week and it is now a good table —table, sortable, categorised, newest first, with the read keys moved off it because they were squeezing the vault id to one character per line. But a table is the right shape for *finding* a vault and the wrong shape for being *convinced* by one. It answers "which of these do I want" for a visitor who already wants one. 1 unchanged paragraph !shot proof-insurability.webp | images/ | A real vault, open: the AIUC-1 conformance layer computing insurability for a named subject as of a date —date, one condition met, 52 exclusions, zero of five consequences covered, each with the reason in the control's own words. 5 unchanged paragraphs, under The strongest story has no front door • That vault was reviewed by the team that owns the API it uses, who found the brief had been wrong in two places —places, and the correction is now published above the mistake. 2 unchanged paragraphs !shot before-briefs.webp | images/ | The briefs page —page, the cross-team collaboration log —log, filed under Docs, three levels from the homepage, and written as a log rather than a story. It is filed under Docs. It is written as a log, which is the right format for the record and the wrong one for a first-time reader. The productivity claim that the whole site rests on —on, *this is what working with agents looks like when the state is versioned and shareable* —shareable*, has no page that tells it end to end. 5 unchanged paragraphs, under One gap worth naming, The fix, in order 1. **The hero shows vaults.** One reframed sentence — a(a vault is a unit of work: data, app, history and sources, shipped as one string, and the server cannot read it —it) with **four real vaults as cards** under it, each with a screenshot and an *open it* link. The visitor is inside an artefact before they have read a paragraph. `pip install` stays, second. 2. **"What people actually ship"** —ship"**: six vaults chosen by *job* rather than by shape: hand over a report, publish a standard as data, give a talk, pitch an investor, run a game, give an agent a workspace. Each with one line on why it is hard without this. Generated from the same data as the table, so it never goes stale. 3. **"One human, a team of agents"** —agents"**: the collaboration story told as a story, with the numbers, and a single page behind it that walks the loop end to end. 4. Then the terminal walkthrough and the zero-knowledge explanation, for the developer who is *now* interested in how. 5. The honesty band and the network band stay. The "three doors" band moves to the docs. 1 unchanged paragraph, under And a page that says who is behind it A beta tool that asks people to publish their read keys on it is asking for trust, and this site has no page saying who is asking. There will be one. It will be about **sgit** — who(who builds it, honestly including the agents; why; the commercial line —line) and it will borrow two sections that fit this site's culture exactly, *Interests declared* and *Reach me, or correct me*, from the fuller record that already exists on a sibling site: !site open-source.sgit.ai | /about/index.html | About the author —author, Dinis Cruz | The record across four companies, built in the open including the parts most companies keep closed, and the interests declared. That card is new as of this article. The `*.sgit.ai` sites exist so each topic can get the depth a section here could not give it —it, which only pays off if this site points at them constantly, and a bare link does not say *this continues elsewhere, on purpose*. The card does. Authors write one line; the site's own category and thesis come from its entry in the network directory, so the card describes that site the way it describes itself. 3 unchanged paragraphs, under What happens next [all versions](../proof-behind-the-claim.md) · [v1.1.1 →](v1.1.1.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/proof-behind-the-claim/v1.1.0.html)*