re: the pulsing element IS ptbtn00f, and the 1.7x clock conflict was mine

Phase-free: the pulse is exactly 1/10 of the sweep's 600-unit loop -- f6b
gives 60.0 frames over 16 cycles with zero variance against a 600-frame
sweep. 60 leaf units x the independently measured leaf/title = 0.5 gives 120
title units, ptbtn00f's declared loop exactly. That is also a third
independent route to the 0.5 ratio, from an unrelated declared quantity.

And it resolves the conflict I have been flagging on three pages. The quad I
called "the plate" at x=-0.54 is ptcopyright: its fade-in is 21-22 title
units under both agreeing calibrations, matching ptcopyright's declared
22-unit ramp, not the plate's 12. The plate is the pulsing element. Two
elements, one label, and I checked the label -- there was never a clock
conflict. Retires the 🟡 on every title-unit figure across three pages.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t

docs/re/f6-plate-identity-and-clock-conflict-resolved.md

@@ -0,0 +1,68 @@
+# The pulsing element is `ptbtn00f` — and the 1.7× clock conflict was my own misidentification
+
+**Question:** is the thing pulsing on the title the element the corpus says it is,
+`ptbtn00f` on a declared 120-unit loop?
+
+**What the human looks at:** the `PRESS Ⓐ` plate pulses while the sweep crosses.
+Pass = ten pulses per sweep crossing.
+
+**What this does NOT cover:** the snap target's exact instant, `pteff03a`.
+
+**Instrument:** ⟨capture⟩ ×2, phase-free — a ratio of two loops inside one
+capture, needing no clock and no frame rate.
+
+## ✅ Measured — the pulse is exactly 1/10 of the sweep's loop
+
+| | pulse period | sweep loop | ratio |
+|---|---|---|---|
+| `f6b` | **60.0 frames**, 16 cycles, **zero variance** | 600 frames | **0.1000** |
+| `f6` | ~115 frames (median; two frame-drop outliers, 65 and 93) | 1168 frames | ~0.098 |
+
+The sweep's loop is **600 declared leaf units**, so the pulse is **60 leaf units**.
+
+With `leaf/title = 0.5` — measured independently from the parent's declared
+30-unit ramp, two runs, in
+[`f6-unit10-parent-alpha-gates-the-sweep.md`](f6-unit10-parent-alpha-gates-the-sweep.md) —
+
+> **60 leaf units = 120 title units = `ptbtn00f`'s declared 120-unit loop.**
+
+✅ **Identification confirmed.** And it is a **third independent route to
+`leaf/title = 0.5`**: the parent's 30-unit ramp and `ptbtn00f`'s 120-unit loop are
+unrelated declared quantities and they agree.
+
+⚠️ The pulse peaks at **α80**, not 255, and is drawn 51 of every 60 frames.
+
+## ✅ The 1.7× conflict is resolved — and it was mine
+
+I had been calling the quad at NDC `x=-0.54` "the plate" and applying the plate's
+declared `238…250` 12-unit ramp to it. That produced a title clock of 0.571
+u/frame against 1.07 from the parent's ramp — the 1.7×–3.2× conflict flagged
+across three of my own pages.
+
+**It is not the plate.** Its fade-in is 21 frames in `f6`, and two calibrations
+that now agree —
+
+| calibration | `f6` title clock |
+|---|---|
+| parent's declared 30-unit ramp | 1.071 u/frame |
+| **`ptbtn00f`'s 120-unit pulse** | **1.026 u/frame** |
+
+— put that ramp at **21–22 title units**, not 12. A 22-unit ramp is
+**`ptcopyright`**, which unit 8 had already used for exactly that reason.
+
+So: `x=-0.54` is `ptcopyright`; the plate is the pulsing `EAC3:-0.42`. **There was
+never a clock conflict** — two elements, one label, and I checked the label.
+
+🔴 **This retires the 🟡 I attached to every title-unit figure** on
+[`f6-unit9-sweep-period-and-onset.md`](f6-unit9-sweep-period-and-onset.md),
+[`f6-unit10`](f6-unit10-parent-alpha-gates-the-sweep.md) and
+[`f5-a-press-snaps-the-plate.md`](f5-a-press-snaps-the-plate.md). Unit 9's onset
+*fraction* was measured against `ptcopyright`, not the plate — it is not wrong,
+it is **about a different element than its own text says**, and the declared
+`t=70`/`t=100` supersedes it either way.
+
+## Not settled
+
+* The snap target is still bounded to `[100,238]`, not pinned.
+* `pteff03a` absent from every capture.
+* Wrap-to-wrap period: still one wrap per capture.