Home / Articles / The new data lake: many small append-only lanes instead of one big lake, a curator agent that turns their rows into a semantic graph, and a graph that draws its own infographics, as we ran it at Web Summit
The new data lake: many small append-only lanes instead of one big lake, a curator agent that turns their rows into a semantic graph, and a graph that draws its own infographics, as we ran it at Web Summit
By Dinis Cruz · 2026-11-15 · article v1.0.0 · newsroom v0.14.94 · data-intelligencedata-lakeknowledge-graphagentsappend-onlyinfographicsdemoarticle
Abstract: The data lake promised one place for all of a company's data, and often delivered a swamp: a lot of data, little meaning, and nobody sure where a number came from. With agents, I think the next generation looks different. Instead of one big lake, many small lanes: each source appends signed rows and never edits the past. A curator agent reads the lanes and turns rows into a semantic graph of things and links, every one pointing back at the rows it came from. And the graph draws its own pictures: the charts, maps, flows and infographics that people actually read. This is data intelligence that you can audit, and it is how we ran PrompTugal.news and the Storm Charles site in November: a researcher capturing public pages four times a day, a curator mapping them into story candidates, a graph of 877 entities, and observability appended to lanes in a vault. A working demo shows the pattern with made-up data.
In short
- The old promise: one lake for all the data; too often, a swamp nobody trusts.
- The new shape: many small append-only lanes, each source signing its rows and never editing the past.
- A curator agent turns rows into a semantic graph, every node and link pointing back at its rows.
- The graph draws its own pictures: charts, maps, flows and infographics, rebuilt at every release.
- We ran it in November, for a newsroom and a storm site.
- Try it: a working demo in a public vault, with made-up data.
The swamp problem
My friend in crypto told me how his company started: to do good analysis, they bought the data. Then they found it was too expensive, and built their own infrastructure. That is a common path, and it often ends in the same place as the classic data lake: a great deal of data, and very little meaning.
The problem is not storage. It is that nobody can say, for a given number, where it came from, when, and who changed it. An agent makes this worse if it reads a swamp, and better if it helps build something you can audit.
Lanes, not a lake
The first change is to stop pouring everything into one place. Each source gets its own lane: the news a researcher agent captured, the prices a pricing agent read, the orders, the support tickets. A lane is append-only: a source adds rows and never edits or deletes the past. Each row is signed, so you know which agent wrote it.
We use this pattern everywhere. Every agent on the Web Summit team had its own lane; PrompTugal.news appended reader counts and agent runs to lanes in an encrypted vault, read in the browser with a published key. Its own page is honest about the weakness, and I like that: the lanes' tokens are public, so rows can be forged or flooded, and only a signed agent run names a key. A lane is a claim, not a fact, until something checks it.
A curator that makes a graph
The second change is who makes sense of the rows. A curator agent reads the lanes and turns rows into a semantic graph: the things that matter to this company, such as a customer, a route, a product or a competitor, and the links between them. Every node and link points back at the rows it came from, so any claim in the graph can be checked.
At PrompTugal.news, a researcher captured public pages into its vault four times a day, and a curator mapped them: 104 captures, grouped by beat, into 64 story candidates, from which journalists wrote 73 articles. The newsroom's graph held 877 entities and 1,026 edges by 15 November, drawn again at every release (PrompTugal.news, the newsroom we ran).
A graph that draws its own pictures
The third change is the last mile. People do not read graphs; they read pictures. So the graph draws them: a chart of what was mentioned this week, a map of where the late deliveries are, a flow of how a story moved, an infographic for the board. They are rebuilt from the graph at every release, so they are never older than the data.
That is how the Storm Charles site grew to 2,618 pages in three days, each with its source and the time it was read, and how every figure in this newsroom is made: from data, by code, and checked.
Insight, with its evidence
An insight is a claim with its evidence: late deliveries cluster on one route, and the road news names the same route; a customer's orders fell after a competitor's cheaper list. Because every link in the graph points at its rows, the insight can show its working, and a person can decide whether to act on it.
This is where the data lake and the company brain meet. The lanes and the graph are the brain's memory; the insights are what it says when you ask (a brain you arrive at).
Try the demo
The demo's second tab has four made-up lanes, news, prices, orders and support. Click a lane to see its rows, watch the curator turn them into a graph, and read the chart and the insights it drew, each tagged with the lanes it came from.
What this does not claim
- The demo's lanes, rows and numbers are made up.
- The PrompTugal.news and Storm Charles figures are ours, from their repositories in November 2026.
- A signed row proves who wrote it, not that it is true; that is what the curator and the reviewers are for.
Where this comes from
A conversation with a friend in crypto, 15 November 2026; the PrompTugal.news repository and its live newsroom and observability pages, read 15 November 2026; the Storm Charles repository. Earlier on this site: PrompTugal.news, the newsroom we ran, Storm Charles, a newsroom built in a night, the team's operating system, and the two companion articles, a brain you arrive at and a market for sweets.
Peer review Not reviewed yet. Review it
Threads
Builds on
- PrompTugal.news, the newsroom we ran at Web Summit: desks of agents that captured, mapped, wrote and reviewed 73 signed articles in ten days, an accountant that counted every run, and fifty outreach drafts that no agent was allowed to send PrompTugal.news: 73 signed articles in ten days from desks of agents, a reviewer for every draft, and fifty outreach drafts no agent could send.
- Storm Charles, a newsroom built in a night: one person, about thirty agents and a weather face over a data room, where every figure carries its source, the time it was read, and whether it is a fact, evidence or our hypothesis Storm Charles: about thirty agents built a weather face over a data room in a night, every figure sourced, timed and labelled.
- A brain you arrive at: a company brain for information, decisions and insights is built for one company, one division and one team, starting with one person's and growing, and the Web Summit team already ran one A company brain is made for one company, division and team, and you arrive at it: start with a person's, then a team's. We already ran one.
- The team's operating system: web-summit.sgit.ai, the one site where six people and their agents ran Web Summit, with a brief and a command centre for each person, a key and an inbox for each agent, the board as files, and the outside world on a map web-summit.sgit.ai: one site where six people and their agents ran Web Summit, in four layers built on git.
- A market for sweets: the opposite of a market for lemons, a semantic graph for one financial decision that gives the buyer the evidence, an agent that gathers and weighs but never trades, and the judo move of leaving the trade to others The opposite of a market for lemons: a semantic graph for one financial decision, an agent that gathers but never trades, and the person decides.
Continued by
- A hub for agentic sites: every site AgentiCCells builds in a repository and an sgit vault, served at its own address, and listed on hub.agenticcells.site, where it can be found, promoted and copied as a template; with an orange grower as the first example hub.agenticcells.site: every agentic site in a repository and an sgit vault, served at its own address, found, promoted and copied as a template.
- Starting AgentiCCells: a company that sets up small agentic teams, cells, in the customer's own environment, with a control centre, everything open and no state on our side; how it was named, researched, reviewed and set up in a day AgentiCCells: a new company that sets up small agentic teams in the customer's environment, with a control centre, all open, no state on our side.
- Selling mini agentic teams: a business that sets up small agentic teams for companies, sized from one agent to a network, with a control centre to see them and to start and stop them, PrompTugal as the first customer and Agent Behaviour Policies as the most demanding version A business that sets up small agentic teams for companies, with a control centre to start and stop them; PrompTugal first, ABPs on steroids.
- Decide, then buy: deciding what to buy and buying it are two different businesses, one for explorers and villagers and one for town planners, and an open path with a better deal beats locking the customer in Deciding what to buy and buying it are two businesses: custom explorer work and commodity town planner work. Give an open path and a better deal.
- A market for sweets: the opposite of a market for lemons, a semantic graph for one financial decision that gives the buyer the evidence, an agent that gathers and weighs but never trades, and the judo move of leaving the trade to others The opposite of a market for lemons: a semantic graph for one financial decision, an agent that gathers but never trades, and the person decides.
- A brain you arrive at: a company brain for information, decisions and insights is built for one company, one division and one team, starting with one person's and growing, and the Web Summit team already ran one A company brain is made for one company, division and team, and you arrive at it: start with a person's, then a team's. We already ran one.
Article No. 405 · start a reading list with it
Reviews
No reviews yet.