Get started
How anyone could start, today.
To be plain about where things are: the pattern's repository is still to be set up, in the open, in the SovereignWebsite organisation on GitHub. There is no finished template to copy yet.
What there is: a clear description of the parts (the pattern), and a working example of an agent pipeline held to a behaviour policy. Here is how you could start from those.
Six steps
- Make a repository you control. On your own account, not someone else's. Everything else goes in it.
- Put the site in it as plain files. Static HTML and CSS, no server code, no database, no cookies unless you choose to add them.
- Keep content and structure as files. In open formats your own AI can read and change, so you own the schema as well as the pages.
- Write a
CLAUDE.md. What the site is, how to change words and photos, which checks run, and what not to touch. - Write a behaviour policy. What any agent may change, and what it may never do. Anything not listed is refused.
- Add checks and a deploy. A build, validation and a leak scan on every change, then publish the files to any static host. GitHub Pages serves a static site with HTTPS and a custom domain, for free.
Then point your own AI at the repository, and start editing.
The working example: the Factory
SovereignWebsite__Factory is the control repository of the SovereignWebsite organisation: the organisation as code, with everything done by CI under an Agent Behaviour Policy in policy/abp.json. It is the clearest place to see steps 5 and 6 working:
- The policy: what each agent may change, what each pipeline may do, and every privilege its GitHub App and cloud role hold, with the reason. Anything not listed is refused.
- Checks on every pull request and push, read-only and with no secrets: tests, policy validation, a leak scan, signed commits and policy paths, and a dry plan checked against the policy.
- Apply pipelines that may only take the actions the policy lists, and are always refused actions such as deleting, transferring, archiving or making a repository private.
- The owner decides: changes to the policy, the workflows and the build scripts take effect only when the owner merges them, and releases to the main branch are merged only by the owner.
Its code is Apache-2.0 and its text CC BY 4.0, as its README states, so you can read it, learn from it and reuse it.
Free code is not free work
Using the pattern costs nothing, and the running and the upkeep are yours. Owning the files means you can move; it does not move them for you. And a static site is not automatically safe: the policy and the checks are there because an AI can still publish something it should not.
If you would rather not do it yourself
A hosted version is being prepared, with the repository and the site set up for you and the agents building it: see sovereignwebsite.ai. The result is the same kind of thing, a repository you control and can take anywhere.
Follow the work
- The organisation and its repositories: github.com/SovereignWebsite
- Why the name, and the open pattern: Sovereign Agentic Website
- Why governance comes with every step, even the free one: governance from zero
- How one commit can make a repository and a live site: one commit, one site, one owner
What this does not claim
- The pattern's repository is not published as finished; these steps describe the pattern, not a supported product.
- The Factory is an example of CI under a behaviour policy for an organisation, not a site template.
- The hosted version under this name is not running yet.