Deleting what an AI holds — a memory, an uploaded source, a learned preference — is a blind action: you cannot see what actually goes, or what silently breaks when it does.
Deletion Awareness
Show what disappears before it is gone
Deleting what an AI holds — a memory, an uploaded source, a learned preference — is usually a blind action: you cannot see what actually goes, or what silently breaks when it does. Deletion Awareness shows the blast radius before the delete commits: exactly what will be removed and what currently depends on it, with an option to keep the dependencies and a short window to undo.
Metaphor
Shredder Preview
Interaction
Pre-delete Impact Preview, Keep-Dependencies, Undo Window
Use case
Deleting AI Memory, Removing Sources, Privacy Cleanup, Account Offboarding
Failure mode
Blind Delete
Control mechanisms
Impact List · Dependency Map · Delete / Keep-deps / Cancel · Undo Toast
Reference examples
Homebrew / apt dependency-removal prompts · Google Drive & macOS Trash 30-day restore · Gmail Undo Send
Interactive Example
The chat default and the pattern, against each other on the same task. The demo is the comparison.
"Forget that" is a blind action. You can't see what goes.
Deleting what an AI holds — a memory, a source, a learned preference — usually happens on a single word, with no preview and no trace. You find out what it actually removed only later, when something quietly behaves differently because a dependency went with it.
Deletion Awareness shows the blast radius before the delete commits: exactly what will be removed, and what currently depends on it. Keep the dependencies, delete everything, or cancel — and undo within a short window. Removal becomes a decision you can see, not a guess made in the dark.
Irreversible and invisible is the worst pair in interaction design — at least make the irreversible visible first.
DOPE Lens
How this pattern improves AI interaction quality.
Directability
Delete everything, keep the dependencies, or cancel — and undo within a short window
ObservabilityPrimary
Before you confirm, the delete shows exactly what will be removed and what currently depends on it
Predictability
The same delete always previews the same blast radius — nothing extra disappears silently
Explainability
Each item names what it is, when it was added, and which features rely on it
Fit
Where it earns its place.
when
Deleting AI-held data is irreversible and opaque; users need to see what goes and what breaks before they confirm, not discover it afterward.
when
The item is trivially re-creatable and nothing depends on it — a preview adds friction with no risk to surface.
Closest neighbours
No product ships this exactly — these come closest.
This is a research pattern — we describe a UX move that no shipping product implements cleanly today. The entries below are adjacent: they share the spirit of the pattern even if they take a different shape.

Homebrew / apt · dependency-removal prompts
Homebrew · Debian
The blast radius shown before the delete commits: apt lists "The following packages will be REMOVED" — including dependents you never named — and waits for an explicit confirm; Homebrew warns when an uninstall would break formulae that depend on it. The dependency map half of the pattern, shipping in every package manager.
Visit Homebrew · Debian ↗

Google Drive & macOS Trash · 30-day restore
Google · Apple
The undo window half of the pattern: deleted items move to a trash surface where they stay restorable for 30 days before permanent removal, and a single Restore / Put Back action reverses the delete in place. Deletion as a staged commit, not an instant erase.
Visit Google · Apple ↗

Gmail · Undo Send
The undo-window precedent for irreversible actions: after hitting Send, a toast holds the action open for a user-configurable window (up to 30 seconds) with a one-tap Undo before it commits. The same short-window mechanic the pattern asks for on AI-data deletes.
Visit Google ↗
Research Frame
Why this pattern exists, and where it breaks.
Before the delete commits, show exactly what will be removed and what currently depends on it, with a keep-the-dependencies option and a short undo window.
Chat deletes on a word ("forget that") with no preview and no trace — you learn what it removed only when something later behaves differently.
An impact list that overstates dependencies scares users out of cleaning up; one that understates them is the silent breakage it was meant to prevent.
Common questions
What people ask about this pattern.
When should I use the Deletion Awareness pattern?
+
Deleting AI-held data is irreversible and opaque; users need to see what goes and what breaks before they confirm, not discover it afterward.
When should I avoid the Deletion Awareness pattern?
+
The item is trivially re-creatable and nothing depends on it — a preview adds friction with no risk to surface.
What problem does Deletion Awareness solve?
+
Deleting what an AI holds — a memory, an uploaded source, a learned preference — is a blind action: you cannot see what actually goes, or what silently breaks when it does.
Why is chat the wrong fit for this?
+
Chat deletes on a word ("forget that") with no preview and no trace — you learn what it removed only when something later behaves differently.