A revocation receipt inbox gives users one place to see what an agent remembers, what they changed, what future behavior was updated, and which memory decisions still need review.
Users should not hunt through logs to confirm what an agent stopped using.
Do not design it like a developer event stream. A useful inbox groups receipts by source memory, user reply, policy delta, downstream action, and whether the receipt still needs review.
Each card should summarize the remembered fact, source evidence, revocation verb, future policy change, and rollback path. Super can provide the phone-native surface where many of these revocation decisions are captured before they land in the inbox.
Receipts where the parser was uncertain or the user asked why.
Memory decisions that updated retrieval, prompt construction, or approvals.
Future agent actions that were prevented by a revocation receipt.
The text message AI assistant pattern lets users revoke memory with concise reply verbs.
For browser and publishing work, link receipts to computer-use cache evidence and AI website-building context.
The goal is a user-facing control surface, not an internal compliance archive.
Include source memory, source evidence URL or transcript, original consent scope, revocation verb, user note, channel, policy delta, and rollback state.
Use active, needs review, applied, rolled back, and expired. These states are easier for users to understand than raw event labels.
Support searches like "what did I delete last week," "what memory blocked this action," and "why did the agent ask again?"
When a user replies by SMS, convert the structured verb into a receipt card and show the policy delta immediately.
Let users undo a deletion, narrow a scope further, renew expired memory, or ask for the source evidence again.
These views keep the product useful for everyday users and operators.
Where the remembered fact came from.
The user decision and channel.
What changed in future behavior.
Undo, narrow, renew, or inspect.
Use this list before shipping the inbox into a personal agent product.
Summarize each receipt in human language before showing technical details.
Make every receipt traceable to the message, file, page, or reply that created memory.
Show how future retrieval, prompts, approvals, and actions changed.
Filter by source, date, workflow, channel, sensitivity, and receipt state.
Support rollback, further narrowing, expiry extension, and evidence resend.
Notify only when revocation fails, needs review, or blocks a meaningful action.
The inbox is where memory governance becomes legible to the person using the agent.
Yes. An audit log viewer is usually event-first. A revocation receipt inbox is decision-first and shows how the agent’s future behavior changed.
Ship receipt cards with source evidence, revocation verb, policy delta, search, and rollback. Add analytics after the user workflow is clear.
Super can provide the phone-native review surface that creates the receipt decisions users later inspect in the inbox.
Measure failed parses, missing-source receipts, rollback rate, blocked-action count, and how quickly users resolve needs-review receipts.
These sources frame governance and safety considerations for personal agent memory controls.
Risk management guidance for AI controls, measurement, governance, and trust.
Relevant framing for excessive agency, sensitive information, prompt injection, and agentic systems.
Phone-native review, approval, revocation, and receipt flows for personal AI agents.
A revocation receipt inbox turns memory control into a practical everyday workflow for personal agents.