port: record H3 -- the PRESS (A) plate arrives late, and which half is ours

Human play-test, 2026-09-01. Three candidate causes and they do not share an
owner: the unit->seconds constant is the Decoder's, the clock origin and rest.t
are ours. REFUTED.md records that believing rest.t already put a plate 3.97 s
late once. Establish which half before asking.
This commit is contained in:
MechaCat02
2026-09-01 17:59:17 +02:00
parent 72f116a3b4
commit 1494b094c7

View File

@@ -106,6 +106,7 @@ method finding that applies to the Decoder's harness as much as this one:
|---|---|---|
| **H1** | **Does a held direction REPEAT in the menus, and at what rate?** Initial delay and repeat interval, for the d-pad and for the left stick separately if they differ. | Behavioural. The port now does **one step per deflection**`authored`, and deliberately the conservative half: it cannot run away and it invents no rate. If the game repeats, a human will feel it as *"I have to flick it again"*. |
| **H2** | **The splash blur/fade-in does not match the game.** A human watching both says the game's is **more pronounced** than the port's. | Needs a capture of the publisher/developer splash across its fade, at a known frame cadence. The port's ramp comes from the declared keyframes; whether the game applies a **blur** on top — and whether what we read as a fade is one — is not answerable from the export. |
| **H3** | **The `PRESS Ⓐ` plate arrives LATE.** The port raises it at `t=236`, derived `238 118 = 120 units = 2.000 s`. | 🟡 **Half of this may be the port's, and that half must be settled here first.** Three candidate causes: the **unit→seconds constant** (Decoder's), the **clock origin** — do builds 2 and 4 really start together? — and **`rest.t`** (both ours). `REFUTED.md` records that believing `rest.t` already put a plate **3.97 s late** once. Establish which half it is *before* asking, and say how. |
**On H2, three things the port can say that narrow it**, none of which settle it: