Examples: the best policies we have, and why
Read 16 November 2026. None of these is in the AgentiCCells format yet (it is new); each shows one thing done well. Links point at the published page or at a pinned commit.
Whole policies
| Policy | What it does well | Watch out for |
|---|---|---|
| Web Summit conductor's ABP | Measured reach (environment variables by name only), a mandate in three parts, gaps with dates and issue numbers, a barrier table with kind and evidence, its own failure recorded, a licence to operate, a phase line. The team's template. | Observe only; dev still unprotected. |
PrompTugal place.faro (and the other town agents) | Four exact paths for one place; its own site key signs its own data file, machine-checked ("36 of 36 places pass"); a never list with named hosts. 20 town folders: 233 runs, 34 attempts, 8 breaches. | content/articles/*.md is shared by 20 roles, so "never writes another place's file" does not hold for articles. |
PrompTugal outreach | One folder; one testable never ("sends an email or posts: a person does") backed by an empty send_hosts. | |
PrompTugal security | Two paths; owns board/HOLD.md, which nobody else may write; may not fix what it finds in others' paths: separation of duty. | |
| Storm Charles librarian's ABP | The clearest Reach, Mandate, Gap and Barriers page, with each barrier's kind, and an honest "DRAFT, NOT AGREED" header. | |
| Newsroom behaviour policies | Generated from the same role files the checker reads: "this table and the check cannot disagree". Three principles: create anywhere, edit your own; one owner for each shared surface; flag, do not fix. |
Parts worth copying
- The data file and its checks: PrompTugal's
policies.json: deny by default, aprotected[]list where every entry has an owner and a reason, a breaker per rule, fixture tests for the hook (183 at v1.9.0), a hash pin on the hook, re-anchoring on compaction. - The run report: PrompTugal's
run-report.schema.json: per run, the policy version and hash, tool calls by kind, would-have-denied attempts with rule and target, breaches, compactions and whether they were re-anchored. It stores a hash and a redacted head of each prompt, never the full text. (Missing: a mode field.) - The vocabulary: RiskMandate's 23 capabilities, each with verb, object, reach, undo class and gloss, and its derived delta.
- One rule as a page: RiskMandate's push-anywhere, with a line a person can paste: "Push only to the branch I named; never push to main or force-push, and ask before pushing anywhere else or opening a pull request."
- Altitudes: the email cell's five (the email agentic cell), the model for the cell template.
- Measured reach, before and after a harness: the Swarm's harness reach file: mandate, reach unharnessed and harnessed, and what the harness closed.
- A scoreboard: Web Summit's ABP in action after five days and about 85 agents: 7 caught by review, 7 found by an ABP and fixed, 1 rule turned into a technical barrier, 6 still open.
In this format
This page is generated from index.md, its Markdown twin.