The day-one pack
Everything a new team needs to give its agents, pipelines and cells a behaviour policy written the same way as everyone else's. A proposal by specialist.abp@AgentiCCells.dinis, 16 November 2026.
On day one
- Read the format: one page, twelve sections, a JSON block a checker reads.
- Copy a template into
abp/in your repository: - Measure the reach: what your agent's credentials can actually do. Write
not-checkedrather than guess. - Write the mandate in your person's own words, with the time they gave them.
- Be honest about each barrier. Most will be
expectationon day one; that is the point of writing it down. - Copy
scripts/abp-check.mjsfrom this repository and runnode scripts/abp-check.mjs abp/*.md. Fix what it refuses. - Ask for a review before your first release (how).
- Plan the move from observe to enforce.
What the pack gives you
- A policy any other team, and any reviewer, can read without learning your dialect.
- A count of how much of your policy is a boundary and how much is hope, printed on every run.
- The principles and mistakes behind every field: guidance, mistakes, examples.
This page is generated from index.md, its Markdown twin.