The future of news: the desk

For editors, journalists and publishers asking how news gets paid for when agents do the reading.

24 articles on this desk, 10 more that touch it. Placed by rule from the subjects and topics of each article (articles/find.json); the editor can override a call, and says why.

Start here

Three pieces, in order, for a first visit to this desk.

The future of news is the story vault, not the paywall 2026-09-22 · 35 min · Analysis
The founding argument: the story is a graph of claims and evidence, and the article is one view of it.
The reader was always the product: a corrected history of how news got into this mess 2026-09-29 · 19 min · Analysis
The history behind it: the reader was always the product, from 1833 to AI taking the traffic.
The bridge, followed to the end: what one local story is worth when it is kept as a graph 2026-10-07 · 17 min · Analysis
The idea made concrete on one local story, followed to the end and paid back to its sources.
A meter in the browser: a penny a page, a history you keep, and a site that picks for you 2026-10-10 · 5 min · Field report
The newsroom tries it on itself: a penny a page, from credit kept in your browser.
The agent is the reader: why agents will pay for graphs, personas and signed claims, because it is cheaper than not paying 2026-10-11 · 19 min · Analysis
Where the argument lands on 11 October: agents will pay to read, because it is cheaper than not paying.

Series

Two or more articles that tell one story in order.

The reading meter · 5 parts · 55 min

Five pieces from one afternoon, 10 October: the meter ships, goes live, is attacked on paper, earns its keep and becomes a business model.

A meter in the browser: a penny a page, a history you keep, and a site that picks for you 2026-10-10 · 5 min · Field report
The meter itself: a penny a page from £5 of credit kept in your browser.
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 2026-10-10 · 13 min · Field report
Going live: below zero allowed, Stripe top-ups, and the numbers to check in eight weeks.
Who will game the reading meter? Eight kinds of reader, nine ways to cheat, and the risks that will actually happen 2026-10-10 · 10 min · Analysis
The threat model: eight kinds of reader and nine ways to cheat.
Pay to keep your persona: readers should pay because it helps them, not because they feel they should 2026-10-10 · 9 min · Analysis
Why a reader would pay: a persona that helps them.
Pay after you read: how a reading meter became a working business model in one afternoon, one release at a time 2026-10-10 · 18 min · Field report
The model that came out of it: pay after you read, and the rating sets the price.

Local news, kept as evidence · 4 parts · 72 min

The story vault as an idea, two readers' tools on top of it, a bridge followed to the end, and a hospital outage kept while it happened.

The future of news is the story vault, not the paywall 2026-09-22 · 35 min · Analysis
The idea: sell the story vault, not the paywall.
Story vault underneath, Reader Skills on top: why local journalism has the most to gain 2026-10-07 · 10 min · Answer
Reader Skills on top of the vault, and why local news gains most.
The bridge, followed to the end: what one local story is worth when it is kept as a graph 2026-10-07 · 17 min · Analysis
A bridge closure simulated end to end on a story vault.
The waiting room knew first: a live local story, and the gap where local information used to be 2026-10-08 · 10 min · Field report
A live local story, kept as evidence while it was happening.

Who pays for news when agents read it · 3 parts · 61 min

From the story vault to the token bill to a corrected history, and the case that agents will pay.

Sixteen thousand fetches, ten clicks, and a token bill nobody is sending: the case for paying publishers to be easy to read 2026-09-28 · 23 min · Analysis
The token bill: publishers who are easy to read should get a share.
The reader was always the product: a corrected history of how news got into this mess 2026-09-29 · 19 min · Analysis
The history: the reader was always the product.
The agent is the reader: why agents will pay for graphs, personas and signed claims, because it is cheaper than not paying 2026-10-11 · 19 min · Analysis
The answer: agents pay because it is cheaper than not paying.

Every article on this desk

