From 7c007cc421df6d9f243afe8fa7551c7411f45996 Mon Sep 17 00:00:00 2001 From: sylph-decoder Date: Thu, 3 Sep 2026 19:22:37 +0000 Subject: [PATCH] re: pre-register the two-leaf period ratio before measuring pteff03a's declared timeline has never been checked against a capture. The leaves declare 600 and 720 units, so the periods must differ by 1.200 within a single capture. Equal periods is the flattering-but-wrong outcome the batched-draw reading could have produced. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t --- docs/re/f6-two-leaf-periods-prereg.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 docs/re/f6-two-leaf-periods-prereg.md diff --git a/docs/re/f6-two-leaf-periods-prereg.md b/docs/re/f6-two-leaf-periods-prereg.md new file mode 100644 index 00000000..a9e6dadb --- /dev/null +++ b/docs/re/f6-two-leaf-periods-prereg.md @@ -0,0 +1,20 @@ +# Pre-registration — the two sweeps must loop at 720:600 + +Committed **before** measuring. `pteff03a` was only found to be drawn at all in +[`f6-unit11`](f6-unit11-pteff03a-IS-drawn.md), so its declared timeline has never +been tested against a capture. + +The leaves declare **different loop lengths**: `pteff03` **600 units**, +`pteff03a` **720**. If that decode is right the two strips must drift apart, with + +> **period(pteff03a) / period(pteff03) = 720 / 600 = 1.200** + +measured inside a single capture, so no clock or frame rate enters. + +| if the decode is right | if it is wrong | +|---|---| +| ratio ≈ 1.20, in both captures | equal periods (one shared clock), or any other ratio | + +Equal periods is the outcome that would flatter a lazy reading — one traveller +driving both quads — and it is exactly what unit 11's batched-draw discovery +could plausibly have produced. So the test can fail against me.