Guides
Action receipts
Every AI action that changes your company leaves a receipt — what ran, why, what changed, and how to undo it when reverse is a single step.
An action receipt is the durable record of an AI action that changed your company: what ran, on what evidence, with what outcome, and how to reverse it when reverse is one coherent step. Receipts answer “what happened while I wasn’t watching?” — so you can stop babysitting without flying blind.
This is operator documentation for the trust spine. Short citable definition: Action receipt (glossary). Product narrative: /receipts.
- 01Draft / planNot committed yet
- 02Approval boundaryHold · edit · reject · or earned auto
- 03ActWorld changes
- 04Action receiptWhat · why · outcome
- 05Undo or ledgerRestore only if one reverse step
- 01
Draft / plan
Not committed yet
- 02
Approval boundary
Hold · edit · reject · or earned auto
- 03
Act
World changes
- 04
Action receipt
What · why · outcome
- 05
Undo or ledger
Restore only if one reverse step
Why receipts exist
Autonomy without a record is just hope. HiveBase treats trustworthy autonomy as scaled to blast radius: reversible work can run with a receipt; one-way doors stay held. Receipts are the reason you can turn the dial up — not a compliance product in disguise.
What’s on a receipt
Exact UI varies by surface (tasks, squads, integrations), but a real receipt includes:
| Field | Meaning |
|---|---|
| What | Action type, target, short summary of the change |
| Why | Sources, brief rationale, which policy path allowed it |
| Outcome | Succeeded, held, failed, corrected |
| Before / after | What changed when that delta is meaningful |
| Undo / restore | When one compensating action can put the world back |
No fake undo
Not every multi-step scorecard gets one-click undo. A genuine one-action receipt can restore; a complex verification pack without a single reverse does not invent an undo button.
Draft ≠ commit
Agents prepare freely. Committing to the outside world (or high-impact internal state) is a different step. See Draft ≠ commit and Approval boundary.
How receipts show up day to day
- An agent proposes or runs work grounded in the Brain.
- If the step is outbound or high-impact, it holds for you (unless that category has earned autonomy).
- After the action applies, a receipt is written to the ledger.
- You can inspect sources, outcome, and undo when available — from the task, FYI, or receipts views in product.
Related verdicts
For coding and other verified work, a receipt may sit next to a verification verdict: Completed is a claim. Delivered is a verdict. Receipts record the action; verdicts judge whether evidence supports “done.”