for agents/llms.txtv0.14.177

Home / Articles / 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

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

By · 2026-11-19 · article v1.0.0 · newsroom v0.14.171 · sovereign-websitedesignbriefagenticcellsriskmandatesgitarticle

Abstract: Sovereign Website is our first mass-market product, and its site, sovereignwebsite.ai, is next. This is the brief for the team that builds it, written in public so that the agents and the people can work from the same page. It starts with how everything we have talked about now stacks up: SGit for encrypted, versioned vaults; RiskMandate for the behaviour policies that bound what agents do; AgentiCCells for agentic teams; and on top, Sovereign Website, the first layer a small business can buy without knowing the others exist. Then six ways to say what it is, from "Built by agents, owned by you" to "Where is your website, from 0 to 5?". Then the ten pages of the first version, with a sovereignty maturity model from level 0, rented, to level 5, sovereign and proven, at the centre, and a one-minute self-check. Then how to build the site: as a sovereign website itself, in the SovereignWebsite organisation, five designs by a design agent, every claim on it true of the site. And five homepage designs, as every site we make starts with five.

Our stack with a new layer on top: SGit, RiskMandate, AgentiCCells, and Sovereign Website.

In short

A new layer on the stack

Everything we have built this autumn now stacks up, and it helps to see it in one picture:

Each layer is open and builds on the one below. What changes with the top one is the market. Sovereign Website is the first thing we make that a florist, a bakery or a surf school can buy without knowing the other three exist. That makes it our first mass-market product, and its site has to work for them first.

Six ways to say it

We should test these, not pick one on instinct:

  1. "Your website. Built by agents, owned by you." The plain promise, for a small business.
  2. "Where is your website, from 0 to 5?" The maturity model as a question; it invites a check.
  3. "A website under your own roof." The European message: your files, your domain, your host.
  4. "Five designs. Pick one. It is yours." Show, then own; it leads with design.
  5. "Stop renting your website." The challenge to the platforms, from the pitch.
  6. "Websites built by agents and owned by the people they are for." For the people who will use and build on the open pattern.

The ten pages

The ten pages proposed for the first version of sovereignwebsite.ai.

The first version needs ten pages: a home page with one promise and one action; how it works, from the interview to five designs, the handover, changing it by talking and moving it; the maturity model, with a self-check; examples, real sites each shown with its level; prices; moving your site from Wix, Squarespace or WordPress; owning your domain (your own registrar); the open pattern; partners; and trust, which shows the behaviour policy and the signed commits behind the site.

The maturity model at the centre

The idea I like most for the site is the sovereignty maturity model, and it should sit at its centre. It has six levels. 0, rented: a hosted builder decides everything. 1, exportable: your words leave, the design stays. 2, a part you do not control: open software held by one paid plugin, theme or agency component. 3, open, on one host: open code tied to one host's features. 4, portable: plain files, open tools, your domain. 5, sovereign and proven: portable, and deployed on more than one host.

On the site it becomes a one-minute self-check: five questions about where your domain is registered, whether you can export your site, what it depends on, and where it runs, and an answer from 0 to 5 with what it would take to move up. It gives a visitor a reason to engage before they are asked to buy, and it explains the product better than any feature list.

How to build it

The site has to be what it sells. That means:

The full pipeline will not be wired on day one, and it does not need to be. The team can work end to end by hand first, and I will wire the flow once the steps are proven.

Five homepage designs

Design 1, the plain promise: built by agents, owned by you, and the launch offer.
Design 2, the maturity model as the question: where is your website, from 0 to 5?
Design 3, the European message: a website under your own roof.
Design 4, show then own: five designs, pick one, it is yours.
Design 5, the open pattern, for the people who will build on it.

Five directions, as every site we make starts with five. They are sketches to react to, not finished designs: the real ones should be made by the design agent from these directions, with real photographs and real example sites in place of the blocks of colour. My own instinct is to combine 1 and 2: the plain promise above, and the maturity model and its self-check immediately below.

What I am asking the team

Set up a team to build sovereignwebsite.ai from this brief: a conductor, a designer, a writer, a developer, and a reviewer for security and for the claims. Start from the ten pages, the six messages and the five directions; propose back what is missing; and build it end to end, by hand where the pipeline is not ready. Every site we make should look very good, and this one most of all, because it is the one that sells the rest.

What this does not claim

Where this comes from

My own thinking, in writer-10's session on 19 November 2026, building on Sovereign Agentic Website, the sovereign website, the pitch, the website cell, your own registrar, the cell is the unit, sgit is a standard and feature behaviour policies.

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