diff --git a/ansible/inventories/devnet-7/host_vars/buildoor-lighthouse-geth-1.yaml b/ansible/inventories/devnet-7/host_vars/buildoor-lighthouse-geth-1.yaml
new file mode 100644
index 0000000..d449a42
--- /dev/null
+++ b/ansible/inventories/devnet-7/host_vars/buildoor-lighthouse-geth-1.yaml
@@ -0,0 +1,17 @@
+---
+# Canary: run the buildoor PR build with per-slot recurring action plan rules
+# (ethpandaops/buildoor#147) on this builder only — the other three buildoors
+# stay on default_tooling_images.buildoor (main-latest).
+#
+# What it adds: a rule can repeat a slot plan on the same slot index of every
+# epoch, so "win slot 31 and withhold its payload" holds for the whole devnet
+# run instead of a bounded slot list. The image alone changes no behaviour —
+# the rule set starts empty and is created via the WebUI / the
+# POST /api/buildoor/action-plan/rules endpoint. Rules live in the state-db
+# (/data/buildoor.sqlite), so they survive container recreates.
+#
+# Moving tag on purpose: this host is in the watchtower list, so new pushes to
+# the PR branch (with the `build-docker-image` label) roll out here automatically.
+# Revert = delete this file and re-run with `--tags buildoor --limit
+# buildoor-lighthouse-geth-1`.
+buildoor_container_image: ethpandaops/buildoor:qu0b-action-plan-recurring-rules-latest