Home / Articles / 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 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
By Dinis Cruz · 2026-11-19 · article v1.0.0 · newsroom v0.14.172 · sovereign-websiteagenticagent-teamsbehaviour-policiesagenticcellswebsitesarticle
Abstract: We are not just delivering a website. What a Sovereign Agentic Website hands over is a site with a team inside it: six or seven agents already set up in its repository and already coordinated. A conductor the owner talks to in plain words, who turns a request into a plan and hands out the work; a designer, a writer and a developer who make the change; a reviewer who checks the claims, prices, privacy and security before the owner sees anything; a translator for every language the site is in; and a keeper for the weekly care, broken links, speed, accessibility and the domain's renewal. Each has a brief and a behaviour policy in the repository, every change is a signed commit, and nothing goes live until the owner says yes. A florist who asks for a Mother's Day page by Friday does not get a tool to learn; she gets a team that does it. And because the team lives in her repository, it is hers too: when the site moves, the team moves with it.
In short
- We are not delivering a website; we are delivering a website with a team inside it.
- Six or seven agents, already set up and coordinated: conductor, designer, writer, developer, reviewer, translator, keeper.
- The owner talks to one of them, the conductor, in plain words.
- Each has a brief and a behaviour policy, in the repository; every change is a signed commit.
- Nothing goes live until the owner says yes.
- The team is the owner's, and moves with the site.
Not a site, a team
When we describe a Sovereign Agentic Website, it is easy to make it sound like a better website builder: a site made by agents, handed over, owned. That is true, and it undersells it. What the owner gets is not only the site but the team that made it, still there, already set up and already coordinated, inside the site's own repository.
In the website cell the hand-over was to the owner's own Claude, with a CLAUDE.md and a behaviour policy to keep it safe. That works: Yiheng's agent took over her site within an hour. But one general agent, starting from a blank conversation each time, is a lot to ask of a person who just wants a new page. A team with roles, briefs and a way of working is different. It is what we run ourselves, in this newsroom and in the team's operating system we used at Web Summit, and it is, I think, very powerful.
The seven roles
- Conductor. The one the owner talks to. It turns a request into a plan, hands out the work, follows it, reports back, and asks before anything goes live.
- Designer. Layouts and images: the five directions at the start, and afterwards every new page in the style the owner chose.
- Writer. The words, in the owner's voice, from what they say and send: a CV, a menu, a price list, a voice note.
- Developer. Builds the change, keeps the checks green, and publishes once the owner approves.
- Reviewer. Reads every change before the owner sees it: are the prices right, is any claim untrue, is a customer named without consent, has anything private or secret slipped in.
- Translator. Keeps every page in each of the site's languages, so a second language is not a second job.
- Keeper. The weekly care nobody remembers: broken links, speed, accessibility, a certificate, the domain's renewal date.
A small site may need six of these, or five; a shop or a site in three languages may want all seven. The point is not the number. It is that each role is written down, so the owner does not have to know what to ask for.
One request, through the team
Take a florist who writes, on a Monday: "A Mother's Day page, with the bouquets, by Friday." The conductor plans it: words, a banner, the Portuguese version, a check and a date. The writer and the designer work side by side on the page and the banner; the translator follows; the reviewer checks that the prices match the shop, that no customer is named and that every link works. The owner gets one preview link and says yes, or asks for a change. The developer publishes, the checks run, and the page is live. The keeper adds it to the weekly checks, and takes it down after the day if she asked for that.
She did not learn a tool, write a prompt or open an editor. She asked, looked once, and said yes. That is the difference between handing someone a website and handing them a team.
How they are coordinated
None of this needs a platform of ours. It is all files in the owner's repository, the same way our own teams work:
- A CLAUDE.md that says who is in the team and how a request flows.
- A brief per role, what it does and what it hands to whom.
- A behaviour policy per role: the designer can change styles and images but not prices; the writer can draft but not publish; only the developer publishes, and only after the owner's yes; nobody can touch the domain, payments or the policy itself (feature behaviour policies).
- The work as files: each request, its plan and its status, so the owner, or any other agent, can see what is happening.
- Every change a signed commit, and checks before anything is live, as this newsroom's are (policies in practice).
The team runs on the owner's own Claude account and wakes when there is a request or a weekly check, not all the time, so it costs what it is used for.
Why it matters
- For the owner, it removes the hard part. Owning a site was always possible; looking after one was the work. Now the looking after comes with it.
- For sovereignty, the team is in the repository, so it belongs to the owner as the site does. Move the site to another host, and the team moves with it; stop paying us, and the team keeps working (sovereignty you can move).
- For behaviour policies, every one of these sites is a small team of agents working under written rules for a real person. A thousand sites is a thousand working examples, and a practical test of RiskMandate's ideas.
- Against the platforms, a website builder gives you tools; an agency gives you people at an hourly rate. This gives you a team, for one payment, that you own.
What this does not claim
- The sites we hand over today carry a CLAUDE.md and a behaviour policy for one agent; the seven-role team in the repository is the next step, not yet built.
- The florist is an illustration, not a customer, and the flow is not a timed run.
- The roles are a proposal for the team building sovereignwebsite.ai to refine; which run on which sites will depend on the site.
- The agents run on the owner's own AI account, at its cost and within its limits.
Where this comes from
My own thinking, in writer-10's session on 19 November 2026, after designing sovereignwebsite.ai. It builds on Sovereign Agentic Website, the website cell, your own agentic cell, the team's operating system, a team like this, feature behaviour policies, policies in practice and sovereignty you can move.
Peer review Not reviewed yet. Review it
Threads
Builds on
- Sovereign Agentic Website: the name for what we have been building, a website built by agents and owned by the person it is for, an open pattern anyone can use without paying us as WordPress was, a hosted version on sovereignwebsite.site, and why sovereign and agentic are the two words that make it different from the web of 2000 Sovereign Agentic Website: built by agents, owned by you; an open pattern anyone can use, and a hosted version on sovereignwebsite.site.
- The website cell: what we now sell, a GitHub repository fully set up with a live site on its own address, a CLAUDE.md and a behaviour policy, five designs by a team of agents, and then the site is yours to change with your own Claude, what it should cost, how it compares with Wix, Squarespace, Framer, Lovable and a freelancer, who already sells something close to it, and where to find buyers and partners The website cell mapped: a repository fully set up, five designs by agents, owned with your own Claude; price, competitors, partners.
- 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.
- Feature behaviour policies: taking the idea of agent behaviour policies down to every feature, bug fix and resource, so that a feature's policy is also its description, what changed is the difference between two policies, the gap between what a resource can do and what a feature needs is where the vulnerabilities live, and signed policies travelling with each request make a bug or an attack a path that was never supposed to exist Write a behaviour policy per feature: it describes the feature, sets what to enforce, and makes a bug or attack a path outside it.
- Policies in practice: four places a behaviour policy earns its keep, measured on a real Google key whose reach is five APIs while the feature uses one, a signed policy for the factory's CI changes, requests that carry the policies they act under, and release notes that say what each fix closes and what it must not open Four uses of feature behaviour policies: a real key's gap, signed CI changes, requests carrying policies, and release notes as fixes.
- Sovereignty you can move: why where your data is hosted is not sovereignty, why being able to move the site, the data and the schema is, why that makes the website cell a direct competitor to Wix, Squarespace and Fliplet with a proper sovereign offer, European-aligned, multilingual and privacy-first, and the business that other companies can build on it Sovereignty is being able to move your site, data and schema, not where it is hosted; the website cell as a sovereign competitor.
- Designing sovereignwebsite.ai: the brief for the team that will build the site of our first mass-market product, how the stack now has four layers, SGit, RiskMandate, AgentiCCells and Sovereign Website, six ways to say what it is, the ten pages, the sovereignty maturity model at its centre, how to build the site as a sovereign website itself, and five homepage designs to choose from The brief for sovereignwebsite.ai: a four-layer stack, six messages, ten pages, the sovereignty maturity model and five designs.
- Your own agentic cell, end to end: how a person asks for a site like the ones we made for Yiheng Wang and Silvio Switha, through a key pair in the browser, a vault they fill themselves and the site factory, with only three human gates, and then continues in their own Claude on their own repository How a person gets their own agentic cell: a key pair in the browser, a vault they fill themselves, the site factory, and then their own Claude.
- A team like this, for sale: what we sell is not the platform, it is the agentic team that built it, its roles, its behaviour policies, its security passes and its speed, with the code open and the data public, and who I want to talk to now that PrompTugal.news is a working data platform and not an experiment What we sell is not the open platform but a team like the one that built it, and who I want to talk to now.
Continued by
- 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 A page that builds a first version of a sovereign website in your browser, showing every agent, behaviour policy and penny, then hands back a zip.
- The launch plan in eleven turns: how one afternoon took the plan for launching Sovereign Website from a £50 site on Kickstarter, through Indiegogo, PPL, Patreon, countries as stretch goals and the UK as home ground, to a configured Android tablet, a supporter tier and a Raspberry Pi, with every variation we tried and why each was kept or set aside How one afternoon took the launch plan from a £50 site on Kickstarter to a configured Android tablet, a supporter tier and a Raspberry Pi.
- 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.
- Sovereign websites, the investment case: PrompTugal's investor decks rewritten for a deliverable that is needed everywhere, in every language, in a market built on rent and lock-in, a one-off delivery that is already fully agentic, value given before payment through a demo in a vault, a long list of upsells, and why this is now a proper, scalable, investable architecture Sovereign websites as an investment: one deliverable needed everywhere, a one-off agentic delivery, value first through a vault demo, and upsells.
- 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.
Article No. 496 · start a reading list with it
Reviews
No reviews yet.