Sylpheed port agent 7a0318c2c0 port: a reproduce recipe naming a path off this repo is not a recipe
From the Decoder's catch at shutdown, not my own. They found their Canary logger
change -- the texture content hash -- living UNCOMMITTED in /canary, a checkout
pushed nowhere. Two committed findings could not be reproduced without it: it is
the field separating "the buffer rotated" from "a frame was decoded", and its
absence is what cost two withdrawn positions on units/second in one day. They
committed it and exported it into the repo as a patch.

Their generalisation applies here too, so I audited this side at the same moment.

One real instance: DECISIONS.md cited
`/reborn/docs/re/captures/main-menu-oracle.png` as the evidence for a decision.
The capture IS in the repository, at docs/re/captures/main-menu-oracle.png --
only the path was stale, left by the monorepo move. Fixed. The other /reborn
mentions are deliberate: one warns the mount is empty, one is a table row listing
the pattern as an example of what not to do.

⚠️ tools/port/check-citations does NOT catch this class, and the gap is named
rather than quietly left: it scans for REPO paths that fail to resolve, and an
absolute path is not a repo path, so it slips through. Extending it to flag
off-repo absolutes -- especially ones whose basename does resolve in-repo, the
recoverable case -- is the obvious next increment and is deliberately NOT done
here. It was found minutes before a shutdown, and a hasty checker is worse than a
named gap.

Index regenerated.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AHUQvXGyNcKonSEWsgWcX
2026-09-01 19:57:50 +00:00

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-cli and 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

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.

Description
No description provided
Readme MIT 820 MiB
Languages
Rust 57.6%
Python 27.7%
Shell 10.6%
GDScript 3.5%
Dockerfile 0.4%
Other 0.1%