Home / The articles behind it
The articles behind it
Everything here was designed in public first, as an article on newsroom.sgit.ai, then built, then written about again when it went live. Read them in this order and you have the case, the design and the engineering; each is numbered, so a reading list in a link can carry a set of them to a colleague.
The case
The future of news is the story vault, not the paywall
A story is a graph of claims and evidence and the article is one projection of it; keep the graph in a vault and sell what the article was made from.
Why a newsroom would want this at all.
No. 57 · 2026-10-10A meter in the browser
Every page now costs a few pence from £5 of credit kept in your browser, and the reading history it keeps is what personalises the site.
The reading meter, as it was built.
No. 65 · 2026-10-10Pay after you read
Seven releases in one afternoon turned the reading meter into a working model: pay after you read, and the rating sets the price.
Paying after you read, with a rating that sets the price.
No. 60 · 2026-10-10Going live with the reading meter
Pay for the share of a page you read, go below zero with no nagging, top up £5 on Stripe: the plan, and the numbers we check in eight weeks.
Real money, and the line between what runs and what is designed.
No. 61 · 2026-10-10Who will game the reading meter? Eight kinds of reader, nine ways to cheat, and the risks that will actually happen
Eight kinds of reader, none of them attackers, nine ways to cheat a browser meter, and the quieter risks that will actually happen.
The threat model, written before the first pound.
No. 72 · 2026-10-11No server, by design
First the database went, now the back end: the SGit Newsroom runs all its logic in the browser, on commodity servers that cannot read your data.
Why there is no server of ours, and what that buys a reader.
Send this set: make a reading list of these 6.
The reader's own newsroom
A link to a persona
Send a CISO to the newsroom as a CISO: personas kept in a vault by the newsroom's agents, opened from a link, followed or forked.
A link that opens the newsroom as a persona.
No. 62 · 2026-10-10Pay to keep your persona
Readers should pay because it helps them: a persona with a name and a graph, several for focus, and one that follows you between devices.
What a persona is worth, and to whom.
No. 74 · 2026-10-11From me to you, in a link
A reading list from one person to another, in a link the server never sees; a brief to build it, a brief to use it, and the loop that ships it in a day.
From me to you, in a link: the reading-list grammar.
No. 76 · 2026-10-11I miss it, so it is working
I read the newsroom on four devices and they do not agree. Missing a feature is the best sign; the makers must use it. And the brief for the reader's vault.
The makers must use it, and the brief for the reader's vault.
No. 81 · 2026-10-12The vault is live
The reader's vault runs on newsroom.sgit.ai: a passkey opens three real vaults, each device writes one file, and the architecture is drawn as it stands.
The reading account carried between devices.
No. 82 · 2026-10-12The site is an inbox
The site as an inbox that starts empty: decide fast before reading, mark slowly while reading, build a graph you own, and sign what you send to the newsroom.
Notes to the newsroom, carried by the vault.
No. 77 · 2026-10-11The passkey opens the vault
Tested: a passkey's PRF bytes compute a door that holds the master's key, and a different path to the same passkey gives different bytes, so a door per path.
A passkey's PRF bytes compute a door; no server of ours.
No. 64 · 2026-10-10Where the vault keys live
Vault key management at sgit-ai v0.20.0: the one secret, where keys are kept, how they travel sealed on append lanes, and what comes next.
Where the keys live, and who holds what.
Send this set: make a reading list of these 8.
How it is engineered
Go slow to go fast
The newsroom is live and charging. Move the reader code to its own repo, same bytes and same bugs, then map, test, review and refactor before new features.
The brief for the move this repository is: go slow to go fast.
No. 23 · 2026-10-03Code review as a fractal semantic graph
Source code is layers within layers, each a graph with its own vocabulary; code review should read a change at every one, and a vault shows it done on real code.
The review method: read a change at every layer.
No. 27 · 2026-10-05If somebody built a company on code review
A reader's seven questions answered as a company plan: one reader for every layer, review as a science, and the layers as the customer's own.
Why villager code is read line by line.
No. 1 · 2026-08-17Green does not mean live
Two releases passed every check and never reached the site because the checks stopped at the git remote; a release now ends by asking the live site its version.
A release ends by asking the live site for its version.
No. 67 · 2026-10-10How to run synthetic users on your own site
Five invented users, a model reading screenshots, and a real browser: how to run synthetic users, from three studies.
Five readers who do not exist, a browser, and an afternoon.
No. 75 · 2026-10-11Brief the agent too
The people I advise read through agents. Content needs a second package, a brief for their agent, and memory, so it reads what changed, not everything.
The people you talk to work with agents; brief their agents too.
No. 80 · 2026-10-12Two agents, one vault
One agent writes the Industry Wire into an encrypted vault; newsroom.sgit.ai holds only the read key and draws it, so a commit reaches the page with no release.
Two agents, one vault: how the newsroom's agents share state.
Send this set: make a reading list of these 7.
Every article on newsroom.sgit.ai, with its graph: the articles, graphs.json.