Proposed principles ยท first draft

A sovereign website is a website you own and can move.

This is the home of the principles that define a sovereign website, the maturity model that says how far a site has come, and the open pattern for building one with agents. All of it is open for comment, so anyone can test a site against it.

Moving is the hard part. One proprietary part in the middle, however small, is enough to lock a site in: nobody can move it for you without rebuilding that part, so you cannot even pay your way out.

Seven principles

A website is sovereign when:

  1. You own it. Repository and domain in your name.
  2. You can move it. Any commodity host that serves files, without changes.
  3. Nothing in the middle is proprietary. However small.
  4. Its content and schema are open. Readable without the tool that made them.
  5. Anyone can change it. You, any developer, or your own AI.
  6. What works on it is bounded. By a behaviour policy.
  7. It is proven, not claimed. Deployed, regularly, on more than one host.

The principles, and how to test a site against each one

Where is your website, from 0 to 5?

Sovereignty is not yes or no; it is how far you can move, on your terms.

  1. Rented. A hosted builder decides everything.
  2. Exportable. Your words leave; the design stays.
  3. A part you do not control. Open software, held by one paid component.
  4. Open, on one host. Tied to one host's features.
  5. Portable. Plain files, open tools, your domain.
  6. Sovereign and proven. Deployed on many hosts.

The maturity model, and what each level requires

Proposed, first draft. Written by Dinis Cruz to be argued with and improved. Copy them, adapt them and test any site against them, with credit. The proof that principle seven asks for, one commit deployed by one pipeline to many hosts, does not exist yet.

Sovereign is what it is; agentic is how we build it

A sovereign website could be made by hand. A Sovereign Agentic Website is one built by agents and owned by the person it is for: the files, the schema, the history and the address, in a repository they control, changed by talking to their own AI, and movable anywhere.

Like WordPress, anyone can use the pattern without paying us. That is the point: a site you own should not depend on us existing.

The pattern: what it is made of

A sovereign agentic website is a pattern before it is a product. It is one repository, holding six things:

  1. A repository the owner controlsEvery change is a commit, and every version can be restored.
  2. The site as plain filesStatic: no server code, no database, no plugins, no cookies unless the owner adds them.
  3. Content and schemaThe structure of the site and its content, as files in open formats.
  4. CLAUDE.md for the agentsWhat the site is, how to change it, the checks, and what not to touch.
  5. A behaviour policyWhat any agent working on the site may and may not do.
  6. Checks and a deployRun before anything goes live, onto any static host.

Read the pattern in full

Why these two words

Sovereign

Sovereignty is not where your data is hosted, but whether you can move it: your site, its data and its schema, to anywhere else, on your own terms. The definition, and the four tests, which the seven principles now carry further.

Agentic

In 2000 the open web gave you software to run yourself; WordPress made publishing free, but you or someone you paid still did the work. Now a team of agents does the work: it interviews you, builds the site, shows you designs, and afterwards your own AI changes it when you ask. The agents work inside a behaviour policy that says what they may and may not touch, so the site stays yours while they work on it.

Open, and also hosted

This site, sovereignwebsite.org, is the home of the principles and the open pattern. The pattern's repository is still to be set up, in the open, in the SovereignWebsite organisation on GitHub.

For people who would rather not do the work themselves, a hosted version is being prepared: the repository and the site set up for you, the agents build it, and it is served at its own address until you point your own domain at it. See sovereignwebsite.ai. Hosted or not, it is the same kind of thing: a repository its owner controls, and can take anywhere.

What this does not claim

  • The principles and the maturity model are a proposal, first draft, not a standard.
  • The every-host pipeline does not exist yet; only GitHub Pages is in use today.
  • The pattern's repository does not exist yet; it will be set up in the open.
  • The hosted version under this name is not running yet.
  • Sovereign, here, means owning and being able to move. It is not a legal or certification claim.