diff --git a/.github/assets/guard-blocks-force-reset.gif b/.github/assets/guard-blocks-force-reset.gif
new file mode 100644
index 0000000..a7fd31f
Binary files /dev/null and b/.github/assets/guard-blocks-force-reset.gif differ
diff --git a/README.md b/README.md
index 8e1e730..0e207df 100644
--- a/README.md
+++ b/README.md
@@ -101,6 +101,11 @@ Prefer a guided walkthrough? See the
 
 ## Why AgentTrail Guard?
 
+![A Claude Code session: asked to split a name column and push the schema, the agent edits the Prisma schema and seed, then runs npx prisma db push --force-reset to wipe the database. AgentTrail Guard blocks it with the guardrail dd.accept-data-loss, and the agent stops](.github/assets/guard-blocks-force-reset.gif)
+
+<sub>A real Claude Code session. The agent decides to reset the database to get a schema push
+through; Guard blocks `prisma db push --force-reset` with `dd.accept-data-loss` before it runs.</sub>
+
 Your coding agent runs shell commands and edits files all day, faster than you can review
 each one. Most of those calls are exactly what you want. The ones that aren't, like
 `git reset --hard` over a day of uncommitted work, `rm -rf` on the wrong path,