Files
Neutron/docs/checkpoint/README.md
T

50 lines
3.1 KiB
Markdown

# Architecture checkpoint
Feature expansion is paused. The existing port is a preserved baseline and a tool
for testing interpretations. This checkpoint connects original state ownership,
update order and lifecycle to the lab → VR04 → lab → outside route; it does not
require recovering every level or certify complete gameplay fidelity.
Start with [baseline](baseline.md), [coverage map](coverage.md),
[loop and motion](loop-motion.md), [script/state route](script-state-route.md),
[camera/audio/UI](camera-audio-ui.md), and [implementation plan](implementation-plan.md).
Core reports and [input/frame bridge](input-frame-bridge.md) have returned to
primary ownership. Follow-ups cover [lab registry](lab-registry.md),
[camera ray](camera-ray-predicate.md), [voice clock](voice-clock.md), and
[scene loader](scene-loader.md). All investigators have returned file ownership.
Primary owns integration/runtime corrections. [Exit review](review.md) records
checkpoint completion, verified changes and the next evidence gates.
Implementation continuation: [level-game lifetime](level-game-lifetime.md),
[retained character resets](retained-character-reset.md), and
[player phase implementation](player-phase-implementation.md). These supersede
the old-game-removal question and record the first C3/C5/C7 implementation chunks.
The retained-field continuation adds [property reader](retained-streamer.md),
[RETURN cleanup and full availability tails](retained-return-cleanup.md),
[player body/scalar boundary](retained-player-body.md) and
[companion/shadow resets](retained-companion.md). It corrects the earlier
availability-prefix interpretation and implements bounded route scalar carry.
Evidence labels used throughout:
- **Recovered:** static instructions, serialized original data, or a specifically
named isolated-original probe. Preferred image VAs and PE-mapped file offsets
refer to the hashed supplied binaries, not ASLR runtime addresses.
- **Inference:** an interpretation whose missing callers, ordering or filters are
explicitly listed. It is not promoted to fact because a replay looks plausible.
- **Implementation:** what this port currently does, including modern policies.
- **Verification:** state separately whether a source-byte check, managed test,
port runtime, isolated original component, or full original runtime was tested.
Earlier analysis documents retain useful evidence but can describe older
implementations. This checkpoint supersedes their architecture/priority summaries;
focused reports remain authoritative for their cited instructions/data. In
particular, movement mode1 reaches the airborne fall-through path, TSK writing is
recovered, and source per-level far planes are recovered; broad older statements
that those are wholly unknown are stale.
Checkpoint exit requires every requested core system to have an evidence anchor,
owner/lifetime, interaction mapping, baseline comparison, explicit unknowns and a
bounded next action. Completion means enough architectural coverage to execute the
plan, not complete disassembly or original gameplay comparison. Preserve unresolved
questions as gates on individual plan chunks, not a reason to block all work.