# The articles behind it > The newsroom.sgit.ai articles that designed, built and reviewed this API, curated for publishers, for the reader's own newsroom, and for the engineering. *api.newsroom.sgit.ai · v0.2.14 (reader code v0.2.5) · this file is generated from the same source as , so the two cannot drift. The site's index for agents: .* --- ## The case - [The future of news is the story vault, not the paywall](https://newsroom.sgit.ai/articles/future-of-news-story-vault-not-paywall.html) (2026-09-22, No. 11): Why a newsroom would want this at all. - [A meter in the browser: a penny a page, a history you keep, and a site that picks for you](https://newsroom.sgit.ai/articles/a-meter-in-the-browser.html) (2026-10-10, No. 57): The reading meter, as it was built. - [Pay after you read: how a reading meter became a working business model in one afternoon, one release at a time](https://newsroom.sgit.ai/articles/pay-after-you-read.html) (2026-10-10, No. 65): Paying after you read, with a rating that sets the price. - [Going live with the reading meter: pay for what you read, go below zero if you like, and the numbers we will check in eight weeks](https://newsroom.sgit.ai/articles/going-live-with-the-reading-meter.html) (2026-10-10, No. 60): Real money, and the line between what runs and what is designed. - [Who will game the reading meter? Eight kinds of reader, nine ways to cheat, and the risks that will actually happen](https://newsroom.sgit.ai/articles/who-will-game-the-reading-meter.html) (2026-10-10, No. 61): The threat model, written before the first pound. - [No server, by design: first I retired the database, now I am retiring the back end](https://newsroom.sgit.ai/articles/no-server-by-design.html) (2026-10-11, No. 72): Why there is no server of ours, and what that buys a reader. ## The reader's own newsroom - [A link to a persona: send people to the newsroom as someone, not as nobody](https://newsroom.sgit.ai/articles/a-link-to-a-persona.html) (2026-10-10, No. 66): A link that opens the newsroom as a persona. - [Pay to keep your persona: readers should pay because it helps them, not because they feel they should](https://newsroom.sgit.ai/articles/pay-to-keep-your-persona.html) (2026-10-10, No. 62): What a persona is worth, and to whom. - [From me to you, in a link: a personal reading list, two briefs to build and use it, and the loop that makes it a day's work](https://newsroom.sgit.ai/articles/a-reading-list-in-a-link.html) (2026-10-11, No. 74): From me to you, in a link: the reading-list grammar. - [I miss it, so it is working: the people who decide the roadmap have to use the product, and the vault the newsroom now needs](https://newsroom.sgit.ai/articles/i-miss-it.html) (2026-10-11, No. 76): The makers must use it, and the brief for the reader's vault. - [The vault is live: from a design on 11 October to a reader's vault on newsroom.sgit.ai by two in the morning, and how all of it fits together](https://newsroom.sgit.ai/articles/the-vault-is-live.html) (2026-10-12, No. 81): The reading account carried between devices. - [The site is an inbox: deciding before reading, marks that build the reader's own graph, and why I could not write this brief until the vault existed](https://newsroom.sgit.ai/articles/the-site-is-an-inbox.html) (2026-10-12, No. 82): Notes to the newsroom, carried by the vault. - [The passkey opens the vault: a door per path, a master vault for every user, and no server of ours](https://newsroom.sgit.ai/articles/the-passkey-opens-the-vault.html) (2026-10-11, No. 77): A passkey's PRF bytes compute a door; no server of ours. - [Where the vault keys live: key management at sgit-ai v0.20.0, and what comes next](https://newsroom.sgit.ai/articles/where-the-vault-keys-live.html) (2026-10-10, No. 64): Where the keys live, and who holds what. ## How it is engineered - [Go slow to go fast: moving the newsroom from an explorer project to a villager one, with the brief to do it](https://newsroom.sgit.ai/articles/explorer-to-villager-newsroom.html) (2026-10-11, No. 78): The brief for the move this repository is: go slow to go fast. - [Code review as a fractal semantic graph: source code is already one, and the review should read every layer of it](https://newsroom.sgit.ai/articles/code-review-as-a-fractal-semantic-graph.html) (2026-10-03, No. 23): The review method: read a change at every layer. - [If somebody built a company on code review: how I would do it, and why it is only now possible](https://newsroom.sgit.ai/articles/if-somebody-built-a-company-on-code-review.html) (2026-10-05, No. 27): Why villager code is read line by line. - [Green does not mean live](https://newsroom.sgit.ai/articles/green-does-not-mean-live.html) (2026-08-17, No. 1): A release ends by asking the live site for its version. - [How to run synthetic users on your own site: five people who do not exist, a browser, and an afternoon](https://newsroom.sgit.ai/articles/how-to-run-synthetic-users.html) (2026-10-10, No. 67): Five readers who do not exist, a browser, and an afternoon. - [Brief the agent too: the people I talk to work with agents, so what I send has to reach both](https://newsroom.sgit.ai/articles/brief-the-agent-too.html) (2026-10-11, No. 75): The people you talk to work with agents; brief their agents too. - [Two agents, one vault: the Industry Wire is written into an encrypted vault by one agent and drawn by newsroom.sgit.ai, which holds only the read key](https://newsroom.sgit.ai/articles/two-agents-one-vault.html) (2026-10-12, No. 80): Two agents, one vault: how the newsroom's agents share state.