918ccc46bf
ui-render-tone-curve.md records the game's gamma-ramp write as "inferred from a closed chain, not directly observed". The direct observation is a log in Canary's own DC_LUT write path, which /canary being read-write makes available. Wrote it; could not build it. The patch logs each completed 256-entry sweep with samples against the identity ramp the source documents (i * 0x3FF / 0xFF), so a written ramp is distinguishable from an unwritten one by reading the log. Recorded in the page in full so a future iteration with a working build can re-apply it. BLOCKED: /sylph-home/re/canary-build was configured with -S/work/xenia-canary and that path does not exist in this container. ninja fails at CMake regeneration before compiling anything, and reconfiguring against /canary would trigger a near-full Xenia rebuild -- not something to start on the way to one log line. Per "do not improvise around a blocker", stopped and wrote it down. REVERTED the patch and verified /canary byte-identical to its backup. Leaving instrumented source the running binary does not contain is the source-and-binary-disagree trap this session has caught three times; a later reader would find the logging in the tree and conclude it was live. Also of note for the corpus: the header edit initially failed silently because I chained it with `||`, which hid the failure -- the "assert every edit" lesson from four iterations ago, repeated. Caught by grepping for the symbol afterwards rather than by trusting the command. The ramp write remains inferred, not observed. What is new is the reach: the experiment is written and the obstacle is a build-tree path, not anything about the game. 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.