Their finding was that MISSION.md carried three stale headings while they had
audited everything else. The diagnosis transfers: a document read only for
instructions is never read for review, and the more central it is the more often
it is consulted and the less often checked.
The brief names five documents to read every iteration. I had audited BLOCKED.md
and never PORT-MISSION.md or MODDING.md. Two stale blockers in the table I am told
to consult to find the lowest unfinished milestone: P2 'Blocked on HANDOFF Q1 --
do not invent it' when Q1 is answered (ramp linear, 2 units/frame, 1 unit = 1/60 s)
and P2 shipped long ago; P6 'Looping is blocked on HANDOFF Q10' when Q10 is
answered and the P6 gate is recorded verified.
Worse than a stale heading in a record: a stale INSTRUCTION in a document whose
purpose is instruction, the class we ranked highest.
Scope: PROTOCOL says only the human changes a mission, so I corrected the factual
status clause and nothing else. Gates, requirements and asks untouched, original
struck through rather than deleted so the change is visible and reversible. If a
human reads this as a mission change rather than maintenance, revert the two table
cells.
MODDING.md is still unaudited and is named as such rather than quietly skipped.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
Merges the Godot port into the reverse-engineering repository, preserving both
histories -- 1019 commits of corpus plus the port's 31, brought in by subtree
merge and then moved into place so git can follow each file across the rename.
The reason is not tidiness. The two-repo split forced the exporter to depend on
the decoders by pinned revision, and that created a whole class of failure that
now disappears: a sha reachable only from a topic branch, orphaned by a
squash-merge, breaking a fresh checkout silently at build time. It also forced a
live read-only mount of one agent's working tree into another's container, which
is why a contract file could move mid-iteration. With a path dependency, a
decoder change and the exporter change it requires land in the same commit or
not at all.
Canary stays separate: it is a fork tracking upstream.
New structure for the long term:
docs/game/ how the game is NAVIGATED -- menus, modals, prompts, alerts,
and in-game flight. Written so nobody rediscovers it. Mostly
open questions on purpose; the in-game tutorials are the
resource for the flight half.
docs/port/MODDING.md
modding as a constraint on the exporter TODAY, not a later
feature: one logical asset in one file (the disc splits nearly
everything, and resolving that is the exporter's job), names a
person recognises, PNG/OGG/OGV/JSON only, base-and-overrides so
re-exporting is always safe, provenance in every file.
data/base + data/mods
generated tree and drop-in overrides, both gitignored
exchange/ transient inter-agent files, deliberately outside history
docs/agents/ the team protocol
Both the README and the navigation doc lead with the correction that cost the
most: the oracle is the real game under Xenia Canary. Reborn's renderer is a
hypothesis under test, it has been wrong, and treating it as ground truth
propagated into three documents and both agents before a human caught it.
Scripted modding stays possible without being built: no screen name is hardcoded
in GDScript and there is no native code in port/, which is what Godot Mod Loader
needs to be able to substitute behaviour later.
