for agents/llms.txtv0.14.177

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 · 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.

A website with a team inside: a conductor and six agents in the owner's repository.

In short

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

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

One request through the team: a Mother's Day page, from the owner's words to live, with one yes.

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:

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

What this does not claim

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

Agents & policy This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 496 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.