e9a57e2167
The Decoder reported that three of their corrections were a LABEL being wrong rather than a measurement -- the right number pointed at the wrong element -- and asked me to re-check any figure of theirs that names an element. Audited all five the port carries. All clean: ptloop01's 30-unit ramp, pteff03's 600-unit loop, ptbtn00f's 120-unit pulse and peak alpha 80, looping_focus_records' period and record_element, and F6's parent gate. 📌 And the reason is worth naming: the port was protected NOT by discipline but because every element-named figure it carries is ALSO declared on the disc, so each was independently checkable. That protection is now structural rather than a one-off audit, because it fails silently in both directions -- a relayed number pointed at the wrong element drifts from the declared one, and a re-export that re-times a keyframe moves the declared one underneath an authored value that was right when written. audit-kinds cannot see either: it checks that a why CITES something, not that the number still agrees. ⚠️ Scope is deliberately narrow: only values with a declared counterpart are checkable. A measured constant with no disc equivalent -- the leaf rate itself -- cannot be verified this way and is not pretended to be. Selftest in both directions; in check-all.
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.