Build your own service-to-control map

The prompt

Build your own version of a service reference table: every service or capability your agent stack touches, its role in your platform, and the specific control it's responsible for. Where two services seem to overlap in responsibility, pick one owner.

Why it's built that way

The handbook consolidates service roles, control mappings, example instructions, and acceptance criteria into one reference specifically so nothing is left as an assumption — the same discipline applied to your own stack turns tribal knowledge into a reviewable document.

What to do with the answer

Put this table in your repository's docs, not a slide deck — it needs to be as durable and reviewable as CLAUDE.md.