Skip to main content
Every action Hive takes — or prepares and a person approves — leaves a receipt. The Audit log collects them. Its own description is the contract: “Immutable. Every action traces signal → plan → decision → result. This is the ‘why’ and the receipt.”

​
Open the audit log

The audit log is not pinned to the sidebar. Open it directly at app.get-hive.ai/audit, or follow a link to a receipt from the place the action started (for example, a handled signal). Use the filter at the top to switch between All actions and Reversible only.

​
What a receipt contains

Receipts are written once and not edited. Undoing an action does not delete its receipt; it marks it as undone and records the compensating action.

​
”Why I did that”

Open a receipt’s explanation to see Hive’s reasoning in four steps:
1

What I noticed

The originating signal.
2

What I checked

The evidence and readings Hive looked at.
3

How I decided

The policy decision — which rung, which limits, who approved.
4

What I did

The action and its result.
The explanation ends with either Reversible · one-click undo or Final · no compensating step, so you know straight away whether a mistake can be walked back.

​
Undo an action

For a reversible action, expand the receipt and choose One-click undo (replays compensating action). Hive runs the compensating action on the server (for example, restoring the previous value or moving an item back) and marks the original receipt as undone.
  • Undo needs the Operator role or higher.
  • Undo is only offered when the source system can safely reverse the change. Irreversible actions — refunds, charges, deletions, revoked access — cannot be undone from Hive, which is why the policy engine always asks a person before running them.
  • If an undo cannot be completed, Hive tells you why rather than marking the receipt undone.

​
Use the audit log in an incident

If something went wrong:
1

Stop further actions

An Owner or Admin engages the Kill switch — see Safety and control.
2

Find the receipts

Filter to Reversible only to see what can be walked back first.
3

Trace the chain

Choose Why did you do that? on the receipt to see whether the cause was the source data, a learned rule, a policy setting or the connection.
4

Undo and correct

Undo what can be undone, then fix the cause: correct the source data, pause the rule in Learned behaviours, or lower the action type’s rung.
5

Resume deliberately

Resume autonomy only when the owner of the affected work confirms the fix.

Review and approve

How actions get approved in the first place.

Safety and control

Kill switch and policy.