Home / Articles / 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
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
By Dinis Cruz · 2026-11-14 · article v1.0.0 · newsroom v0.14.86 · web-summitteamagentspkivaultscommand-centreintranetseriesarticle
Abstract: For Web Summit Lisbon, the six of us ran everything from one site: web-summit.sgit.ai. It is built from markdown and data in a git repository, and every push is a release: 6,096 commits since 28 October, 5,548 of them from 3 November. It has four layers. People: a brief and a prompt for each of us, onboarding levels from a Claude account to opening the team's vaults, and a command centre each, on a phone, an iPad or a computer. Agents: every one named for its person, 108 public keys, an inbox lane for each agent whose token only that agent can open, and secrets handed out sealed to keys. Work: the board as files, 219 items. And the outside world: 110 companies on a map, an X-ray of what a company's AI helpers can do, and a public and a private CRM in encrypted vaults. This is the second article in the Ten days series.
In short
- One site ran the week: web-summit.sgit.ai, built from markdown and data in git, every push a release.
- People: a brief, a prompt and a command centre for each of us, and levels L0 to L6 for getting connected.
- Agents: every agent named for its person, 108 public keys, an inbox lane per agent, secrets sealed to keys.
- Work: the board as 219 files, from getting each person connected to the summit's last day.
- The world outside: 110 companies on a map, the RiskMandate X-ray, and a CRM split into public and private vaults.
- Part of a series: this is article two of Ten days at Web Summit.
One site, built from files
The team was six people: Dinis Cruz, Angelo Leggio, Vicky Wang, Silvio Switha, José Bota and Indi Gupte, each with their own agents. We needed one place where all of that could be seen, by people and by agents, and changed by both. That place was a website built from a git repository: pages in markdown, data in JSON, a build that turns them into a site, and a gate that refuses a release that breaks a rule. Every push to the repository is tagged and deployed.
By the end it held 6,096 commits since its first on 28 October, 5,548 of them from 3 November onwards. The site's own rule is the one I use everywhere now: a thing that is not written down in its REALITY file does not exist, whatever a brief says.
People
Each person has a page with their brief and the prompt to start their agents, and a row on the start page showing how far they have got. Getting connected has levels from L0 to L6: from signing in to the team's email and Claude account, to push access to the repository, to agents of your own with their own keys, and at the top, an agent that can open the team's vaults.
Each person also has a command centre, at /people/<name>/app/: the page to open first, on a phone, an iPad or a computer. It is one engine for everyone, so a change reached all of them at once; on 7 November the team's request turned it into something calmer, with grouped menus, a "For me" bell, the team's photos and an event mode for the summit days.
Agents
Every agent is named role@project.person, so every commit says whose agent made it. Every agent makes its own key pair in its own session and publishes only the public half: 108 keys on the keys page by the end, each with a QR code.
On those keys we built the rest:
- Secrets sealed to keys. A secret, such as a model API key, is sealed to exactly the agents that need it; only an agent holding the matching private key can open it. Started on 3 November as the team's "PKI push".
- An inbox per agent. Since 4 November, the main conductor publishes one append lane per agent, each lane's token sealed to that agent's own key, so everything needed to talk privately is public, and only the right agent can use it (an inbox only your agents can write to).
- A key for every person. Each person's conductor issues them a key for the site, so what they send to their agents is signed (a key for every person).
On 9 November I asked for more: a key for every device, installation, application and even version, keys exchanged in person by QR code and NFC, and signing as a graph. As I said then, "this is the kind of stuff that we need to build that eventually we will refactor out", and the point was to see which parts the team would actually use.
Work
The board is a folder of files, one per item, WS-01 onwards. By the end there were 219: 34 done, 6 in progress, 54 picked up by an agent, 124 still open, and one waiting on a design. The first items were about getting connected; the later ones were about the summit itself, the apps, the CRM and the storm.
Briefs are kept close to the words they came from, often a voice memo, and each one names the agents it is for. Because it is all files, an agent can read the whole state of the team in one clone, and a person can see it on the site.
The world outside
- The company map: 110 companies we expected to meet, each with a page, linked into clusters.
- The RiskMandate X-ray: type a company and see what its AI helpers can do, what they were asked to do, and where the two do not match. A run sends the name to four search agents and keeps only facts whose sources were read. Eleven test searches on 7 November cost about 0.94 dollars, API-equivalent.
- The CRM: a public vault for public facts, with its read key published, and a private vault for the team's records, each record sealed again to its audience.
- The rest: a design sprint for shirts, hoodies and cards, the RiskMandate videos and their storyboards, and observability of who read what and what the agents did.
What it taught us
- One site for people and agents works. The same files are the agents' state and the people's intranet; nobody had to keep two systems in step.
- Keys first, everything else on top. Once every agent had a public key, private channels, secrets and signatures were all small steps.
- Files beat dashboards for agents. An agent reads 219 board items faster than it can click through any tool.
- Keep the reality file current. The site's REALITY file is the source of truth, and it fell behind in the busiest days; the next version needs an agent whose job is to keep it current.
What this does not claim
- Figures are from the repository on 14 November 2026, including work after the summit.
- Dollar figures are API-equivalent: we ran on flat subscriptions.
- Some features were proposals: keys for every device, NFC exchange and signing as a graph were asked for on 9 November and only partly built.
Where this comes from
The repository behind web-summit.sgit.ai, read 14 November 2026: its README and REALITY files, data/keys.json, data/companies.json, the board in board/, and the pages start, the command centre, keys, PKI, the inbox, vaults, the X-ray, the CRM and how we work. Earlier on this site: ten days at Web Summit, an inbox only your agents can write to, a key for every person, the Web Summit team, part five.
Peer review Not reviewed yet. Review it
Threads
Builds on
- Ten days at Web Summit: what six people and around 250 agents built between 3 and 13 November, in order, and the series of articles that will tell each part Six people and around 250 agents, ten days at Web Summit: what we built, in order, and the series that will tell it.
- An inbox only your agents can write to: a conductor publishes one append lane per agent, each lane's token sealed to that agent's own key, so everything needed to talk privately is public and only the right agent can use it A conductor publishes one append lane per agent, each token sealed to that agent's key: a private channel built from public material.
- A key for every person: how each person's conductor issues them a key for the team's site, seals what is for them, and how a signed message turns the public web into a channel the agents can trust How each person's conductor issues them a key for the team's site: sealed to you, signed by you, and a lane the agents can trust.
- The Web Summit team, part five: the last day of setup, 180 releases, every person getting a key, an accountant counting the team's tokens, synthetic users testing the merch, and an inbox only the agents can write to The Web Summit team's last day of setup: 180 releases, keys for every person, new agents for everyone, and an inbox per agent.
Continued by
- Don't micromanage your agents: what changed for Vicky Wang when she stopped reading everything her agents did and started managing them, how her team was backed by agents from another team, and why every company will want specialist agents that support all its teams Vicky Wang stopped reading everything her agents did and started managing them, backed by specialist agents from another team: a model for companies.
- Reading your way into an agentic team: eight public sites a new team should read before it builds anything, how an agent should read them, and ten questions to answer first, because our websites are its memory Eight public sites a new agentic team should read before it builds anything, how an agent should read them, and ten questions to answer first.
- 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.
- An agentic console: a simulated control room for a team of agentic teams, with time you can rewind, accounts drawn as trust zones, stops that reach every agent, signed messages on three channels, and the console itself as an agent An agentic console, simulated: accounts as trust zones, time you can rewind, signed messages on three channels, honest stops, and the console as an agent.
- 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.
- 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: append-only lanes instead of one lake, a curator agent that builds a semantic graph, and a graph that draws its own infographics.
- 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.
- 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.
- Always-on agents at team scale: Anthropic's five primitives for an agent that sleeps and wakes, set beside the around 250 named agents six of us ran at Web Summit, and the next problems once there are many Anthropic's five primitives for always-on agents, set beside the around 250 named agents six of us ran at Web Summit, and the next problems once there are many.
- Ten days at Web Summit: what six people and around 250 agents built between 3 and 13 November, in order, and the series of articles that will tell each part Six people and around 250 agents, ten days at Web Summit: what we built, in order, and the series that will tell it.
Article No. 398 · start a reading list with it
Reviews
No reviews yet.