Files
Sylpheed/authored
Sylpheed port agent 2e29572b02 port: the clock freezes at settle -- my window is the game's, and the boot is known too fast
The Decoder measured build 4's top-level clock stopping inside [160,236]. The
exporter computes title's settle window as [160,236,198] from the file alone.
Same interval, two independent methods -- the first evidence for the settle
instant that does not come from our own renderer. ptcopyright reaching alpha
255 exactly at t=160 agrees from a third direction.

Corrects a claim in three places: timing.json, flow.json and boot.gd all said a
screen's dwell IS its keyframe group and the port reproduced 'the disc's own
pacing'. Build 4 declares ~120 presented frames and dwelled ~1100. The decision
to hold zero extra stands; the claim that it was faithful does not.

Checks their two declared spans against the file: both exact, with a 106-vs-105
interval-convention quibble that changes nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
2026-08-29 21:24:10 +00:00
..

Authored decisions

Everything here is a decision we made, not something the disc said. It is hand-written, committed, and survives a re-export — unlike export/, which is regenerated wholesale and must never be hand-edited.

Every entry carries a why. When the RE agent decodes the real answer, delete the entry and let the exporter emit it; that deletion is the measure of progress.

See docs/FORMAT.md for the schemas and docs/BLOCKED.md for which HANDOFF question each placeholder is standing in for.