diff --git a/authored/rendering.json b/authored/rendering.json
index 3b5df0fe..726648c7 100644
--- a/authored/rendering.json
+++ b/authored/rendering.json
@@ -185,12 +185,29 @@
     "  leaf/title = 0.4795 and 0.4667, 2.7% apart.",
     "  docs/re/f6-unit10-parent-alpha-gates-the-sweep.md.",
     "",
-    "  \ud83d\udd34 This number was adopted as 0.514, withdrawn, and reinstated as 0.5 within",
-    "  one day. What failed the first time was quoting a rate in captured FRAMES --",
-    "  frames are presents and the present rate differs per run (1168 vs 600 for one",
-    "  animation). The ratio itself was sound; it was discarded with the frames.",
-    "  A calibration that is itself declared does not have that failure mode.",
+    "  \u2705 THREE INDEPENDENT CONFIRMATIONS, and it needed them. The number was",
+    "  adopted as 0.514, withdrawn, then reinstated at 0.5 inside one day. What",
+    "  failed the first time was quoting a rate in captured FRAMES -- frames are",
+    "  presents and the present rate differs per run (1168 vs 600 for one",
+    "  animation). The ratio was sound and was discarded along with the frames.",
+    "  It now rests on three declared quantities that agree:",
+    "    - ptloop01's own 30-unit alpha ramp used as an in-capture title clock;",
+    "    - the leaf's declared 600-unit loop;",
+    "    - ptbtn00f's pulse at exactly 1/10 of that loop -- 60.0 frames over 16",
+    "      consecutive cycles with ZERO variance, and 60 leaf units x 0.5 = the",
+    "      declared 120 title units.",
+    "  The third has no relationship to the first, which is what makes it worth",
+    "  more than a repeat measurement.",
     "",
+    "  \ud83d\udd34 A STALE CAVEAT REMOVED HERE. This block carried a 1.7x/3.2x title-clock",
+    "  conflict as an open doubt against every unit-valued figure on the screen.",
+    "  It was never a conflict: the Decoder had been applying the plate's declared",
+    "  ramp to ptcopyright, and one mislabelled element generated the whole",
+    "  discrepancy (docs/re/f6-plate-identity-and-clock-conflict-resolved.md).",
+    "  Two elements, one label -- the same shape as the port gating a snap on",
+    "  settle_instant while reading a printed number that came from settle_time().",
+    "  \ud83d\udccc In both cases what caught it was measuring a RATIO, which needs no",
+    "  identification, rather than a value, which does.",
     "start_units null -- there is NO authored onset any more, and that is the point.",
     "  F6's gate is DECLARED: ptloop01/ptloop02 carry `0:0 70:0 100:255 238:255",
     "  250:0`, so the sweep is invisible until t=70 and full at t=100. The port had",
diff --git a/docs/port/plate-arrives-on-time-but-never-blinks.md b/docs/port/plate-arrives-on-time-but-never-blinks.md
index 6aaa168d..6e004a7b 100644
--- a/docs/port/plate-arrives-on-time-but-never-blinks.md
+++ b/docs/port/plate-arrives-on-time-but-never-blinks.md
@@ -118,3 +118,31 @@ nor was supposed to.
   disagree, and names who can adjudicate.
 * Anything about the plate's **absolute** alpha or position. Onset timing and
   whether it extinguishes, only.
+
+---
+
+# ✅ The pulse is now MEASURED — and still not implemented
+
+**2026-09-02.** This page established that the port holds `PRESS Ⓐ` permanently
+lit where the disc declares a 30-unit pulse, and closed by saying the port would
+not move until someone measured whether the guest pulses it. It has been
+measured, as a by-product of F6:
+
+| | |
+|---|---|
+| element | **`ptbtn00f`** — the focus variant, not `ptbtn00` |
+| period | **120 title units**, from 60.0 frames over 16 consecutive cycles with **zero variance**, against a 600-frame sweep loop |
+| peak alpha | **80**, not 255 |
+| duty | drawn **51 of every 60** frames |
+
+The period is phase-free: it is exactly 1/10 of the sweep's declared 600-unit
+loop, and 60 leaf units × the leaf/title rate of 0.5 gives the declared 120.
+
+**Not implemented, and deliberately so.** The current focus is the title's
+animation timing (F5/F6), both now closed; the plate's blink is neither, and the
+human's standing note on the plate is that its *delay* is accepted. Picking this
+up is a decision for them, not a gap to fill quietly.
+
+⚠️ Note for whoever does: the port draws the plate through `ptbtn00`, and the
+pulsing element is `ptbtn00f`, reached by `focus_link`. That is the same element
+whose absence from a declaration-order walk has now caused trouble twice.