# The vault, opened: what changed in v1.2.0, sgit.ai > The changes to the article "The vault, opened" in v1.2.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 vault, opened](../../the-vault-opened.md) / [Versions](../the-vault-opened.md) / v1.2.0 # The vault, opened: what changed in v1.2.0 From v1.1.0 (2026-10-18, `9f74e5714`) to v1.2.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph. 0 paragraphs added, 0 removed, 5 changed in place, 45 unchanged. About 0 words added and 221 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-vault-opened.md) 2 unchanged paragraphs !shot vo-viewer.webp | images/ | A demo reader vault opened read-only in the SG/App at dev.vault.sgraph.ai, read-only,drawnfrom its published read key. The page isby the newsroom's viewer: its code came from a different vault, lkypj6zq, through a link file, and it drew the account from the demo vault's own records, a balance of £4.84, three pages read, two notes, two devices. The badge at the top right says the session cannot write.viewer. | screenshot 12 unchanged paragraphs, under In short {#in-short}, What was asked {#asked}, Merging devices {#merge} !shot vo-merge.webp | images/ | The Vault tab in the pane, 400 pixels wide,wide in Newsprint, with two devices ticked inandAcrossanyour devices. The bar under the table offersoffer to merge them into one of the two, under a name that can be changed, and says that nothing is deleted. The total row is the account recomputed from the records.them. | small | screenshot 5 unchanged paragraphs, under A chooser that says where a browser goes {#chooser}, The calls, as a tab {#calls} !shot vo-calls.webp | images/ | The Calls tab, widened,tab after an update of the reader vault.vault,Onewith one batch call is open: insidefile,it, a file's contents (the entry page the update wrote), a tree with six entries, atree, commit with its message, time, tree and parent, and a ref pointing at that commit. Each was decrypted in the page with the reader vault's key; the server holds only the ciphertext.ref. | narrow | screenshot 3 unchanged paragraphs, under Your vaults, file by file {#browse} !shot vo-browse.webp | images/ | The page Your vaults, opened,vaults after a merge: the reader vault's tree on the left,tree, the merged device's file in the middle with the device it was merged from in its header, and the commits on the right,commits, newest first, from the merge back to the vault's creation. Picking a commit shows the tree and the files as they were then.first. | small | screenshot 2 unchanged paragraphs, under One viewer that every reader vault opens with {#viewer} !shot vo-link.webp | images/ | How the viewer is linked. Left,linked: a reader vault: its records under activity/, and four small files the next Update writes. Right,vault, the newsroom's viewer invault,vault lkypj6zq, with its code. Below,and what the SG/App does whentoitopenopens the reader vault: reads the manifest, opens the viewer vault read-only from the owner record, loads the viewer's code through the link, and lets it read the reader's own records.them. | architecture 21 unchanged paragraphs, under What changes for you {#for-you}, Where things stand {#stands}, What this does not claim {#limits}… [← v1.1.0](v1.1.0.md) · [all versions](../the-vault-opened.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/the-vault-opened/v1.2.0.html)*