Files
Neutron/docs/checkpoint/README.md
T

4.9 KiB
Raw Blame History

Architecture checkpoint

This records the completed architecture checkpoint. 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, coverage map, loop and motion, script/state route, camera/audio/UI, and implementation plan. Core reports and input/frame bridge have returned to primary ownership. Follow-ups cover lab registry, camera ray, voice clock, and scene loader. All investigators have returned file ownership. Primary owns integration/runtime corrections. Exit review records checkpoint completion, verified changes and the next evidence gates. Implementation continuation: level-game lifetime, retained character resets, and player phase implementation. These supersede the old-game-removal question and record the first C3/C5/C7 implementation chunks. The retained-field continuation adds property reader, RETURN cleanup and full availability tails, player body/scalar boundary and companion/shadow resets. It corrects the earlier availability-prefix interpretation and implements bounded route scalar carry. The next C3 continuation is control phases, backed by uncontrolled player, physics eligibility and cutscene preparation. REA setup records local Ghidra/JDK and Evidence/snapshot use.

C4 continuation: sphere response, ceiling wrapper and physical re-registration. The source kernel is isolated/probed; live capsule replacement remains gated. Shared camera handoff records the next C5 state correction. The next C4 chunk adds grid traversal, contact/material/friction ownership and dispatcher/body component probes. The source dispatcher is implemented and compared with isolated original outputs; whole-body/live integration and special contacts remain gated. Independent review records corrections and remaining limits. The ordinary-body implementation composes the ten numeric references and enables the static subset in VR04. Its source contract closes phase/radius fields; implementation review preserves remaining dynamic, special-contact, initialization and modern noclip/render boundaries.

User-directed gadget continuation is in ../gameplay/gadgets-implementation.md. It supersedes older inferred gadget names: raw mode0 is Bubble, menu item3 is the combined shrink-ray/jetpack and its normal equipped mode remains−1. Numeric collision findings remain valid independently of those old labels.

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.