pipeline-demo.sovereignweb.site
A site from one request
This site is the worked example of the Sovereign Website pipeline, and its documentation. It was made from one small file, a request, and everything after that was done by the pipeline: a repository, an address, HTTPS, and a first page.
The path of one request
- A request folder.
requests/<date>__<label>/site.jsonin the Factory names the site: its label, title, description and kind. It reaches the dev branch only with Dinis Cruz's merge. - Checks. Every push to dev runs the tests, the policy validation, a leak scan, the signed-commit check and a dry plan of the organisation against the policy.
- Org apply. A push to dev that changes
requests/runs Org apply (it also runs every hour). It creates the repositorySite__<label>from the site template, with Pages on, the custom domain, the agents' team with push, and two rulesets: main is locked, dev is safe. - DNS apply. The same push runs DNS apply, which writes a CNAME for
<label>.sovereignwebsite.sitein Route 53, through a short-lived AWS role and no stored keys. - HTTPS. GitHub issues a certificate for the address; the hourly Org apply then enforces HTTPS.
- Publish. In the new repository, every push to dev deploys the
site/folder to GitHub Pages.
This site, as it happened
| When (UTC, 20 Nov 2026) | What |
|---|---|
| about 08:40 | Dinis said yes to pipeline-demo.sovereignwebsite.site. |
| 09:14:09 | The request requests/2026-11-20__pipeline-demo reached dev. |
| 09:14:52 | Org apply created the repository, 43 seconds later. |
| 09:14:59 | Org apply seeded the first four files: this page, its address, the Pages workflow and the agents' rules. |
| by 10:20 | Served over HTTPS; plain http answers with a permanent redirect. |
What the owner holds
The site is static files in a repository. Its files, its history and its address can move anywhere, at any time. There is no server code, no cookies and no tracking. The pipeline never deletes: a request removed from the Factory leaves its repository and address in place, to be retired by hand.
Who does what
Agents do the work and people decide. Each agent signs every commit with its own published key and names its session; the Factory's Agent Behaviour Policy lists what each agent may change, and anything not listed is refused. Changes reach main only when Dinis merges them.
This page is design 1 of five. See all five.