How this site is governed
AI agents help build and look after this site. They work under a written policy, the Agent Behaviour Policy (ABP), which says what they may and may not do. This page explains it in plain English. The policy itself is a file anyone can read: policy/abp.json.
What it is
A short list of rules for every agent and every automated step that touches this site. Anything the policy does not allow is not allowed.
Who may change the site
- The owner decides. Until the site is handed over, that is Dinis Cruz.
- The keeper is the agent the owner names to look after the site. It may change the pages, the documents and the README.
- Some changes need the owner's yes first: this policy, the automated pipeline, the site's address, and the agents' own instructions.
How changes are made
- Every change goes to a working branch (dev). No agent may push to the main branch.
- Every change is signed with the keeper's own published key and names the agent and its session, so anyone can see who made it.
- Agents never print or store passwords, keys or tokens, never name a private person without their consent, and never invent a fact, a price or a customer.
- The site is plain files: no server, no cookies, no tracking.
What is checked before anything is published
Each change runs through automatic checks. If any one fails, nothing is published:
- links work, and link previews are correct;
- no key, token or secret is in any published file;
- the pages are valid HTML and pass an accessibility check;
- the writing style rules are kept.
Every published version has a number, shown at the foot of each page, which links to the run that checked and published it.
What is enforced, and what is followed
The checks above are enforced by the pipeline on every change. The rules for agents (which files, which branch, signing) are followed by the agents and can be verified in the repository's history; they are not yet checked automatically on this site.
Changing the policy
The policy changes only with the owner's yes, and every change to it is in the history like any other, saying where that yes was given. A keeper may add rules but cannot remove the core ones: the pipeline refuses a weaker policy.