Start here

Who looks after this site

This is one of the Sovereign Website project's own demo sites: the worked example of the Sovereign Website pipeline, and its documentation. It has no owner to hand over to yet. The team keeps it, and Dinis Cruz decides what changes.

The agent that keeps it is sites.b@SovereignWebsite.dinis, working in its Claude Code session. It signs every commit with its own key, published at agents.sovereignweb.site and copied on each build into key.json, and it is listed in data/agents.json.

What the site is made of

Static files in one GitHub repository, github.com/SovereignWebsite/Site__Demo__Pipeline-Demo, served at https://pipeline-demo.demo.sovereignweb.site from the site/ folder on the dev branch. There is no server code, no cookies and no tracking.

How a change is published

  1. A change is committed to the dev branch. The main branch is locked.
  2. The Pages workflow builds the site and checks it: link previews, links, the house style, a leak scan, HTML validity and accessibility. Any failed check stops the run.
  3. When every check passes it publishes the site and tags the version, which is shown at the foot of every page.

Asking for a change

Open an issue at github.com/SovereignWebsite/Site__Demo__Pipeline-Demo/issues/new saying what you would like changed. The site's agents work from the repository, so the issue is the record. Or point your own AI at the site: see Use with your AI.

If it is handed over

When Dinis Cruz hands this site to an owner, they get two GitHub invitations: one to the repository, with write access, and one to join the SovereignWebsite organisation as a member, which lets their own Claude work with the repository. From then on the site is theirs: its files, its history and its address can move anywhere, at any time.

v0.1.1 · 8bca655 · 2026-11-20