c7237edc9b
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
Sylpheed
A clean-room reverse engineering and port project for Project Sylpheed: Arc of Deception (Xbox 360, 2007).
Three things live here, in one repository so that a change spanning them lands as one commit:
| The decoders | crates/sylpheed-formats — the disc's formats, read and verified disc-wide |
| The port | port/ — a Godot 4 project, plus crates/sylpheed-export which converts a disc into the open asset tree it reads |
| The corpus | docs/re/ — what has been reverse engineered, with its evidence, its retractions and its dead ends |
You need your own copy of the game. No game content is in this repository and none ever will be. The exporter reads the disc you supply.
The oracle is the real game
sylpheed-cliand the Explorer are tools for verifying our decoding. They are hypotheses under test and they have been wrong. When something must be checked against the truth, the truth is the game running in Xenia Canary, captured — not any renderer of ours.
This is stated first because getting it backwards is the most expensive mistake this project has made.
Layout
crates/
sylpheed-formats/ the decoders. Disc-wide verified; the corpus is its spec
sylpheed-cli/ headless tools -- render a screen, dump a table, probe audio
sylpheed-viewer/ the Explorer: a human's window onto the disc. STATIC data only
sylpheed-export/ disc -> the open, moddable asset tree
port/ the Godot 4 project. Reads open formats ONLY
authored/ decisions that are NOT on the disc, each with its reason
data/
base/ generated by the exporter. Gitignored, never hand-edited
mods/ drop-in overrides. Yours
docs/
re/ the corpus: findings, refutations, method traps
game/ how the game is navigated -- menus, modals, flight
port/ the port's mission, its handoff contract, modding rules
agents/ how the agent team works together
tools/ capture harnesses, probes, the share tool
exchange/ transient inter-agent files. NOT in git
docker/ the agent containers
Where to start
docs/re/INDEX.md— what is decodeddocs/re/REFUTED.md— what has been tested and dieddocs/re/METHOD.md— traps this project has already paid fordocs/game/navigation.md— how the game is navigateddocs/port/MODDING.md— why the asset tree looks the way it does
Xenia Canary is a separate repository: it is a fork tracking upstream, and it carries our instrumentation.
Conventions
Confidence is per claim, never per document: ✅ CONFIRMED · 🟡 PROBABLE ·
❔ HYPOTHESIS · ❌ REFUTED. A withdrawn result is kept with its reasoning
rather than deleted — that is why the numbers here can be trusted.