Deciding a gate
A gate suspends a run until a person decides. Approvals gathers every open gate of the organisation, with what each would let through; every decision is signed and added to the run's chain of proof.
What you see
- The queue: each open gate, its agent, its privilege level, its age and its deadline. Four tabs — For me, All gates, Escalated, Decided today.
- Filters: agent, tool, age, level, and tasks that came from a remote agent; sorted by age or by deadline.
- The selected gate in detail: the tool or the action; for a call gated by a threshold, its arguments, masked as your policy requires; the guardrails' signed verdict, the delegation chain and the decisions already signed on this run.
Deciding
- Approve: the decision is recorded and signed. If it was the run's last open gate, the run resumes where it stopped.
- Refuse: a reason is required. The refusal is signed just like an approval, and it ends the run: the run moves to « Refused » and does not resume.
- Ask for context: the question lands in the thread of the person who started the run — or in the agent's own thread when it runs alone. The gate stays open: you decide whenever you are ready.
- A two-signature gate waits for the second one, from someone else: the run stays suspended until then.
Who decides
| Gate | Who decides | Signatures |
|---|---|---|
| A run's gate | An approver or an owner. The person who started the run may sign a gate of level 1 to 3; at levels 4 and 5, neither they nor the requester sign. | 1 or 2 |
| A message proposed from Work | An approver or an owner other than the one who proposed it. | 1 |
| An e-mail draft proposed from Work | Whoever proposed it, alone: the draft lands in their own mailbox, and Ailu never sends it. | 1 |
| A remote agent's arrival | An approver or a lead of the named team, or an owner — never the one who asked. | 1 |
| Re-approving a remote agent whose card changed | Its team; for an agent with no team, an owner alone. | 2 · 1 |
A tool whose privilege level is not decided shows as « planned » in the queue, never with a guessed level, and is treated as level 4 or 5. For a run started with an API key, the person who created the key counts as the one who started it.
A viewer sees the queue read-only: deciding takes the approver role.
What is signed
When a gate waits too long
In the Escalation rules, an owner sets a delay per privilege level. Once it has passed, the gate moves to Escalated and the owners are told — depending on the rule, the approvers of the agent's team and the person who started the run as well. An escalation never decides: it tells.
Not yet
SoonThe call's content — amount, recipient — in the signature itself: today the queue shows it, but the signature covers the gate and the decision.
SoonAn approval that holds for one call, whatever the gate: a gate opened by a threshold already works that way; a gate opened by a tool's name alone allows the tool for the rest of the run.