Working draft
What a one-page AI gates statement looks like
A short operating document can make ownership, escalation, and approval boundaries unambiguous.
Why one page
A useful gates statement should be read during the work, not filed away after a workshop. One page forces the team to name the few boundaries that actually govern daily decisions.
What it covers
The statement defines what the system may draft, what it may recommend, what requires approval, and what it must never do. It also names the person accountable for each gate.
The practical test
A new team member should be able to read the statement and know when to proceed, when to pause, and whom to ask. If the answer depends on unwritten context, the gate is not yet clear enough.
This is placeholder copy for a forthcoming field note. The final piece will replace it.