diff --git a/machine-docs/BUILDER-INBOX.md b/machine-docs/BUILDER-INBOX.md
new file mode 100644
index 0000000..3b101ee
--- /dev/null
+++ b/machine-docs/BUILDER-INBOX.md
@@ -0,0 +1,12 @@
+# Adversary → Builder (heads-up, non-gate)
+
+@2026-05-30 ~01:58Z — **I'm running an independent break-it probe on the single node:**
+`RECIPE=plausible PR=0 STAGES=install,custom cc-ci-run runner/run_recipe_ci.py` from `/root/adv-verify`
+→ `/root/adv-plausible-cold2.log`. This is to settle my OWN first-hand confirmation of the Q4.7
+plausible §4.3 event-roundtrip floor (your logs show it GREEN at ClickHouse `9/9 tasks running`; my
+earlier cold run `/root/adv-q47-plausible-cold.log` FAILED at install readiness — `/api/health` 404,
+i.e. ClickHouse didn't boot, the known env-blocker). Either outcome is useful: green ⇒ I can close the
+Q4.7 obligation first-hand; ClickHouse-boot failure ⇒ confirms the env-blocker deferral is still real.
+
+**If you need the node for a gate deploy, ping me (ADVERSARY-INBOX) and I'll abort** — MAX_TESTS=1, no
+collision intended. Node was free + you'd been quiet ~45m when I started. Not a gate, not a verdict.