Agent audit trail

Six months from now, you can still show why your agent did what it did.

One log holds the decision, the moment it changed, and every agent action checked against it since, including the ones held before execution. AI agent governance depends on being able to reconstruct exactly that: what an agent did, what it was prevented from doing, and whether it was entitled to act. It is also what lets you give an agent more responsibility.

Audit trail

Default customer pricing

  • When

    Mar 3

    Event

    Starting price set

    Source

    Billing system

    Detail

    Price list v1

  • When

    Apr 18

    Event

    All prices raised 8%

    Source

    Slack

    Detail

    #customer-renewal

    “Let’s take enterprise up 8% from May.”

  • When

    Apr 18

    Event

    Flagged to the owner

    Source

    Rithmo

    Detail

    Price list out of date

  • When

    Apr 21

    Event

    Renewal emailed

    Source

    Agent · without Rithmo

    Detail

    $4,800.00 to Acme Inc.

  • When

    Apr 21

    Event

    Held the renewal

    Source

    Rithmo

    Detail

    Wrong price, nothing sent

  • When

    Apr 22

    Event

    Price list updated

    Source

    Billing system

    Detail

    Back in sync, v2

  • When

    Apr 22

    Event

    Renewal emailed

    Source

    Agent · with Rithmo

    Detail

    $5,184.00 to Acme Inc.

Checked at the point of action

When the information is wrong, the agent does not send.

On April 21 the renewal agent was about to email Acme Inc. a price that was three days out of date. Rithmo checked the price list against the decision, found they did not match, and held the send. The person who owns pricing was told. Both went into the log.

That is the line you need when someone asks whether a wrong invoice ever reached a customer. The send that went out the next day, at the right price, is on the record too. A trail like that is what makes it reasonable to let the agent keep sending.

The same trail, expanded

Expand any line to see what it was based on.

Here the April 18 price change is open: who changed it, where they said it, who confirmed it, and the price list it contradicted.

Audit trail

Default customer pricing

  • When

    Mar 3

    Event

    Starting price set

    Source

    Billing system

    Detail

    Price list v1

  • When

    Apr 18

    Event

    All prices raised 8%

    Source

    Slack

    Detail

    #customer-renewal

    “Let’s take enterprise up 8% from May.”

    Why this line exists

    • Slack · #customer-renewal

      “Let’s take enterprise up 8% from May.”

      VP Sales, April 18

    • Pricing review

      “Agreed. 8% across the enterprise tiers.”

      Confirmed by the CFO, April 18

    • Renewals thread

      “Anything renewing after May 1 goes out at the new number.”

      April 19

    What it contradicted

    Billing system

    Enterprise price list: $4,800.00

    Out of date
  • When

    Apr 18

    Event

    Flagged to the owner

    Source

    Rithmo

    Detail

    Price list out of date

  • When

    Apr 21

    Event

    Renewal emailed

    Source

    Agent · without Rithmo

    Detail

    $4,800.00 to Acme Inc.

  • When

    Apr 21

    Event

    Held the renewal

    Source

    Rithmo

    Detail

    Wrong price, nothing sent

  • When

    Apr 22

    Event

    Price list updated

    Source

    Billing system

    Detail

    Back in sync, v2

  • When

    Apr 22

    Event

    Renewal emailed

    Source

    Agent · with Rithmo

    Detail

    $5,184.00 to Acme Inc.

Give agents more responsibility, and show they were entitled to act.

Rithmo holds the decision each one was checked against, and the record of every action checked against it.