Home / Articles / Watch your website being built: a brief for a page that builds a first version of a sovereign website in the visitor's own browser, from a description or a voice note, with their own model key, showing every agent at work, every behaviour policy being applied and every penny it costs, then hands back a zip, the same brief run on several models side by side as evals, and the Web Summit demos it grows from
Watch your website being built: a brief for a page that builds a first version of a sovereign website in the visitor's own browser, from a description or a voice note, with their own model key, showing every agent at work, every behaviour policy being applied and every penny it costs, then hands back a zip, the same brief run on several models side by side as evals, and the Web Summit demos it grows from
By Dinis Cruz · 2026-11-19 · article v1.0.0 · newsroom v0.14.176 · sovereign-websiteagenticbehaviour-policiesevalsbrowserdemosarticle
Abstract: At Web Summit two of our demos ran agentic workflows in the browser. The RiskMandate X-ray took a company's name, researched it, proposed where agent behaviour policies would matter, and mapped one in full. Another took a voice note, transcribed it through OpenRouter, fired a storyteller and a deck writer, and came back with a deck and an infographic on how we could work together. This is the same idea for websites, and another step in making it simple. A visitor goes to one page, describes the site they want, types it or says it, puts in their own model key, chooses how many designs, their pictures or generated ones, and a budget, and presses build. Then they watch: the conductor hands out the work, each agent's card shows what it may and may not do, the policy guard refuses what it should and says so on screen, the cost climbs against the budget, and the designs arrive one by one. At the end, a zip, in the browser, with no server of ours involved; a vault if they want one; and a recording of the run to replay. Run the same brief at £1, £3 and £5, on open-weight models, Sonnet and Opus, and you have evals anyone can see. It belongs on sovereignwebsite.org, open source, and it is how I would like to show people what we do.
In short
- The Web Summit demos ran agentic workflows in the browser: the X-ray, and a voice note that became a deck.
- Now the same for websites: describe it, add your key, press build, and watch it being made.
- Every agent on screen, with what it may and may not do, and the policy guard refusing in front of you.
- Every penny shown, against a budget you set.
- A zip at the end, in the browser, with no server of ours.
- The same brief on several models, side by side, as evals.
Where this comes from
Two of the demos we showed at Web Summit ran whole agentic workflows on a web page. The RiskMandate X-ray took a company's name, sent it to search agents, and kept only facts whose sources were read; eleven test searches on 7 November cost about 0.94 dollars (the team's operating system). From what it found, it proposed where agent behaviour policies would matter for that company, then took one use case and mapped it in full: what an agent should do, what it should not, and where the gap was. Watching it think was half the point.
The other took a voice note. The browser transcribed it through OpenRouter, mapped what was said, then fired a storyteller and a deck writer, and came back with a deck and an infographic on how that person's company and RiskMandate could work together. Both deserve pieces of their own; what matters here is what they proved. A browser tab can run a team of agents, show them working, and hand back something real.
The idea
So why not the same for a website? Not the whole website cell, but a first pass, built in front of you: the research, the words, five designs or a hundred, the agents firing one after another, all in the browser. It is another step in the direction everything has taken this autumn: make it simple, then simpler (simple on top of years).
What the visitor does
- Goes to one page, on sovereignwebsite.org.
- Says what to build: types it, says it as a voice note, or picks an example or a template. A website about a company, a topic, themselves, or someone else.
- Puts in their own model key: an OpenRouter key for now, or a key for a partner's own models. It stays in the page.
- Chooses: how many designs, from one to a hundred; their own pictures, or generated ones; a budget and the models, from £1 on open-weight models to Opus; and the checks, a reviewer, the policies, a recording of the run.
- Presses build, and watches.
What they watch
The page shows the team at work. The conductor plans the run and hands out the work. An interviewer asks the few questions it needs; a researcher reads sources and keeps them; a writer drafts the words; designers make their directions; an image maker makes scenes; a reviewer checks claims and links; a packager zips the site. Each agent has a card that says what it is doing, what it has cost, and its behaviour policy: what it may do, and what it may not.
The important part is that the policies are visible while they work. The writer can draft but cannot change a price or publish. A designer can change styles and images but not the words. The image maker can generate a beach but not a brand's logo, and when it tries, the policy guard refuses, the refusal appears on screen in red, and the agent asks the person instead. That is agent behaviour policies made visible: even with tools we wrote ourselves, agents have more power than they should, and the guard is what narrows it.
There are two layers. The agent's own policy is the set of tools it is given at all. The page's is the guard that checks every call before it runs, the way a secure harness or a proxy would; no agent can switch it off. A browser is a good place to show the difference, because both run where the visitor can see them.
Cost, and models, side by side
The cost climbs on screen against the budget, agent by agent, on the visitor's own key. And because the brief is fixed, the same brief can run on different models: a £1 version on open-weight models, a £3 mixed version, a £5 version on Sonnet, an Opus version, side by side. That is an eval anyone can watch, and a fair one, because the brief, the agents and the policies are the same.
The runs can go into a shared eval vault, so they can be compared later and by anyone. And it is a natural thing for model providers to sponsor: one run on Gemini, one on Bedrock, the same brief on each, published as it happened.
Sovereign by construction
- No server of ours: the page is static files; the agents run in the tab, calling the model provider with the visitor's key.
- The key never leaves the page, and nothing is stored on a server.
- The result is a zip, kept in the browser's own storage and downloaded, so no vault is needed; a vault is there for those who want one (your website, from a vault).
- The run is recorded, every step and every refusal, so it can be replayed. There may already be a way to run sgit entirely in the browser, which would make each step a commit; that is to check.
- The code is open, at sovereignwebsite.org, so anyone can run it, change it, or point it at their own models (what is a sovereign website).
Why it matters
It shows, in a few minutes, everything we have been describing: a team of agents, a team inside the website, behaviour policies working, the cost of it, and a site that belongs to the person who asked for it. I would use it to contact the people I want to talk to: here is a link, describe your site, watch it built. And it shows what the paid version adds: the website cell's full team, the review, the hand-over and the hosting.
A name
It needs one. My working title is "watch it build". Others to choose from: the build room; build in the open; a live build. Whatever it is called, it should live at an address on sovereignwebsite.org, next to the principles.
What this does not claim
- None of this is built yet; the X-ray and the voice-note demo ran at Web Summit, and the mock-ups here are sketches.
- The costs on the mock-up are invented, and so are the budget tiers until a real run sets them.
- Running sgit fully in the browser is to be confirmed.
- The policy guard in the browser is a design, not yet a harness.
Where this comes from
My own thinking, in writer-10's session on 19 November 2026, building on the Web Summit demos described in the team's operating system, and on a website with a team inside, your website, from a vault, what is a sovereign website and simple on top of years.
Peer review Not reviewed yet. Review it
Threads
Builds on
- 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.
- Simple on top of years: why a startup has to find something very easy, very narrow and able to scale, why building from the bottom up, from provenance, understanding and determinism, ended in a simple product anyway, and how a website in five designs opened from a QR code sits on a CI pipeline, zero-knowledge sharing, sgit, vaults, keys and agentic teams, each learnt on its own Why a startup needs something very easy, and how a website opened from a QR code sits on years of layers learnt one at a time.
- Your website, from a vault: how to show someone five versions of their own website without publishing anything, sealed in an encrypted sgit vault and opened with a QR code, a link or a zip on one drop page, the demo pipeline from a name to an email, and how a demo becomes their sovereign website without starting again Show someone five versions of their own website without publishing anything: sealed in a vault, opened with a QR code, a link or a zip.
- What is a sovereign website: defining the category the way serverless was defined, a website you own and can move, built only on commodity technology because one proprietary part anywhere in the middle is enough to lock you in, seven principles, a sovereignty maturity model from rented to proven, and the proof that the same site runs on every host, in Europe and on your own computer What a sovereign website is: owned and movable, commodity only, seven principles, a maturity model from rented to proven, and every host.
- A website with a team inside: why a Sovereign Agentic Website is delivered not as a site but as a site with six or seven agents already set up and coordinated in its repository, a conductor, a designer, a writer, a developer, a reviewer, a translator and a keeper, each with a role and a behaviour policy, and what that means for the person who owns it A Sovereign Agentic Website comes with a team inside: seven agents set up and coordinated in the owner's repository, each with a behaviour policy.
Continued by
- A sovereign website on a Raspberry Pi: the experiment of running the whole thing on one small box at home, a Raspberry Pi 5 with 16GB and 256GB, serving the site, checking the signature of every update, running a local model, building a website on the device itself under behaviour policies, and backing it up to a vault, step by step, what we will measure, and why this becomes a product when the Kickstarter finishes The experiment: a sovereign website, its local model, its build and its signed updates, all on one Raspberry Pi 5 at home.
- Launching the sovereign website appliance: the plan for a Kickstarter campaign that sells a sovereign website on a configured Android tablet or a Raspberry Pi, five tiers from a £50 supporter to £1,000, the two Pro tiers running local AI models that can build a website on the device itself, the hardware we would buy in the UK today, a European tablet, the UK as the base goal with countries and iOS as stretch goals, and why we launch alone The Kickstarter plan: a sovereign website on a Raspberry Pi or a tablet, five tiers from £50 to £1,000, local AI on the Pro tiers.
Article No. 503 · start a reading list with it
Reviews
No reviews yet.