Home / Articles / The proof moved up, the homepage after the rebuild, next to the before pictures / Versions / v1.2.0
The proof moved up, the homepage after the rebuild, next to the before pictures: what changed in v1.2.0
From v1.1.0 (2026-09-07, 60bceff94) to v1.2.0 (2026-09-20, 8b46d2853), paragraph by paragraph.
0 paragraphs added, 0 removed, 10 changed in place, 21 unchanged. About 0 words added and 14 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 · all versions · v1.2.1 →
# The proof moved up —up, the homepage after the rebuild, next to the before pictures
Summary: The previous article diagnosed a homepage that led with encryption and buried twenty-five real vaults under a table. This is the rebuild, put beside those screenshots —screenshots, what moved, what was cut, what it is generated from, and the one thing it still cannot show.
5 unchanged paragraphs, under The first screen
!shot after-hero.webp | images/ | After. Four published vaults with their screenshots, each one click from open. pip install is still there —there, second.
The sentence changed from *"the encrypted git for humans and AI agents"* to *"a vault is a unit of work: data, app, history and sources, shipped as one string."* Encryption did not leave; it became the subordinate clause —clause, *and the server that stores it cannot read it* —it*, which is where a property you cannot see belongs. The four cards are chosen by a hero field in the vault data, so changing the front door is a data edit, not a page edit.
2 unchanged paragraphs, under The use cases became things
!shot before-usecases.webp | images/ | Before. "Multi-agent collaboration —collaboration, agents on their own branches, humans reviewing the merge." True, and not something you can open.
5 unchanged paragraphs, under The collaboration story got a front door
!shot before-briefs.webp | images/ | Before. The cross-team briefs —briefs, the record of agents working with each other and with the human —human, three levels from the homepage, written as a log.
1 unchanged paragraph
!shot after-team.webp | images/ | After. Four numbers computed at build time — releases,(releases, vaults, sibling sites, briefs —briefs) and the loop told in three beats with the artefacts linked.
4 unchanged paragraphs, under What was cut
• Nothing from the terminal walkthrough. It moved down and gained a heading — *Under(*Under the hood, it is git* —git*) because for the visitor who has just opened a real vault, *how* is now the question. It gained one feature card too: *apps live inside the data*, which was somehow never on the list.
The band count did not change —change, nine before, nine after: three were cut and three were added, so what changed is the order and what comes first, not the length. (The first version of this paragraph said "nine became eight"; it was corrected in v0.2.61 after counting rather than remembering.) The page is longer in bytes, because it carries ten screenshots, and slightly shorter in words: 1,370 to 1,332. That is the trade: pictures of real things instead of paragraphs about them. The screenshots load lazily and through the same mechanism every vault page uses, so the page still renders from inside a vault.
1 unchanged paragraph, under What it cannot show yet
The previous article named a gap, and the rebuild did not close it: no published vault demonstrates two agents on one vault —vault**: their branches, and a human merging them. The team band tells the story of agents building *for* each other, which is true and evidenced. It does not yet show agents building *with* each other in the same history, which is the site's strongest claim. The band is written so that it does not pretend otherwise. When that vault exists, it goes in the hero.
3 unchanged paragraphs, under What it is generated from