/ on its own port. Sign in with an operator token.
What it shows
Pending operations
Everything waiting for a human, with the statement as it will run, the agent’s stated reason, the blast radius, hazards, and the deadline.
The diff panel
What the change would do, per record, with the fidelity label always visible.
Connections
Each connection’s capability ladder — what is enforced here, and by whom.
Agents and leases
Who can touch the database right now, their state, and the buttons that end it.
Reading the diff panel
Every preview carries a fidelity label, and the panel never hides it:
“No records change” and “no preview was possible” look completely different, deliberately. A reviewer who cannot tell a measured diff from a guess is being given false confidence.
Previews are masked. A preview reads the table directly, so its rows are masked and column-restricted exactly as an agent’s results would be before a reviewer ever sees them. A review queue lives in browsers and outlives the operation; it must not become a way to read what the agent itself cannot.
What you can do
Revocation is deliberately a review capability rather than a manage one: severing an agent’s access mid-incident is exactly what a reviewer is on call to do, and making them find someone else first is how it fails to happen in time.
Every decision is attributed. Approvals, rejections, freezes, and reinstatements all record who did it and why, and the agent’s own response names the person who approved its change.