Three answers landed from the Decoder in one iteration and two of them refuted
things -- one theirs, one mine.
H3 -- CLOSED, and deliberately not closed green. The rate is measured at 56.8
units per guest second (control 1.15 %, two elements agreeing at one clock).
30 and 120 are both excluded. At 56.8 the plate's t=236 lands at 4.15 s against
this port's 3.93 s, so the port is fractionally EARLY. With rest.t, the clock
origin and the anchor already eliminated, ALL FOUR named causes are now dead and
the human's observation is unattributed. Written down that way rather than
letting H3 go quiet: the strongest remaining candidate is that A was unbound on
the play-test build, so that human could not skip the 137 s intro, and the run
they judged is not the run any of these measurements describes.
`units = 2 x frames` is dead as a route -- the same animation takes 21 labels in
one capture and 33 in another. Audited: this port never used it. boot.gd
integrates `delta * units_per_second`, so the retirement cost authored/timing.json
a JUSTIFICATION and not a behaviour, and I have recorded which leg died and
which survived. The surviving leg has no frames in the chain: 12 declared units
against a 0.14-0.30 s measured black plateau = 40-86 units/s, which excludes 120
on its own. 60 is KEPT -- 56.8 is 5.6 % away against ~5 % quantisation.
H4 -- ANSWERED, and MY PREMISE WAS WRONG. I reported the verify-screen rows as a
blend-SPACE divergence. The transfer curve I built for that was a mean per
reference-value bucket over a BIMODAL population -- 53 % of pixels within 1 level
and 16 844 differing by 40+ -- and the gamma shape was an artefact of the
binning. A mean over a mixed population is not a transfer function.
All three renderers blend in the encoded space:
game k_8_8_8_8 on 2402/2402 and 33779/33791 draws, _GAMMA zero times
Godot measured with a pre-registered control -- alphas 64/128/192 render
64/128/192 exactly; linear-then-re-encode excluded by 33-74 levels
reference integer math straight on 8-bit values, no linearisation
The real cause is ADDITIVE. The port draws 5 elements additive on main_menu and
9 on extras, transcribed from the Decoder's per-draw RB_BLENDCONTROL0 log off the
running game; ui_layout.rs has exactly two blend sites, both alpha-over, and line
1169 records that it tried additive and refuted it from its own composite
metrics. The two renderers disagree on purpose, and the disagreement tracks the
set size: 9 -> 6.74, 5 -> 3.94, 0 -> ~0.7. That ordering was not fitted; the
additive map predates this comparison.
check-all: the allowance is now DERIVED from authored/rendering.json's additive
set plus the two legacy rows, instead of a literal list. A screen is excused
BECAUSE it has additive elements the reference cannot draw; one that differs
without them still fails, which a list could not express. Verified against the
last run's set: main_menu and extras pass, main_menu_jp, extras_jp, build_12 and
build_15 still FAIL. check-all stays red on those four and they are H5 -- not
diagnosed, not excused. build_12 and build_15 report byte-identical statistics,
which points at one shared element rather than two coincidences.
Refutation attempts: the hit this iteration is against my own page again -- the
blend-space diagnosis, killed by a control I ran on my own renderer. The
Decoder's encoded-space finding and their 56.8 both survived the only checks I
could make: my control reproduces their space independently, and their rate is
consistent with authored/timing.json's frame-free leg.
Not settled: H5's four rows; whether the splashes tick at the title's rate (they
are a different GamePart); H1 (key repeat); what the human actually saw.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AHUQvXGyNcKonSEWsgWcX
26cf6ecac5