da7864e499
The Decoder answered H3 in both halves (a482d9a, against a pre-registration
committed before they read the capture) and refuted two things I published an
hour earlier. Both are struck in place, not deleted.
1. units/frame is 2, not the 5 I inferred. Three consecutive gap-free steps of
exactly 23 on ptbtn00's own ramp; 255*2/22 = 23.18. My 4.4-frame prediction
is excluded by more than 2x.
My derivation was sound arithmetic on two unsound premises, both mine to
have used:
- an alpha step is not a clock rate. dA/frame = 255*(units/frame)/T, so
elements with different declared T show different steps at ONE clock.
Splash quads step 34 with T=15; the plate steps 23 with T=22.
- my "onsets" were first submissions, and on splash A both quads are
already at a=85 when first submitted -- biased late, and by a different
amount per element because the bias scales with T.
The three intervals agreed with each other because they SHARED the bias.
Three measurements with a common error are one measurement. That is the
shape I should have checked for and did not.
2. My claim that the t=160 anchor collapses `clock: "shared"` is WITHDRAWN. The
anchor is indeed t=160 -- ptcopyright, calibrating to t~168-176 -- but I
falsified the model using the 2.135 s figure, which is the one number the
same capture puts in dispute. Falsifying a model with the quantity that is
itself under dispute is the error. Against the new capture's own labels the
declared 54 and 76 units reconstruct at 44 and 66 -- short by 13-19 % in the
same direction, with empty labels a named candidate for the residual.
`clock: "shared"` stands, and the port keeps it.
Still open and now the only thing left on H3: units/second = 2 x guest fps, and
whether the guest is 30 Hz or 60 Hz is unestablished. 2x60 = 120 units/s puts
the plate at 1.97 s instead of 3.93 s, which is the size of what the human
reported. The Decoder asked me not to move off 60 on their account yet; I have
not.
Separately -- check-all is RED and stays red. verify-screen newly DIFFERS on six
screens outside its allowed set (main_menu, extras, main_menu_jp, extras_jp,
build_12, build_15). Measured, not diagnosed:
* not this iteration's doing, and excluded structurally rather than by a
passing test: sprites are read as bytes and built with
Image.load_png_from_buffer, so they never enter Godot's import pipeline and
the new `--import` step has no path to the drawn pixels;
* the difference is FULL-FRAME, exactly zero on unblended pixels (18 081 of
them agree to a hundredth of a level at ref 199/204/255) and gamma-shaped on
every blended one. That is a blend-SPACE divergence, not moved content;
* scored against live-main-menu.png the port is 16 % closer than the reference
(RMSE 3152 vs 3770) -- an ordering only, since both sides carry this
script's --pose=rest contamination, which has produced a false finding here
before.
Not widened. This allowance has twice been broadened with a reason that turned
out false, and "I measured it but cannot say which renderer is right" is not a
reason. New ask H4: what colour SPACE is the blend evaluated in -- the Decoder
has the equation from shader ucode, not the space.
Refutation attempts: both of this iteration's hits are against my own page from
last iteration. The Decoder's units/frame law and their anchor measurement both
survived the only check I could make of them -- their steps reproduce this
export's declared T on two screens at one clock.
Not settled: guest fps; which renderer's blend space is right; H1 (key repeat).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AHUQvXGyNcKonSEWsgWcX
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
-- and RUNNING.md, which is how you actually start it
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.