# QVM57312 active-state movement and actual main caller

This batch completes bounded RE-537–539 / F-262–264 by evaluating the movement body selected when query state220 retains bit1024. It extends [shared query/main state](QVM_MAIN_QUERY.md), [friction](QVM_FRICTION.md), [command scaling/acceleration](QVM_ACCELERATION.md) and [continuous slide](QVM_SLIDE_REPEATED.md). No original executable, full QVM, native collision, physics or rendering executes.

Reproduce with `python3 scripts/analyze_qvm_active_mode.py`; validate with `python3 scripts/test_qvm_active_mode.py`. The [machine report](qvm-active-mode.json) contains the complete57312–57713 instruction partition, initialized configuration words,66 standalone fixtures and12 main chains. The evaluated body stops at57712 before the void PUSH/LEAVE epilogue, after applying the requested57714 child. Native responses remain supplied. The report occupies1730167 bytes in ordinary Git; assets are unchanged.

## ACTIVEMODE-001 — Live friction, command scale and wish-vector overwrite (RE-537)

Mode57312 first calls39988 friction against current PS/global state, then40397 with the actual command pointer FRAME+4. Both children return complete shared memory. File-backed initialized words include21228=10 for the later acceleration request; these words are supplied configuration, not proven immutable or current runtime values. Friction retains its earlier recovered speed/drop/override policy. Main fixtures consume the clock's actual float timestep.

The64-case standalone grid varies commands(0,0,0), (1,0,0), (−128,127,1), (0,127,−128), plane0/1, two initial velocities, stationary fraction1/0.5 and clear/contact slide records. Two extra controls supply forward-basis Z0.5 and right-basis Z−0.25. Other supplied basis vectors use planar forward(3,4,0), right(−4,3,0); these deliberately finite inputs do not prove native input normalization or legal gameplay domains. Existing friction and scale formulas independently predict the child outputs.

The initial wish construction combines scaled forward/right and up input, but the subsequent plane branch replaces the whole vector: with plane0 only scaled right remains, and with plane1 scaled forward plus right remain. Direct up addition therefore does not survive this branch; up can still affect command normalization/scale. Forward input then replaces Z with +70 when positive or −70 when negative. With zero forward, basis Z can still supply a vertical component, as the two extra controls demonstrate.

Finally57549–57576 zero wish X/Y and PS velocity X/Y. The mode normalizes only the remaining vertical wish, then requests40275 with that speed and coefficient21228. Thus the horizontal friction result is discarded before acceleration, while friction's current vertical velocity remains live. Zero root skips normalization and preserves exact source float signs. This documents numeric source behavior without assigning a complete gameplay name to the mode or its flag.

## ACTIVEMODE-002 — Actual acceleration, stationary query and gravity-off slide (RE-538)

Actual40275 receives the live mode-local direction pointer and float-word speed/coefficient arguments. Its projection, positive gap, acceleration amount cap and all resulting velocity words are checked independently. The mode then issues a stationary hull trace: start and end both point at current PS origin, using current frame bounds, entity7 and mask65537 in these fixtures.

Supplied fraction below1 requests5123 with string pointer55142. Fraction1 skips it. Logging effects remain omitted; this call is not treated as a state reset, collision result or movement cancellation. Mode57312 proceeds to57714(0) in both cases. That child evaluates the recovered continuous slide with gravity disabled, current velocity/origin/plane/touch/impact state and ordered supplied native records. Clear and repeated-contact outputs are independently predicted, including conditional contact registration and solver exits.

No60091/59710 step wrapper or41768 gravity tail is attached to this mode. Its own final state is the actual57714 child output. Native stationary/slide record consistency, side effects and legal collision domains remain unverified.

## ACTIVEMODE-003 — Reached query/event-to57312 handoff (RE-539)

Twelve main chains vary acquisition/existing active/gated cases, flags32/160 and clear/contact slide patterns. Actual clock/timer and54981(0) run before the recovered query; newly acquired state evaluates event23 and its queue writer before routing. An optional57312 effect runs after main CALL54422/POP54423, before the caller continues at54424. Other mode paths never receive these effects, and existing no-callback main reports remain byte-identical.

Four chains select57312 and execute its complete bounded child composition. Six flags160 controls select41768 by higher priority and retain that mode's established effects. Two flags32 feet-hit controls suppress the query and request55465 with omitted effects. Four acquisition chains emit numeric event23 before either reached movement mode; their queue/anchor/state outputs survive movement. Existing active-state cases do not emit a second acquisition event.

This batch does not yet combine the query/57312 path with actual posture/ground/nested-ground-action environment producers. Ground, basis, bounds and native records are still supplied in these main fixtures. Other alternative movement bodies, main prefix/suffix, logging/event consumers, complete53418/scheduler and macOS/Linux Rust/Bevy/Solari runtime behavior remain open.

## Validation and next tasks

Eight new tests cover all66 helper/wish/acceleration/slide fixtures, discarded horizontal state, signed input and fixed vertical speed, direct-up overwrite and nonzero-basis-Z controls, stationary pointer/bounds/mask/logging priority,12 reached/skipped main mode handoffs, acquisition queue order/persistence, initialized-word provenance and source/scope limits. All687 tests pass. Prior friction, main-contact and main-query reports regenerate byte-identically; the new report reproduces twice byte-identically. Storage/filter, documentation links and whitespace checks are recorded in the ledger.

RE-536 remains open for broader alternative modes, combined producers, native behavior and runtime work. RE-540 tracks55465/41848/43626/42838, combined posture/ground/query/57312 ordering, original reference traces, native collision/legal domains and remaining main/scheduler/consumer/platform scope. See also the [whole-project progress estimate](../PROGRESS.md).


Follow-up: [flagged55465 movement](QVM_FLAGGED_MODE.md) evaluates the relevant40966 entry impulse/command-byte effects, bit16 bypass, ordinary wish/inline clip/slide and measured resource at the actual main branch. Other bodies/native/combined/full runtime scope remains open.