FOUR THINGS, and the first is what MISSION section 3 calls the measure of
progress.
DELETED `exit_ramp_units` AND `exit_ramp_seconds`. They were authored because the
disc had no time slot on a group's final keyframe, so the ramp into it was the
one unknown duration per screen. Under the corrected record layout that keyframe
does not exist -- a group is an 8-byte header then frames x {u32 time; 36-byte
pose} and every pose is timed. VERIFIED DEAD BEFORE DELETING: setting it to 9999
(166 s) moved the boot's transitions by 0.04 s, which is wall-clock jitter, and
both uses in ScreenView are gated on a condition that no longer fires on any of
the export's 866 keyframes.
INVERTED THE FORMAT'S OWN RULE. `check.rs` enforced "the final keyframe has no
`t`; the disc has no time slot there" and FORMAT.md stated it. Both are now
backwards, and the validator fired 150 times on a re-export. I had not run
`check` between pinning the tag and measuring against the oracle -- the pixel
harness was green while the format validator was failing on every screen with a
multi-keyframe group. A correctness harness does not replace a format one; they
fail at different layers.
GUARDED A SCALE-0 LEAF, which the Decoder hit in its own renderer: its leaf
branch marked the element drawn unconditionally while the blit returned early on
zero scale, so a scale-0 leaf suppressed its parent and blanked the element --
live on all four loading screens. This port did not have the bug only because
authored/rendering.json happens not to list pgloading_loop5. That is an accident
of a gate written for another reason, not a defence, so `_draw_leaf` now reports
whether it drew and `_draw` falls back to the parent.
ISOLATED THE PACING QUESTION rather than leaving it as a suspected regression.
Legacy association: publisher 4.70 agrees, developer 3.92 DIFFERS. Corrected:
publisher 4.26 DIFFERS, developer 3.62 agrees. Both misses are ~0.03 s outside a
composite bound. The association traded which screen is marginally out; it did
not regress the pacing.
Bumped the pin c -> d for the parser and audio changes. Its headline renderer
change does not reach this port: sylpheed-cli builds from the workspace crate.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
The human listed pulsation as first-class and the port drew nothing: the plate's
focus record `ptbtn00f` was never reached, because press_start has no `buttons`
and nothing is focused. That it LOOPS is measured -- the corpus timed the period
four times (2.12 / 2.19 / 2.34 / 2.31 s) and you cannot measure a period unless
the thing repeats.
THE RULE I WAS GOING TO WRITE DIED IN THE CENSUS. The spinning ring is a rule in
the renderer because it has a disc-wide check: 16 of 212 elements match its shape
and all 16 are focus rings. The analogous shape for a pulse -- keyframes varying
only in alpha, first alpha equal to last -- matches 82 OF 212, including
ptcopyright, palogo_sqex, ptmsg and every _eff fade. A renderer rule on it would
make the copyright notice pulse. Narrowed to focus records it matches exactly one
distinct element, and a rule justified by n=1 is a special case wearing a rule's
clothes.
So it is a LOOKUP in authored/timing.json keyed <screen>/<element>, with the
census recorded beside it so nobody widens it later.
The period is 129 units -- the element's own group under the port's existing
model: last timed keyframe t=105 plus the authored exit_ramp_units of 24. No new
constant. 2.150 s at 60 units/s, 2.295 s at the ~28.1 fps the emulator presents,
against measurements of 2.12-2.34.
IT IS A CHOICE AND THE ALTERNATIVE IS STATED: restarting at the group's first
keyframe (t=6) instead of 0 gives 123 units = 2.050 / 2.189 s, also inside the
measured spread. Nothing separates them. t=0 is taken because it is where every
other group starts -- consistency, not evidence.
Verified the way the ring was, by bit-identity one period apart. 20 periods is
43.00 s = exactly 172 film frames: frames N and N+172 differ by 0-1/255, while
the control a quarter-second off (43.25 s) differs by 58.7/255. On the held boot
title the glow-box mean swings 26.0 <-> 37.7.
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.
