fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: an uncontrolled capture instant, and why the ptlogo_eff3 result survives it

Browse Source 
sylpheed-port's harness grabbed main_menu at t=9.00 in one session and t=8.00 in
the next. One keyframe unit apart, mid-build-in, is 70 % of the picture, and it
read as "the change broke two screens" -- a real measurement of the wrong thing.
The instant was stable WITHIN a session and drifted BETWEEN them, so every cheap
reproducibility check said deterministic. Their flags are their harness's, not
sylpheed-cli's (checked: `screen` has only list/info/render), so the tool defect
is not in my crate -- but the hazard generalises to every live capture here.

It would void this iteration's ptlogo_eff3 adjudication if the JP capture had
been taken at an arbitrary moment. It was not, and for two independent reasons
recorded rather than assumed: the grab was gated on the plate pulse, the title's
own settled signature, with the gate and a contrast control written beside the
capture in jp-title-at-rest.txt; and the --at sweep shows the capture on a
plateau flat to 1.2 RMSE across 105 units against edges at 78, where a capture
caught mid-build would give a sharp minimum. The sweep was run for a noise scale
and answers this too -- which is luck, so METHOD now names both defences.

METHOD: pin a capture's instant explicitly, and do not infer stability from
repeat runs inside one session. Gate the grab on a settled signal prospectively,
and sweep --at retrospectively -- a broad flat minimum with sharp edges means at
rest, a sharp minimum means the instant is load-bearing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-30 14:57:55 +00:00
parent 0c2910636a
commit c7237edc9b
2 changed files with 37 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/re/structures/ui-resting-pose.md
View File

@@ -54,6 +54,22 @@ and cannot separate the *policies*, and the number that says so is the plateau's
own width. The settle-instant proposal stays unadopted on the same evidence it
had.
### ✅ Why the capture's own instant is not a confound here
`sylpheed-port` found their harness capturing the same screen one keyframe unit
apart in different sessions — 70 % of the picture, mid-build-in, and stable enough
within a session that repeat runs said "deterministic". That hazard would void this
adjudication if the JP capture had been grabbed at an arbitrary moment. It was not,
and there are two independent reasons:
* **prospective** — the grab was gated on the **plate pulse**, the title's own
settled signature, and [`data/jp-title-at-rest.txt`](../data/jp-title-at-rest.txt)
records the gate and a contrast control taken with it;
* **retrospective** — the `--at` sweep above shows the capture on a **plateau flat
to 1.2 RMSE across 105 units with edges at 78**. A capture caught mid-build would
produce a sharp minimum instead. The sweep was run for a noise scale and answers
this too.
⚠️ **Reach.** One screen, one capture. The absolute residual is ~40 RMSE even at
the best instant, because the JP title carries live animation a static render
cannot reproduce; every comparison here is relative and none of it says our render