Their run gives five replicates with no variation -- title->menu 3,3,3 and
EXTRAS->menu 2,2 -- while every differing value comes from a different ordered
pair, and the same origin gives different values to different destinations. The
origin constrains; the ordered pair determines.
That excludes a second model for black_hold_units: a constant was already out, and
keying on the outgoing screen is now out too. Only an ordered-pair key survives,
needing a measured value per pair.
Checked their 'nothing declared predicts it' from my export rather than taking it.
Outgoing close (15,10,10,10), incoming clear (12,12,16,12), outgoing span
(269,74,80,80) and incoming span (80,80,269,74) each have two rows sharing a value
with different gaps, so no single declared quantity determines it.
Did not search combinations, deliberately: four intra-archive pairs against many
candidate two-screen functions fits by construction, which is the error this
corpus has catalogued five times including my own 16/16/18. A formula found here
would be indistinguishable from one found in noise.
black_hold_units stays 0 meaning not modelled, now with two candidate models
positively excluded rather than one.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
Their measurement orders the four gaps by the screen being LEFT: menu 0 and 1
frames, EXTRAS 2, title 3. Direction, button and incoming screen are each
positively ruled out -- the same pair both ways differs, (B) gives 0 and 2 while
(A) gives 1 and 3, and an incoming menu takes 3 from the title and 2 from EXTRAS.
That resolves the escalation I raised: a uniform value is not merely unsupported
but excluded, so 0 is no longer one option among several. It is the only honest
uniform choice, because it models the gap as absent rather than as constant.
black_hold_units is unchanged at 0; its justification is replaced.
And my own rule is now refuted rather than unadopted. Gap plus the incoming
screen's opening black-clear held at 16/16/18 on three transitions; their fourth
gives 16, 14, 16, 18, and decisively the two transitions with the same incoming
screen have different gaps, so the incoming screen cannot determine it. A fourth
point did to a three-point fit exactly what it should.
Not keying per outgoing screen: three screens with one value each restates the
data, which is the objection I raised against my own 16/16/18. BLOCKED row
rewritten to ask for a second value on any one outgoing screen.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
They answered ask #2 -- the gap is deterministic, not a load -- and held me to
re-stating the choice against four measurements (0, 6, 4, 6) rather than the three
it was made on. That is my own standard for check-all's stale allowance turned
around.
The arithmetic moved against 0: it costs 2.0x the best fit on four measurements
against 1.7x on three, and is now the minority outcome, wrong on 3 of 4 where a
uniform 6 is wrong on 2 of 4.
Still 0, because the reason was never the fit -- it adds no black the game does
not have, and is measured-correct for a real transition rather than for an average
of them. Picking 6 because it appears twice is choosing a mode from four samples
when their finding is that a rule exists and nobody has found it.
But one leg is gone and is not being kept quietly: part of the case for 0 was that
the quantity might be machine-dependent and unauthorable. It is not. That removes
an excuse without supplying a value.
Added a tripwire: if the gap is non-zero in most transitions and no rule emerges,
omitting a real quantity stops being caution and becomes a different invention.
The port is wrong by 4-6 units on three of four known transitions and the why now
says so.
Also records as settled: the outgoing ramp is the declared final ramp, my {8,10,10}
against their measured multiset, two independent routes.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
The Decoder measured the black gap on three transitions: menu->title 0 units,
title->menu 4, EXTRAS->menu 6. Not a constant, and 9 was outside the range
entirely -- wrong for all three by up to a sixth of a second of black the game
does not show.
Did not take the best-fitting value. A uniform 4 minimises total error (6 against
0's 10); that is fitting three samples. 0 has a reason that is not a fit -- it
adds no black the game does not have, the tie-breaker input_during_transition
already uses, and it is measured-correct for one real transition. The error is now
a missing gap of at most 6 units on two transitions rather than an invented one of
up to 9 on all three. Boot artifact unchanged at 0.0009% differing.
Their EXTRAS run vindicates the earlier refusal: B from EXTRAS goes black for two
completely empty frames, so the two-line change I declined would have been wrong
for two of three transitions.
Also: the declared final ramp is confirmed from my side (title 8, main_menu 10,
extras 10 -- their exact multiset), needing no constant. And exit_ramp_units
defaults to 24.0, the number HANDOFF told me to author and I refused, on a branch
that cannot execute: 866 keyframes across 16 screens, 0 untimed.
And origin/main is the stale era -- verified 0 145 left-right, tip 2026-08-29,
still carrying the pre-fix association. The per-iteration merge has been a no-op
for days, its 'Already up to date' reading as 'I am current' while meaning 'main
has nothing'.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
Ask #1 measured: held at the title with no input the plate oscillates ~23 cycles
per window with no decay and NEVER goes off -- floor 159 thresholded pixels,
pulse bottoming at 714. A glow alone cannot do that (0 -> 80 -> 0); a steady base
plus a pulsing glow can, and 714/1520 are base-only and base-plus-glow.
The port already had the base right: ptbtn00's fade to 0 at t=244 is its EXIT
ramp, and while held the base sits at alpha 255. The glow was missing.
The defect was in the renderer, not the entry I deleted on 2026-08-29. _draw
treated a looping record like a focused one -- drawn INSTEAD of the base, which
is right for a focused button and wrong here. I deleted the right thing for the
wrong reason. A looping record now draws OVER the base and the entry is restored.
Rendered: 95.68 base only, 115.52 at peak, period 1.980 s against a declared 120
units = 2.000 s, ratio 0.990. Visible on the boot path; not under --screen
--overlay, where a static overlay poses at its arrival by design.
Authored in UNITS on their instruction, with their three limits verbatim: one
boot, does not distinguish boot from attract title, and 714/1520 is not an alpha
ratio so no duty cycle is inferred.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
1. --time= was silently ignored on any screen with a settle window >= 30 units:
pose_at overwrote the requested instant with settle_instant. ScreenView.frozen
now marks an explicit instant and skips both clamps.
2. press_start's settle window was [0,214] -- the dead stretch BEFORE the plate
exists -- so its settle instant was t=107, where the element is alpha 0. The
exporter now rejects intervals in which nothing is visible. title keeps
[160,236], the interval the Decoder's draw stream confirmed.
3. My authored looping_focus_records entry for press_start/ptbtn00 drew a dim
focus record INSTEAD of the plate's own sprite: max 0 vs max 252.5. Deleted --
an authored guess that overrides a decode with a worse answer is removed.
4. verify-capture passed --time=5.9617 for the title and it was never applied.
Every title figure it has printed, including the 0.26% quoted to the Decoder,
was measured at the settle instant under a note claiming t=357.7. Both rows now
pose by omission and the note matches. title is 0.21% honestly; splashes
unchanged at 0.01%.
The boot's end artifact now contains the plate (region mean 95.7 vs 33.6).
Corrects last iteration's BLOCKED row, which had the entry's effect backwards.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
Their ARM=early disclosure (~40% silent trigger loss) makes every draw-stream
figure n=1. Exactly one port constant depends on one: the black hold. Three of
its supports have moved -- the 105-frame count they revised to 114, the 2.231
corroboration they retracted, and a run-average rate now known to drift 33%.
Redone on their corrected segments the two runs give 8.95 and 6.71 units, not
one number: overlapping +/-1 error bars are not agreeing central values when one
frame is a third of the quantity. Range ~6.5-9.2, port at the top.
Value UNCHANGED and proposed rather than adopted -- it would be my arithmetic on
their instrument. Filed with the single run that would settle it.
Also checks their statistics: per-boot excesses reproduce exactly, and their
2.3 sigma uses population SD where sample SD gives 1.89 -- cutting against their
own concession. Neither framing reaches significance.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
Counting indices/4 lands every transition where the export's declared alpha>0
count changes, within a half-open boundary. Their quad counts (1/2 publisher,
3/6 developer) also reproduce exactly when restricted to sprite-bearing
elements -- independently confirming the layerless backdrop is absent from the
batch they log.
Refutation: their drift explains the corpus 4.1% in SIGN but overshoots in
magnitude 2.4x (predicts a 1.369 ratio, corpus shows 1.278, declared 1.214).
The drift was measured in their container and the 4.1% belongs to a different
instrument -- the same transfer I just got wrong with build 4.
Guards keyframe_units_per_second at the constant itself: 60 is the game's
logical rate, not a frame rate, and the 33% drift is not evidence about it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
The Decoder measured both splashes over 3 cold boots: publisher t=0..255,
developer t=0..210, the developer agreeing with wall clock to 1.1%. The port
emits each declared value plus the 9-unit black hold, exactly. No code change.
My error was the generalisation, not the arithmetic: build 4 is the title, whose
exit is caused from outside its timeline, so it holds; a splash's exit is caused
by nothing, so it plays out. I used the one boot screen the port is unaffected
by to overturn the two it governs. Declining to scale by 9x while adopting the
conclusion that implied was half a caution.
Also refutes their two splash boundaries as not comparably anchored: 2.237 vs
2.414 units/frame in one boot, and the publisher has a glow symmetric with the
developer's three.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
The Decoder measured build 4's top-level clock stopping inside [160,236]. The
exporter computes title's settle window as [160,236,198] from the file alone.
Same interval, two independent methods -- the first evidence for the settle
instant that does not come from our own renderer. ptcopyright reaching alpha
255 exactly at t=160 agrees from a third direction.
Corrects a claim in three places: timing.json, flow.json and boot.gd all said a
screen's dwell IS its keyframe group and the port reproduced 'the disc's own
pacing'. Build 4 declares ~120 presented frames and dwelled ~1100. The decision
to hold zero extra stands; the claim that it was faithful does not.
Checks their two declared spans against the file: both exact, with a 106-vs-105
interval-convention quibble that changes nothing.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
THREE THINGS FROM THE DECODER, one of which I am not taking.
REFUTED: "the developer splash is one composited quad, the bounding box of the
three logos". The observed quad is 525x259 at (378,155). The three logos'
bounding box is 500x421 at (390,164) -- a 259-tall quad CANNOT contain them, and
palogo_anima alone starts at y=449, thirty-five pixels below that quad's bottom
edge. The observed quad matches the union of gamearts_eff and seta_eff, 521x261
at (379,154), to about four pixels in every dimension -- and both of those are
TRANSIENTS my own census flagged, dark by t=45, so a frame containing that quad
is a build-in frame rather than the settled screen. I cannot see their draw
stream, so I sent the arithmetic rather than a verdict, and the port keeps
drawing three: I will not stop drawing an element on a claim whose stated
identification excludes that element from its own bounding box.
THE BLACK HOLD IS 9 UNITS, NOT 12. I authored 12 from Q7's luminance plateau of
0.17-0.23 s, supported by the menus' transition quad. The Decoder counted
SUBMITTED QUADS instead -- luminance cannot separate the outgoing fade's tail
from true black. Four frames with no sprite quad at all, at 2.284 units/frame
derived from the disc as its own clock, gives 9.1 units = 0.152 s (6.9-11.4).
That overlaps the luminance figure only at the top, and the true black is SHORTER
still since both boundary frames carry picture. My 12 was supported by analogy --
a different screen's quad on a different path -- and a number that fits by
analogy loses to one measured in place. verify-dwell's bound moved with it; both
screens still agree.
THE TITLE'S SWEEPS LOOP. The oracle shows the quad oscillating over its whole x
range and resetting hard, one reset in the first title dwell and two in the
second. The loop-length field could NOT have settled it, correcting a hope I had
stated: both records declare exactly their last keyframe time, slack zero, and
"loops at 600" and "runs once for 600 and stops" write the identical header.
Verified on the two sweeps' LCM, since their periods differ: 600 and 720 realign
at 3600 units, mean diff 0, against 0.438 at half that.
Scoped to the title. The menus declare the same lengths but the oracle
measurement is of the title, and my own weak evidence points the other way there
-- best match with the sweeps off-screen, three times worse mid-screen, against a
73% on-screen duty cycle if they looped. Two weak signals in opposite directions
is a reason to scope, not to pick.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
I carried this as "0.03 s outside a composite bound, probably a property of the
bound rather than the game", and the Decoder agreed. Both wrong, and the way it
was settled is the point: I stopped reasoning about the bound and filmed the
transition.
At 0.05 s the port fell straight out of the publisher's fade into the developer
logos -- mean 5.06 -> 0.32 at t=4.20, then 5.65 at t=4.25. NO BLACK FRAME AT ALL,
where the oracle measures a 0.17-0.23 s pure-black plateau (HANDOFF Q7). The
bound was fine; the port was missing a fifth of a second of black, and had been
since P3.
Authored at 12 units because the boot path has nothing to read it from:
publisher_logo and developer_logos each carry a single palogo_eff0, a 1280x720
primitive with ONE keyframe at t=0 -- static, not a transition ramp. The menus'
quad declares black for 12 units and 12/60 = 0.200 s sits mid-range, so the
number is the disc's where a screen has one.
Filmed after: t=4.25, 4.30, 4.35, 4.40 all at mean 0, then the developer logos at
4.45. publisher interval 4.26 DIFFERS -> 4.47 agrees; developer 3.62 -> 3.73,
still agrees. Settled-frame comparisons untouched, as they should be.
THE LESSON IS THE SHAPE OF THE DISMISSAL, NOT THE NUMBER. "A 0.03 s miss against
a bound composed from two measured ranges plus jitter slack is more likely a
property of the bound" is plausible, was accepted by both of us, and was wrong.
The composite bound is why the miss looked small -- the underlying gap was 0.2 s
-- and a plausible explanation for a small number is how a real defect stays
hidden. The film cost one command.
Also recorded: the Decoder has reproduced across two build-ins that the console
NEVER draws ptlogo_back2eff3 (0 draws against ~5 expected), with sampling phase,
invisible draws and position error all ruled out -- but WHY is not established,
and nothing in eff3's record differs from its neighbours. The port keeps drawing
it, deliberately: dropping an element the disc declares on a measurement with no
mechanism is authoring a behaviour neither agent can derive, and nothing this
port gates on would notice, since the flashes live only in the build-in and
verify-capture compares the settled frame.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
The Decoder found it in the format: a nested record is itself a RATC bundle and
its header's +0x08 is the LOOP LENGTH. A record's keyframes need not fill it and
the slack is a hold at the final pose, so ptbtn00f is 105 units of ramp inside a
120-unit cycle -- the glow rests dark for 15 units. The five ptbtn0Nf records
fill their 120 exactly, which shows the slack belongs to that record and not to
the format. Disc-wide over 1781 timed nested records: 92.3% declare exactly their
last keyframe time, 7.7% more, 0 LESS -- the falsifier never fires.
THE DECISIVE TEST USED THIS PORT'S NUMBER. Both candidates need the same emulator
pacing factor, and the ring measures it independently: declared 120 -> 2.177 s ->
1.0885. 105 units needs 1.211-1.337 to reach the measured 2.12-2.34 s, which
EXCLUDES it; 120 units needs 1.060-1.170, which CONTAINS it. Two different
elements in different bundles, separate runs, tied only by both declaring 120.
My three readings in order are the useful record: 129 (105 + the since-deleted
exit_ramp_units) fitted the measurement for a reason that evaporated; 105 (the
group length) I shipped knowing it was 17% short; 120 is decoded. And the
123-vs-129 pair I once called unseparable STRADDLED the right answer without
containing it -- the sharpest argument I have seen against treating "two
candidates, nothing separates them" as if the truth must be one of the two.
Verified bit-identical 120 units apart (mean 0), 0.061 at a quarter, 0.888 at
half. Still authored because the pinned tag does not expose +0x08; delete the
entry the day a tag does.
THEIR rest() FLAG, CHECKED RATHER THAN ASSUMED: they warned a focus record is the
kind of element rest() mishandles. Censused -- 34 focus-record elements, only 2
with a varying alpha, both ptbtn00f, whose rest.alpha of 80 IS their peak,
exactly the pathology described. The port does not hit it because the plate draws
through the loop path, and the other 32 are constant-alpha so rest() is safe.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
BLOCKED said the record-layout change touches five things: pose_at,
settle_units, spin_period_units, exit_ramp_units and the plate. I checked two,
reported that, and did not work the rest of the list.
`spin_period_units` required "the first timed and the second untimed". Under the
corrected layout the ring reads t=0 rot=0 and t=120 rot=360 -- both timed -- so
the rule returned 0 and THE FOCUS RING STOPPED SPINNING. Nothing reported it: a
period of 0 is a legal "this element does not spin".
Rewritten to take the SPAN between the two poses: 120 - 0 = 120 units, the same
number the old rule produced, which is evidence the corrected layout is
self-consistent rather than merely different. Verified the way P5 verified it,
by bit-identity one period apart on the ring's own 60x60 box so the ptloop sweeps
cannot confound it: 0 at +120 units (twice), 8.61 at a quarter period, 8.88 at
half.
Three wrong instruments on the way, and the sequence is the lesson. A whole-frame
`max` saturates on one rotating edge (adjacent frames scored 131 with a mean of
0.022). A live --menu filmstrip jitters by up to a frame, which is ~3 degrees of
ring. And a whole-frame comparison is dominated by the sweeps, which move 480 px
over one ring period. `--focus=<id>` was added so a --screen run can draw a focus
record deterministically, which is what made the check reproducible.
THE PLATE'S PERIOD IS NOW 105, THE DISC'S OWN GROUP LENGTH, and it disagrees with
the measurement. The ambiguity the entry carried is gone -- it used to say the
cycle might restart at t=6 rather than 0 and that nothing separated them; the
group now runs t=0 to t=105, both at alpha 0, and there is one reading. But 105
units is 1.750 s, or 1.906 s scaled by the factor the ring shows between its
declared 120 and its measured 2.177 s -- about 17% below all four corpus timings
(2.12 / 2.19 / 2.34 / 2.31). The old 129 gave 2.34 s, at the top of the range,
which is why it looked right.
129 was the last timed keyframe plus exit_ramp_units, and that constant is
deleted. A period built on a constant that no longer exists cannot stay even
though it fitted better, so the port ships the disc's number and says it is
wrong. Verified bit-identical 105 units apart, 0.83 at 30 units.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
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.
