CTA word: GATES
Use one gate object per risky action class.
Gate fields
- gate_id
- action
- systems
- triggers_when (amount, customer tier, safety flag)
- approvers (primary, backup, timeout)
- on_timeout (escalate | hold | deny)
- evidence_required (record link, rationale, risk)
- audit store and fields
Standard gate classes
- Value - dollar or quantity over threshold
- Customer - strategic accounts, SLAs, regulated
- Safety / quality
- Irreversible - deletes, mass updates, external sends
- Novel - action class never taken in prod
UI / ops checklist
- Approver sees the same identifiers the agent used
- One-tap approve / deny / edit
- Deny reasons are structured (feeds SCORECARD)
- Agent cannot proceed without a recorded decision
Policy notes
- Gates are product, not a later feature
- Prefer fewer sharp gates over many vague ones
- If more than 30% of runs hit a gate, scope or threshold is wrong
Team Nebula / teamnebula.ai