# Selling capabilities, not content: what changed in v1.1.0, sgit.ai > The changes to the article "Selling capabilities, not content" in v1.1.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) / [Selling capabilities, not content](../../selling-capabilities-not-content.md) / [Versions](../selling-capabilities-not-content.md) / v1.1.0 # Selling capabilities, not content: what changed in v1.1.0 From v1.0.0 (2026-11-15, `ec16a9470`) to v1.1.0 (2026-11-15, `8582b1793`), paragraph by paragraph. 3 paragraphs added, 2 removed, 2 changed in place, 30 unchanged. About 312 words added and 113 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../selling-capabilities-not-content.md) 1 unchanged paragraph Summary: Florent Daudens asks a sharp question: publishers now have the protocols, connectors, collective licences and telemetry standards, so where are the products? His answer is that "we need to move beyond licensing content and start selling capabilities", and his bet is connecting the news subscriptions people already pay for to their personal agents. I agree, and our own newsrooms point at what those capabilities can be. The Storm Charles site went from a voice brief toreached 2,618 pages in three days, every fact with its source and the time it was read: not articles, but a live, sourced picture of a crisis that people and agents could use.use, and it was possible only because of the method for running agents at scale that we had built over months before it. PrompTugal.news ran a newsroom of agent desks for Web Summit and is now going local: a site for Portugal, one for the Algarve and one for every Algarve town, each a lens on one shared semantic graph, which is a product a town, a business or an agent can use, not a stream of articles. And for Florent's open questions on access, permissions and payment, we have been building answers with keys people own, vaults opened by read keys, licences on every page, a meter that charges for what you read, and pages written for agents. This is our second reply to him. 4 unchanged paragraphs, under In short {#in-short} • **The Storm Charles site was a capability:** 2,618 pages in three days, every fact sourced and timed.timed, made possible by months of work on how we run agents. 7 unchanged paragraphs, under His question {#question}, A storm site is a capability {#storm} When Storm Charles reached Lisbon during Web Summit, I asked our agents, by voice, for a site about it. Three days later it had 2,618 pages and 1,434 versions, with desks for the weather, flights, transport and the cloud, and every fact carried its source and the time it was read ([Storm Charles, a newsroom built in a night](../../storm-charles-a-newsroom-built-in-a-night.md)). That is not content to license. It is a capability: a live, sourced picture of a situation, kept current, that a person can read and an agent can query, with the provenance to trust it. The value is not in any one article; it is in having the whole picture, now, with its sources. When Storm Charles reached Lisbon during Web Summit and the summit called off its second day, we had a new site for it the same evening, and three days later it had 2,618 pages and 1,434 versions, with desks for the weather, flights, transport and the cloud, and every fact carried its source and the time it was read ([Storm Charles, a newsroom built in a night](../../storm-charles-a-newsroom-built-in-a-night.md)). It would be easy to tell that as one request to an AI, and it would be wrong. The site could be set up that quickly only because of the work that came before it: months of building the method our agents run on. Conductors that start and brief other agents, roles with written mandates, and hand-overs when a session gets long: the storm site alone passed roles to fresh sessions 106 times. State kept in files, not in conversations. A key and an inbox lane for every agent. Release gates that refuse a page that breaks a rule. And observability and visualisation, so we could see what more than a hundred sessions were doing that day and steer them. The speed was the dividend of that structure ([the team's operating system](../../the-teams-operating-system.md), [six setups of an agentic system](../../six-setups-of-an-agentic-system.md)). What it produced is not content to license. It is a capability: a live, sourced picture of a situation, kept current, that a person can read and an agent can query, with the provenance to trust it. The value is not in any one article; it is in having the whole picture, now, with its sources. And the capability behind it, a method that can stand up a sourced newsroom on any subject in hours, is the real product. 18 unchanged paragraphs, under A newsroom by place is a product {#place}, Answers to the open questions {#answers}, What I would build next {#next}… [all versions](../selling-capabilities-not-content.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/selling-capabilities-not-content/v1.1.0.html)*