# Scooter: original static checkpoint (historical) Current implementation and corrected contracts: [scooter-live.md](scooter-live.md). The following records the earlier evidence boundary. 2026-11-02. Static source recovery only; **no live Scooter implementation or original gameplay verification**. User parked broad collision. Scooter cannot faithfully reuse only Jimmy's current body: original drive/steering depends on separately constructed wheel children. Primary was advised before runtime work and selected another gadget for the next implementation slice. Original EXE SHA-256 `f5281076e1a2492f2d61f87aae3f4544b6d0f535ebe33f9fbb6f78710fe1aea8`. `tools/binary/scooter.py` guards17 complete bounded spans,13 virtual bindings, 10 constants,4 strings and the always-false sprint predicate. Generated ledger `artifacts/scooter-contract/source-contract.json` contains exact VAs, PE offsets, lengths and hashes. For every code VA in this report, file offset is VA−400000. Data/table addresses must use the ledger's PE reader; do not assume this identity for an arbitrary PE. Supplementary instructions are in the same artifact directory. ## REA evidence and coverage Local `scripts/rea.sh`/Ghidra12.1.4 analyzed the generated copy `artifacts/uncontrolled-phases/rea/Neutron.exe`; originals were not executed. `rea-vehicle/01.json` recovered465220 with Evidence `ev_09ecf350c8705d5f9c1da5b444eb8cd027f64f4859713b29c9d04bc4c55c2bc8`; `02.json` recovered465830 with Evidence `ev_dbb6ac283387e14f08d527a750c14af44c52ed80c612c40393a5434a16589916`. Profile digest is `e1ad533d4cc0333c2136fe0894217de2d61feea098240326e78633f9e4ddcbf9`. Complete bundle and closed snapshot are retained.465220 pseudocode contains incorrect float/pointer/local aliases and loses some x87 scalar producers; the guarded instructions resolve the gates and arithmetic cited below. 421580 and412A90 returned explicit procedure-lookup/unmapped-file-offset provider errors. Initial exploratory437F90/43A120 (Jimmy routines, subsequently excluded from Scooter) also failed; `rea-native/` retains failures, empty export and closed snapshot. No unchanged failed request was repeated. The first sandboxed `rea-equip/` attempt saved only successful target-open metadata and no pseudocode/Evidence or closed snapshot before its worker ended; no success is attributed to it. Local static IPC allowance resolved the host restriction for the later complete batches without changing client configuration. ## Actor, construction and selection Inventory item4/raw mode4 is Scooter. Movement mode is a **separate vehicle state**, not Jimmy movementmode3. C3DJEEP constructor4211A0 calls412870→464B90; complete vtable4A2F8C, game interface+C0/vtable4A2AEC.4213F0 loads `omt\\scooter.omt` (string4EEF2C). Radius is150 at42128E via game110→471240; inherited factor is float.2 at412942 via4711E0. These are distinct from body friction; do not replace friction with.2. Jimmy game initialization423CE8..423DC1 lazily allocates6AC bytes, constructs 4211A0, and stores complete actor at Jimmy+A30 (game+970). Complete168→412A90 receives `(73,-30,3,3,1,true,true)` at423D58..75.412A90 constructs **four** C3D wheel actors through type33574845/459CB0 into the first4 of6 pointer slots complete578..58C and stores relative offsets in complete5A0+16*i. It also adds mutual collision exclusions3A8. The slots are initialized null in464C9A..BC. Thus the last2 generally remain absent in this constructor path; support code still scans6. Wheel collision/body scheduling and wheel-type implementation are not closed by this investigation. Panel4278D7 already closes and invokes Jimmy cleanup178 before174(4), as in [gadget-controls](gadget-controls.md). Item4 leaf4290B7 requires Jimmy+A1C companion. It hides companion+994 via58(true), requires companion gameCC true, sets raw4, copies companion root310/Euler328 into vehicle via16C/174, hides vehicle and children through complete174→421800, enables vehicle gameD0/214, then hides/disables companion gameD0/214. **This does not mount Jimmy or change controlled pointer directly.** Failed companion gates still continue to practice handling429297. Armed practice switches item9 to1 and loads VR05. Do not add an energy requirement: the reviewed equip leaf has none. Mount is a later Jimmy interaction callback:422F13..422FB9 recognizes target `C3DJEEP`, invokes Jimmy complete1E0, calls game118(vehicle game interface), stores Jimmy complete pointer into vehicle69C, hides Jimmy+A2C, adds Jimmy's vehicle collision exclusion3A8, selects `SCOOT` with E0(...,true), then refresh148. The callback's full interaction eligibility/caller and complete1E0 effect remain separate gates. Merely selecting the tile must not fabricate a mount event. ## Fields, input and apply Offsets here are **vehicle complete object** unless explicitly marked game. | Offset | Source owner | | --- | --- | |578..58C|6 child pointer slots;4 populated by this setup| |600/602/604|signed WORD front2/rear4/total child support counts| |610/618/620/628|acceleration700/deceleration1200/base maximum2250/current maximum1485| |61C|previous source scalar speed| |63C/640|steering wheel angle/applied yaw rate| |658/659|throttle/braking flags| |65D/65F|keyboard-turn/reverse-held latch| |650/654|camera mode/previous camera mode| |690/694|engine channel/base sample frequency| |698/69C/6A0|jump edge latch/mounted Jimmy pointer/animation clock| 464F60(100), called by base constructor, sets acceleration=100+600, deceleration1200, base maximum=100*4.5+1800=2250 and default maximum=base*.66. Vehicle game268/26C get/set scalar speed. Complete130→413A60 always returns false in C3DJEEP, so the inherited sprint branch is inactive and normal maximum is float1485. Mouse, controller and inherited AI/camera paths are not included in the pure keyboard projection. Input421880 rejects407060 true,475CA0 false or open gadget panel. Primary fire 509834 sets global4F8182; input then delegates465830. That input first copies current scalar speed into61C, clears analog throttle/brake flags and fetches mouse axes through completeF8. With mouseX0, keyboard Left precedes Right, adds/subtracts200dt to angle63C and sets keyboard-turn latch. With no turn key, that latch permits return toward0 by200dt, clamped at crossing. Angle caps±45. Nonzero mouseX uses2*dt*mouseX and clears keyboard-turn latch; inherited return does not necessarily continue after mouse release. Left/Right also accept analogX<−.5/>.5 through421C10/40. Forward predicate421C70 requires rear support count602>0 plus Up, primary fire, controller button509AC4 or analogY>.5. It adds acceleration700dt while below maximum and clamps there; at/above maximum normal no-sprint branch preserves speed. Backward421CB0 also requires602>0 and supports Down/analogY<−.5, with the source primary-fire/controller qualifications retained in instructions. First accepted backward call sets reverse latch: positive speed subtracts1200dt and clamps0; negative speed adds1200dt and clamps0. Subsequent held calls subtract1200dt, allowing reverse down to−currentMaximum*.4 (about−594). Braking flag659 persists through the continued-held path; release clears both braking and reverse latch. Forward executes before backward. These are dt-based vehicle increments, unlike Jimmy's fixed-per-callback Bubble throttle. Apply421580 calls412ED0→465220, which calls462520 first, then requires475CA0 and game210. It scans actual nonnull children and their game218, recomputing 600/602/604. Steering requires nonzero incoming horizontal live velocity and front count600>0. Scalar speed gives scale=min(horizontalMagnitude*.005,1); ordinary yaw rate640=frontCount*angle63C*scale (inherited AI uses2 instead). The dot between normalized horizontal velocity and rotated local forward chooses forward/reverse yaw sign; yaw increment is rate*dt. The drive-velocity rewrite at465594 requires **vehicle game218 AND total child support604>=2**. Missing/unsupported children do not imply support. Unsupported vehicle still publishes scalar speed but does not execute that rewrite. Supported scalar decay/turn drag/slope terms, normalized live/forward direction mixing and friction can change speed and velocity; the whole465220 span and Evidence are retained but no full numerical drive projection is claimed. The `drive_eligible` helper tests only its recovered eligibility gate. Jimmy's ordinary application formula is not equivalent to this routine. ## Mounted update, animation, sound and cleanup After vehicle apply,421580 with mounted69C calls Jimmy complete1AC(dt), handles the five standard jump inputs and copies vehicle root/Euler into Jimmy. Jump uses its own edge latch698: release clears it; held with latchfalse and vehicle support queues `(0,700,0)` through game28C, then sets latch. Airborne hold does not latch, so support can accept it later. This is pending velocity/impulse state, not an immediate Y700 live-velocity assignment. No mounted pointer takes a different stop/reset path421794; it does not run mounted jump/pose updates. Animation timer6A0 stores float(timer+dt), compares to **double.3**, and when greater selects Jimmy `SCOOTSTOP` for signed scalar speed<10, otherwise `SCOOT`, both E0(...,true), then clears timer. Reverse speed therefore chooses stop at this site. float32(.3) is already greater than double.3. Do not replace the threshold with.3f equality. No Goddard195-vertex morph binding was proven; [asset inspection](gadget-assets.md) and vehicle asset export retain that gap. 412ED0 starts positional looping SFX46 (`Scooter`) through4589C0 when vehicle gameCC and audio global696008 are true and engine channel690 is−1. It captures channel base frequency in694; later frames write a speed-dependent frequency, minimum7000. No direct energy debit42A920 was found in the reviewed equip, vehicle input/apply/update spans. This bounded result does not prove global energy policy for every interaction/caller. Cleanup178 raw4 jumps4281B3. If companion absent or companion gameCC already true it proceeds to common raw−1 return42882F without the full vehicle teardown. Otherwise it clears menu4B4, writes JimmyA20=.5 (consumer remains unknown), copies vehicle root/Euler back to companion, shows/enables companion D0/214, resets42AE90 clocks, removes Jimmy vehicle exclusion3B0, exposes vehicle children through completeD8→464F00, disables vehicle D0/214, destroys retained helper via complete164, stops engine690 and clears it−1. If mounted69C nonnull it additionally clears Jimmy action latch1E25 and4F8182, restores game118(Jimmy interface), raises Jimmy rootY by constant49FAD4, clears acceleration278/live velocity2C4, requests `RUN`4ECA64, exposes Jimmy+A2C (unless509A13), and finally clears vehicle69C. Every completed return sets raw−1. The exact elevation constant is intentionally left in guarded source pending the full dismount/body policy; no new cleanup Euler blend or Jimmy movement-mode reset was inferred. ## Camera and implementation boundary Vehicle camera completeEC→4130A0 runs at the end of465830; it uses camera mode650, previous654, global eye509A50, vehicle rotations/speed and native collision clipping. Default mode1 is set in464D1F and its source branch begins 413234; Down/reverse and camera-mode inputs remain separate concepts. Full camera branch arithmetic/obstruction ownership is unresolved, and using Jimmy camera439900 for Scooter would be a declared approximation. There is no proven complete camera contract here merely because source is retained. Practical next slice, in order: 1. Close C3D wheel child transforms, support/contact scheduling, source body properties and static VR05 eligibility; preserve actual4-child constructor. 2. Add distinct registered Scooter actor, spawned/mounted/control-owner state, child exclusions, mount eligibility and atomic cleanup handoff. 3. Port465830 keyboard and465220 full arithmetic with regression projections, then jump/pose/SFX46/camera. Preserve scalar/live/pending state separation. 4. Compare original mount/drive/jump/reverse/dismount runtime before claiming faithful playability. Native Windows comparison remains unverified. These dependencies make a movement-only Jimmy flag insufficient. Broad collision remains parked; no runtime source was edited by this investigator. Nine Python groups pass: identity/span/binding guards, spawn-vs-mount, real support gating, steering caps/release, rear-support throttle, brake/reverse ordering, jump edge, animation float/double boundary and bounded inputs. They validate source projections, not original execution or port vehicle behavior.