Dry-run a new agent policy against past activity before it goes live. See how it works

Skip to content
Gaten

Platform · Audit trail

Who allowed this? Answered in minutes.

Every request, every decision, every approver — written to a log that can only grow, and linked to the exact rule that made the call.

Decision log · liveIllustrative — sample data
09:12:04support-agentissue_refund · $500APPROVEDfinance-lead
09:11:47ops-agentrestart · api-eu-2ALLOWED—
09:11:30payments-agentpay_invoice · $18,400HELD2 approvers
09:10:58support-agentexport_customers · 2,318 rowsDENIED—
09:10:12sales-agentsend_email · pricingAPPROVEDsupport-lead
09:09:41support-agentissue_refund · $45ALLOWED—

Anatomy of a record

Eight facts, every time.

Each entry carries enough to explain the decision on its own — no cross-referencing other systems.

When
09:12:04.318 UTC
Agent
support-agent v3.2
On behalf of
customer #88412
Action
issue_refund
Arguments
order A-2210 · $500
Decision
require_approval → approved
Approver
finance-lead · 1m 52s
Policy
refunds @ v2.4 · rule 2

Search

Ask the questions reviewers ask.

Engineers, process owners and auditors each get to the answer they need.

  • agent:support-agent this week

    Everything one agent did, in order.

  • action:issue_refund amount>500

    Every large refund, and who allowed it.

  • approver:finance-lead

    Every decision one person made.

  • decision:denied policy:refunds

    Where your limits are actually stopping things.

Append-only

Entries can't be edited or deleted. Corrections are new entries that point to the old one.

Versioned with policy

Old policy versions stay readable, so every past decision can still be explained.

Exportable

Send decision logs to your security or data tools, or export a period for a review.

Conceptual sculpture of layered glass records with a blue layer
A record that only growsConceptual illustration

Know what every agent did, and why.

Talk to an expert about the records your reviewers and auditors need.