diff --git a/graph/configurations/discord-bots-vm-1010033-all-containers-stopped-flagged-for-d-6400cc.md b/graph/configurations/discord-bots-vm-1010033-all-containers-stopped-flagged-for-d-6400cc.md
new file mode 100644
index 00000000000..cbd466147b2
--- /dev/null
+++ b/graph/configurations/discord-bots-vm-1010033-all-containers-stopped-flagged-for-d-6400cc.md
@@ -0,0 +1,30 @@
+---
+id: 6400ccf0-b268-4342-9a13-6157cfc8fc03
+type: configuration
+title: "discord-bots VM (10.10.0.33) - all containers stopped, flagged for decommission"
+tags: [proxmox, homelab, cleanup, infrastructure, discord-bots, decommission]
+importance: 0.6
+confidence: 0.8
+created: "2026-02-20T17:09:44.301102+00:00"
+updated: "2026-02-20T17:09:44.301102+00:00"
+---
+
+# discord-bots VM (10.10.0.33) - Decommission Status
+
+## VM Details
+- **IP:** 10.10.0.33
+- **OS:** Ubuntu desktop (GNOME, CUPS)
+- **Total containers:** 12 (all now stopped/exited)
+
+## Actions Taken
+- Stopped `foundry_foundry_1` and `mln-ghost-ball_discord-app_1` — neither was in production use
+- Added CT 302 public key to `authorized_keys` for future access
+- Skipped adding to health monitoring (nothing active)
+- **Flagged for full decommission** on next Proxmox cleanup pass
+
+## Important Note
+Foundry VTT **production** instance is on `foundry-lxc` (10.10.0.223), NOT this VM. Do not confuse the two.
+
+## Next Steps
+- Review during next Proxmox cleanup pass for full VM removal
+- All 12 containers are stopped — safe to decommission when ready