Files
Sylpheed/docs/re/data/ptlogo-eff3-rest-vs-oracle.txt
sylph-decoder ca61aab5f9 re: the record-layout fix is confirmed against the GAME, and settle-vs-rest is not
The era test left one element responsible for all 74 507 differing pixels on
title_jp -- ptlogo_eff3.t32, the corpus's named plateau-less rest() discriminator
-- with two candidate rest poses, (108,72) stale and (98,42) fixed. There is a
capture of that exact screen, so the oracle can choose.

Scored over the 388x423 box where the two renders differ, so the result is not
diluted by the ~92 % of the frame that is identical:

  stale era  rest (108,72)   RMSE 58.412
  fixed era  rest  (98,42)   RMSE 41.690   <- the game agrees with the fixed era
  fixed era  --settle t=213  RMSE 40.210

Until now the keyframe record-layout fix rested on internal consistency: 0 of
1 042 multi-segment alpha ramps constant-rate under the old reading against 857
of 1 540 under the new. Strong, but not a measurement of the game. It now has
one, on the single screen where the two readings change pixels.

Three controls, all run first. Alignment found by sweeping the vertical offset
rather than assuming it -- 45 gives 32.41 against 56.37 and 53.08 either side, a
sharp minimum at the known game-surface offset. The scoring box discriminates:
the same box against a different screen's capture gives 98-103 against 40-58
here. And --black changes nothing (58.412/41.690 either way) because every pixel
in that box is covered by an element -- recorded because the flag's help says a
framebuffer capture must be compared against a black canvas, and here it happens
not to matter.

Sweeping the screen's own timeline with --at gives the noise scale: the capture
sits on a plateau from t~135 to t~240, flat to 1.2 RMSE across 105 units, rising
sharply outside (78 at t=0 and t=270). So the stale-vs-fixed margin of 16.7 is
~14x that flatness and decisive, while the settle-vs-rest margin of 1.5 is INSIDE
it and is not. This capture separates the eras and cannot separate the policies;
the settle-instant proposal stays unadopted.

Refutation attempted: sylpheed-port's adjudication that their shipped pose is
closer to the game than their reference. It SURVIVES, independently and by a
different metric, in the same direction.

Also concedes that my "your branch is the stale era" reasoning was invalid -- I
inferred era from a line count, which is the error they named -- while recording
that the conclusion holds for the ref I could see: origin/auto/port-p6-audio's
ui_layout.rs is md5-identical to origin/main's.

METHOD: two things that should differ producing identical output is a broken
experiment until proven otherwise, and a zero is its most dangerous form. Four
instances now. Verify the inputs differ before believing the outputs match, and
do not infer that difference from a proxy -- line count is not era.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
2026-08-30 14:48:30 +00:00

52 lines
2.1 KiB
Plaintext

# Which rest pose does the RUNNING GAME agree with? GP_TITLE entry 7 (title_jp).
# 2026-08-30. Oracle: docs/re/captures/title-builds/live-title-jp-at-rest.png
#
# The two candidates are ptlogo_eff3.t32's resting pose under the two keyframe
# eras -- the ONE element that differs between them on this screen:
# stale era (origin/main) rest (108,72)
# fixed era (formats-pin-2026-08-30) rest (98,42)
# Scored over the 388x423 bbox where the two renders differ (74 934 px), so
# the measurement is not diluted by the ~92 % of the frame that is identical.
#
# CONTROL 1 -- vertical alignment found by sweep, not assumed:
# offset 0 RMSE 87.29 | 25 83.39 | 40 56.37 | 45 32.41 | 50 53.08 | 60 72.84
# sharp minimum at 45, which is the known game-surface offset in a 1280x720 frame.
# CONTROL 2 -- the bbox discriminates: the same box scored against a DIFFERENT
# screen's capture (the EN title) gives 98-103, against 40-58 here.
# CONTROL 3 -- --black changes nothing (58.412/41.690 either way): every pixel in
# this bbox is covered by an element, so the canvas never shows through it.
## The answer
stale era rest (108,72) RMSE 58.412
fixed era rest (98,42) RMSE 41.690 <-- the game agrees with the FIXED era
fixed era --settle t=213 RMSE 40.210
## The noise scale: sweep the screen's own timeline with --at
t= 0 RMSE 77.974
t= 15 RMSE 78.737
t= 30 RMSE 78.942
t= 45 RMSE 63.053
t= 60 RMSE 71.123
t= 75 RMSE 66.222
t= 90 RMSE 58.504
t=105 RMSE 54.741
t=120 RMSE 45.486
t=135 RMSE 41.276
t=150 RMSE 40.586
t=165 RMSE 40.197
t=180 RMSE 40.336
t=195 RMSE 40.252
t=210 RMSE 40.230
t=225 RMSE 40.141
t=240 RMSE 40.068
t=255 RMSE 58.878
t=270 RMSE 78.414
t=285 RMSE 78.423
# The capture sits on a broad PLATEAU, t=135..240, flat to 1.2 RMSE across
# 105 units, with sharp rises outside it (78 at t=0, 78 at t=270).
#
# So: the stale-vs-fixed margin (16.7) is ~14x the plateau's own flatness and
# is decisive. The settle-vs-rest margin (1.5) is INSIDE that flatness and is
# not. This capture cannot separate settle from rest; it separates the eras.