Competitor comparison
The audit log is historical. The receipt ledger is operational.
Personal AI agents are no longer only responding in chat. They send messages, use browser state, publish websites, and reuse private context across sessions. Traditional audit logs are valuable, but they usually describe what occurred after the fact. Consent receipt ledgers describe the permission boundary before the next action happens.
Audit logs explain events.
An audit log records prompts, tool calls, timestamps, actor identifiers, status changes, and system outputs. This is useful for debugging and compliance. But logs rarely tell the agent whether a previous approval still applies or whether the evidence behind that approval has changed.
A consent receipt ledger stores the allowed action, evidence bundle, excluded action, expiry rule, replay link, result link, and rollback owner. That makes it useful to the agent before execution, not only to the operator after something went wrong.
Audit log
Best for event history, debugging, observability, compliance, and forensic review.
Receipt ledger
Best for approval scope, reapproval triggers, agent policy checks, and rollback context.
Use both
Keep the log for what happened and the ledger for what remains allowed.
Where Super fits
Super is a natural approval layer because personal agents often ask permission over messages while acting across other surfaces. A text message AI assistant can create a receipt without forcing the user into a heavy dashboard.
Where replay fits
For browser actions, a computer-use cache can attach proof to the receipt. For AI website-building agents, the receipt should include the page diff, live URL, source list, and rollback path.