# 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, sgit.ai

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

*Source: <https://newsroom.sgit.ai/articles/designing-sovereignwebsite-ai.html> · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../index.md) / [Articles](index.md) / 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 [Dinis Cruz](https://sgit.ai/about/index.md) · 2026-11-19 · [article v1.0.0](versions/designing-sovereignwebsite-ai.md) · [newsroom v0.14.171](https://newsroom.sgit.ai/admin/versions.html) · 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

- **Four layers now:** SGit, RiskMandate, AgentiCCells, and Sovereign Website on top.
- **Sovereign Website is our first mass-market product.**
- **Six messages** to test, from "Built by agents, owned by you" to "Where is your website, from 0 to 5?".
- **Ten pages,** with the sovereignty maturity model at the centre.
- **The site is built as a sovereign website itself.**
- **Five homepage designs** to choose from.

## A new layer on the stack

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

- **SGit** is the base: encrypted, versioned vaults as an open standard, like git, where work and its history live ([sgit is a standard](sgit-is-a-standard.md)).
- **RiskMandate** is the governance: behaviour policies that say what agents may and may not do, and the gap between what they can reach and what they were asked to do ([feature behaviour policies](feature-behaviour-policies.md)).
- **AgentiCCells** sells agentic teams, cells, installed for a customer, each with a job, a deliverable and a behaviour policy ([the cell is the unit](the-cell-is-the-unit.md)).
- **Sovereign Website** is the new layer on top: a website built by agents and owned by the person it is for ([Sovereign Agentic Website](sovereign-agentic-website.md)).

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](the-pitch.md).
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](your-own-registrar.md)); 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:

- **A sovereign website itself:** a repository in the SovereignWebsite organisation on GitHub, plain files and open tools, served on GitHub Pages at sovereignwebsite.ai first, with no proprietary part in the middle.
- **Built the way the product is built:** a design agent makes five complete directions, the team picks one, and a content agent writes every page from the articles we have already published.
- **In several languages from the start,** as agenticcells.ai already is, with English and Portuguese first.
- **Every claim true of the site itself:** if a page says your site can move, this site moves; once the pipeline that deploys one commit to many hosts exists, this site is its first proof.
- **A behaviour policy for the team that builds it,** and every commit signed, as this newsroom's now are.

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

- **The designs are sketches** drawn for this brief, with placeholder colours and illustrative prices.
- **The site, the self-check and the every-host pipeline do not exist yet.**
- **The prices are the website cell's as published;** the launch offer is a proposal.

## Where this comes from

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

## Threads

Agents & policy[This article as a graph →](graphs.md#designing-sovereignwebsite-ai)

### Builds on

- [sgit is a standard, not a server: everything in a vault is one hash away, any storage can serve it, and the server is the least interesting part](sgit-is-a-standard.md) Git won as a standard, not a server. sgit is one too: every name computed from the key, a file four GETs away, any storage can serve it.
- [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](feature-behaviour-policies.md) Write a behaviour policy per feature: it describes the feature, sets what to enforce, and makes a bug or attack a path outside it.
- [The cell is the unit: positioning AgentiCCells around small, focused cells, each with an objective, a deliverable and a behaviour policy, each with a page that sells it, a free recipe and three ways to get help, a catalogue that grows one need at a time, in each industry's own words, and why we should run our own work in cells first](the-cell-is-the-unit.md) The cell is the unit of AgentiCCells: one focused job with an objective, a deliverable and a behaviour policy, each with a page that sells it.
- [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.md) Sovereign Agentic Website: built by agents, owned by you; an open pattern anyone can use, and a hosted version on sovereignwebsite.site.
- [The pitch: a site that looks better, that you own, that nobody can lock you into, that has almost nothing to attack, that costs once instead of every month, and that you change by talking to Claude, six promises, the proof behind each, and three designs for a site built on nothing else, "six promises", "just say it" and "stop renting your website"](the-pitch.md) A site that looks better, that you own, that nobody can lock you into: six promises, their proof, and three designs built on the pitch.
- [Your own registrar: which domain registrar to recommend to a small business in Europe taking its website's domain into its own name, sixteen compared on price and renewal, .eu, .pt and .ai, privacy, and APIs safe enough to hand to an agent, why AWS now sells .ai but is still a heavy choice, and the three we would put forward](your-own-registrar.md) Which registrar a small business in Europe should hold its own domain at: sixteen compared, and OVHcloud, Hostinger and INWX.
- [The sovereign website: a pivot brief for agenticcells.ai, what the site says today and what it should say next, sovereignty as the headline, a website you own, control, change and can run anywhere, the deliverables explained, the infographics to draw, five homepage designs to choose from, and the partner programme and examples that already prove it](the-sovereign-website.md) A pivot brief for agenticcells.ai: lead with sovereignty, show the deliverables, draw the infographics, and make five homepage designs.
- [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.md) The website cell mapped: a repository fully set up, five designs by agents, owned with your own Claude; price, competitors, partners.

### Continued by

- [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](the-launch-plan-in-eleven-turns.md) 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.
- [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-the-investment-case.md) Sovereign websites as an investment: one deliverable needed everywhere, a one-off agentic delivery, value first through a vault demo, and upsells.
- [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.md) 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.

[All articles](index.md) · [All graphs](graphs.md)

Article No. 495 · [start a reading list with it](https://newsroom.sgit.ai/for/make.html#r=495)

**Posting this article on LinkedIn?** The cover is [designing-sovereignwebsite-ai.jpg](banners/designing-sovereignwebsite-ai.jpg) (1920×1080, title and key ideas on it). Upload it as the article cover, paste the title, then select and copy the body from this page.

**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 →](../subscribe/index.md)

[← All articles](index.md)


---

*[Site index for agents](../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/designing-sovereignwebsite-ai.html)*
