The 'never decompiled' ledger note was wrong: part_013.c:3059 carries the
ENTIRE master performance @004a9b5c as plain C (and @004ab430 is the full
replicant perf; IntegrateMotion sits between them). Reading it end to end
rewrote the movement-mode model:
- mech+0x2c is the entity MOVEMENT-MODE AlarmIndicator; +0x40 is its LEVEL
cell -- everything previously read as 'raw simulationState' is this
alarm. MECHDMG writes it DIRECTLY: half-gone right leg -> 4 GimpRight
@0x49c8fb, left -> 3 GimpLeft @0x49c926, leg destroyed while limping ->
9 @0x49c88f/@0x49c8c5, vital -> 9 @0x49c83c, gated by the real
InDeathTransition. The staged statusAlarm->mode 'promotion' was a
misconstruction -- retired; statusAlarm@0x714 is only the body-graphic
clip selector.
- The master perf's block 7 is three STREAMED mode-request counters
(+0x334 DefaultState / +0x338 GimpLeft / +0x33c GimpRight -- authentic
names, traced as consumed), fed only by creation/update records; landed
with ctor/Reset zeroes and the Reset mode drop.
- The duck driver moved to its authentic slot (counters -> duck -> limp
standup -> volume swap -> advance) and its gate is renamed
mobilityScale: +0x79c is the MAX LEG EFFECTIVENESS over the +0x7ac
roster (scales throttle, zeroes turn, gates duck), not a crouch analog.
- The advance dispatch is death-guarded (InDeathTransition before the
gimp/normal pick) -- and with mode 9 finally written on kills,
InDeathTransition and the camera director's death cut-away are LIVE.
Corrected identities recorded in MECH4.NOTES.md: +0x3f4 = REVERSE/BRAKE
flag (not airborne) with fwd/rev accel pick and gyro lurch kicks; 5-notch
throttle quantizer; RealMaxSpeed(0x15) one-shot send; @0049fa1c =
combat-effectiveness census -> +0x414; @0049fe80 = damage averages ->
+0x354/8/c; block 8 = move/collide with self-dispatched TakeDamage
collision damage + stagger clip 0x20; the instability accumulator and the
five ring buffers.
Soaks: duck cycles green from the new slot (3 full cycles, crash-sig 0).
The lifecycle kill-cycle conf crashes -- PROVEN PRE-EXISTING by a stashed
control build (identical 0xFC fault, EIP moves with the relink); forensics
in MISSILE.NOTES.md, broke unnoticed somewhere in 5.3.26..120.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
CydandClaude Fable 5
6da282738c