897be7bfdd
sylpheed-port's check-claims fails their run when a refuted claim is quoted without an explicit token, and feeding it four withdrawals flagged three still asserted unmarked -- each inside a correction they had written. REFUTED.md publishes deaths without enforcing them, which is the gap I named last iteration and did not close. check_refuted.py is the prose equivalent: for each quoted claim in REFUTED.md it searches docs/ for that text and reports occurrences whose neighbourhood carries no refutation marker. Controlled first -- a claim planted unmarked in a scratch file is detected, so a clean run means something. 9 raw hits, ZERO real revivals. All false positives, and the kinds are the finding: 2 were text explicitly DECLINING to revive a claim; 1 a duplicate report; 4 were BACKLOG.md entries under a 2026-08-12 header, an append-only log recording what was believed then; 2 were the claim quoted inside its own correction. The structural limit is worth more than the clean result. A neighbourhood-language detector cannot separate "asserted now" from "recorded as believed then", because a dated log entry and a revival read identically. The port's design avoids this by testing for a token an author must PLACE rather than for language -- theirs fires correctly inside a correction, which is what caught their three, while mine fires incorrectly there and would miss a revival reworded. Stopped tuning at two remaining. Each marker phrase added fits the detector to this corpus's habits of expression and away from being a test of them; tuning until it reads zero would be fitting the instrument to the answer. Left over-reporting, which is the safe direction. Reach: it matches a claim's exact wording, so "no verbatim revival" is not "no revival". 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.