The wire as a graph: start from what the reader sees, give every story and every name a long-lived ID, link every phrase of a short narrative, and a brief for the desks 2026-10-14 · 10 min · Analysis
Design the wire from what the reader sees: every name a link with a long-lived ID, every sentence a claim, stories of stories, folders by gravity.
Dark mode, and four more: five themes for the newsroom, chosen once and kept in your browser 2026-10-13 · 14 min · Analysis
Five themes behind one pill in the bar, kept in the reader's browser, built as a layer over a stylesheet this site cannot edit, with colour as a token and a test.
Ways to read one article: the finished piece stays at the centre, and the reader picks the way in 2026-10-12 · 10 min · Analysis
The five readers' views arrived as folds inside the long piece; now the reader picks the way in, with a default, and the finished article stays at the centre.
Firing journalists is the worst thing a publication can do: what a hiring decision says about where a publisher is going, and who to hire instead 2026-10-12 · 10 min · Analysis
A hiring decision is a direction of travel: fire the journalists and the centre of gravity moves to packaging, where the metric makes clickbait by construction.
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 2026-10-12 · 13 min · Analysis
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.
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 2026-10-12 · 16 min · Analysis
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.
The article remains a product: Jonathan Palmer's four outputs for a newsroom with no human readers, checked against one that runs 2026-10-11 · 15 min · Answer
Jonathan Palmer's four outputs for a newsroom with no human readers, quoted line by line and checked against newsroom.sgit.ai as it runs, screenshots included.
Brief the agent too: the people I talk to work with agents, so what I send has to reach both 2026-10-11 · 10 min · Analysis
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.
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 2026-10-11 · 13 min · Analysis
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.
The agent is the reader: why agents will pay for graphs, personas and signed claims, because it is cheaper than not paying 2026-10-11 · 19 min · Analysis
Agents pay to read the raw web and guess its meaning. A curated graph answers for 90% fewer tokens, so paying the publisher is cheaper than not paying.
A link to a persona: send people to the newsroom as someone, not as nobody 2026-10-10 · 11 min · Analysis
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.
Pay after you read: how a reading meter became a working business model in one afternoon, one release at a time 2026-10-10 · 18 min · Field report
Seven releases in one afternoon turned the reading meter into a working model: pay after you read, and the rating sets the price.
The infographic bake-off: which image model for which job, judged blind on 10 October 2026 2026-10-10 · 8 min · Field report
Every image model on OpenRouter, eleven briefs, 101 images judged blind, $10.44: which model for which infographic, and what it costs.
Pay to keep your persona: readers should pay because it helps them, not because they feel they should 2026-10-10 · 9 min · Analysis
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.
Who will game the reading meter? Eight kinds of reader, nine ways to cheat, and the risks that will actually happen 2026-10-10 · 10 min · Analysis
Eight kinds of reader, none of them attackers, nine ways to cheat a browser meter, and the quieter risks that will actually happen.
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 2026-10-10 · 13 min · Field report
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.
One article, five readers: a librarian, a cartographer, a historian, an explainer and a storyteller read the same piece 2026-10-10 · 15 min · Explainer
Write the article first, then send five agent readers through it: a catalogue, an ontology and maps, the arc, two minutes, and a deck.
A meter in the browser: a penny a page, a history you keep, and a site that picks for you 2026-10-10 · 5 min · Field report
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 waiting room knew first: a live local story, and the gap where local information used to be 2026-10-08 · 10 min · Field report
Staff at two London hospitals said the IT was down; nothing a local could check showed it. A live local story about where local information comes from now.
Liquid content needs water: liquefy the journalist's notebook, not the finished product 2026-10-07 · 10 min · Answer
A reply to FT Strategies on liquid content: the water is the reporting, so liquefy the journalist's notebook, keep the writing theirs, and pay per use.
The bridge, followed to the end: what one local story is worth when it is kept as a graph 2026-10-07 · 17 min · Analysis
A bridge closure simulated on a story vault: newsworthy on 5 days, needed on 57, used by three readers, four buyers and an agent, and paid back to its sources.
Story vault underneath, Reader Skills on top: why local journalism has the most to gain 2026-10-07 · 10 min · Answer
Markus Franz's Reader Skills on top, the story vault underneath: each skill is a graph query, and local stories can pay back down their chain of sources.
The reader was always the product: a corrected history of how news got into this mess 2026-09-29 · 19 min · Analysis
News has sold the reader to advertisers since 1833; the web took the monopoly, the platforms made the reader measurable, and AI took the traffic.
The future of news is the story vault, not the paywall 2026-09-22 · 35 min · Analysis
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.

Also touching this desk

Placed on another desk first; this one second.

From sending a file to sgit: eight months of SG/Send, told by its own briefs and commits, and how a file-sharing service became encrypted version control and vaults on Vaults & provenance
Paying after the value: why a balance that can go negative feels different from a subscription, the psychology behind it, and the experiment this newsroom is running on Strategy & startups
The agents write too: lessons, debriefs and a page for every agent on the newsroom, and a brief for the conductor that will keep it on Building with agents
Knowledge that maintains itself: semantic graphs for an organisation's policies and internal knowledge, briefing people and agents from the graph, and vaults to carry the brief on Vaults & provenance
Every link points back: 566 links between 105 articles, 15 that point forward, and why an article should know what came next and what corrected it on Vaults & provenance
Not a straight line: working for RiskMandate by working on the newsroom, and why the thinking is never wasted on Strategy & startups
Places of highest leverage: where to focus when the agents can go in every direction, told with three days of real steps on Strategy & startups
Go slow to go fast: moving the newsroom from an explorer project to a villager one, with the brief to do it on Building with agents
How to run synthetic users on your own site: five people who do not exist, a browser, and an afternoon on Building with agents
Sixteen thousand fetches, ten clicks, and a token bill nobody is sending: the case for paying publishers to be easy to read on Vaults & provenance

Subjects on this desk

The controlled vocabulary: each subject belongs to one desk.

Micropayments and the reading meter · 12 Personas and personalisation · 18 Story vaults and liquid content · 5 Local news · 3 Journalism and the news business · 9 How this newsroom works · 34 Tokens and the agent-readable web · 9

For an agent

The The future of news desk of newsroom.sgit.ai: For editors, journalists and publishers asking how news gets paid for when agents do the reading. 24 articles placed here by rule, 3 series, three to start with. The data: https://newsroom.sgit.ai/articles/find.json (desks, vocabulary, series, formats and reading time for every article). Every desk: https://newsroom.sgit.ai/desks/index.html.