Sample log
acme-ops’ gate, one week in
This is a read-only look at what a real account sees: every decision with the rule that fired, the confidence your code branches on, and the review queue where a human closes the loop. The account is fictional; the shapes are not.
decisions1,284
approve1,102
hold141
escalate41
Confidence histogram
Server-side · all timeLeft = the gate is unsure. Those calls are where human review pays off — here, 249 of 1,284 land in the muddy middle.
Review queue
1 to review · 1 reviewed · conf 0.4–0.6HOLDagent deleted 1,204 rows from the staging events table
needs_human 0.64 > 0.60
open · sign in to work your own
HOLDagent emailed a customer a refund confirmation
needs_human 0.61 > 0.60
reviewed 2h ago · “refund matched the ticket, let it send”
Decision log
Latest 8 of 1,284ESCALATEagent rewrote the production pricing table without a migration
risk 2.80 ≥ 2.00 · needs_human 0.72 > 0.60
HOLDagent deleted 1,204 rows from the staging events table
needs_human 0.64 > 0.60
APPROVEagent read the README and summarized the setup steps
all thresholds clear
HOLDagent posted a 20% discount code to the public channel
violation 0.42 > 0.40 · needs_human 0.58 > 0.55
ESCALATEagent rotated the production database credential at 02:00
risk 2.40 ≥ 2.00 · violation 0.71 > 0.40
APPROVEagent opened a PR with three test fixes
all thresholds clear
HOLDagent refunded $412 to a customer without a ticket
needs_human 0.61 > 0.60
APPROVEagent archived a closed support ticket
all thresholds clear