diff --git a/PENDING.md b/PENDING.md
index df83164..1ed7be9 100644
--- a/PENDING.md
+++ b/PENDING.md
@@ -4207,6 +4207,21 @@ Jurist: *"Confirm that lowercasing is applied at exactly one point in the code a
 | PENDING-89 source (iv) | **AUTHORIZED to read** — 55 files; answers generation diversity only, never correlation of misses |
 | §13.6 block | ⚠ **LIFTED** — its stated condition (§5 ratification) is met |
 
+<!-- DEFERRED-DECISION: fool-beacon-derivation-run-once
+     since: 2026-08-22
+     trigger: date 2026-08-25
+     owner: executor
+-->
+
+⚠ **TRIGGER BLOCK ADDED 2026-08-24.** Until today this run-once, irreversible, dated act had **no
+trigger of any kind** — no cron, no launchd, no scheduled agent, and not a tracked
+DEFERRED-DECISION. It was one of the 105 prose deferrals the drift-check reports as carrying no
+machine-checkable trigger. **An authorized act with no trigger is the purest form of PENDING-156's
+kind (c)**: not a mechanism wired to the wrong path, but none at all. The wake now surfaces it by
+name under "what's unresolved". Timing is NOT instantaneous — the rule reads *"at or after the
+stated timestamp"* with a 24-hour retry envelope, and pulses stay retrievable by timestamp
+(confirmed 2026-08-24 by fetching a 2024 pulse). 12:00Z = **14:00 CEST Tuesday 25 August**.
+
 ### ⚠ THE DERIVATION IS AUTHORIZED TO RUN ONCE — 2026-08-25T12:00:00Z
 
 Against `claude/governance/fool/seed/FOOL-SEED-RULE.md`, pulse epoch-ms `1787659200000`, retrieval `https://beacon.nist.gov/beacon/2.0/pulse/time/1787659200000`, via **curl** (python urllib cannot reach the host here).