Implementation: ENABLED (attention gate) · DESIGN (Agency API attention surface) · Exposure: INTERNAL · PUBLIC PREVIEW (contract). See status labels. An approval is a recorded decision by a person, tied to a specific action. It does not weaken a hard deny.

​
Architecture contract

Policy decisions are ALLOW, ALLOW_WITH_LIMITS, ASK and DENY, with a precedence of hard deny, hard allow, soft, cognitive, then fail-closed. ASK creates an attention request; the answer becomes a scoped, expiring grant. Escalation is driven by confidence, consequence, irreversibility, cost, novelty and verification failure, not by blanket review. Money and client communication are always human-approved. Missing calibration, low confidence, a judge timeout or a judge error all resolve to ASK, never ALLOW.

​
Current implementation

The attention gate is on main inside the work runtime. Agency API attention endpoints are a preview contract.

​
Availability

​
Developer relevance

Design actions so an approval answers one specific question. Do not batch unrelated effects behind one approval.