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

PolicyWhat it does wellWatch out for
Web Summit conductor's ABPMeasured 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 outreachOne folder; one testable never ("sends an email or posts: a person does") backed by an empty send_hosts.
PrompTugal securityTwo 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 ABPThe clearest Reach, Mandate, Gap and Barriers page, with each barrier's kind, and an honest "DRAFT, NOT AGREED" header.
Newsroom behaviour policiesGenerated 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

In this format

This page is generated from index.md, its Markdown twin.