Core runtime, events, and authority

The 120-byte base table contains slots 0–14.

Identity and state

getVersion, getModVersion, and isReady are the only calls allowed off the game thread. Registered RuntimeState owners may copy runtime/config state, including readiness, upstream generations, reload sequences, authority flags, capture counts, weapon identity, configuration revision and development-policy summary.

Native capture

CapturedTransforms copies up to 192 named local transforms with source/ destination indices and authority flags. NativeHandPose returns hand-in-weapon plus 15 finger-local transforms and a validity mask for each hand.

Registration and events

PAPER supports 16 consumers and 16 event callbacks. A consumer handle carries owner token, granted mask and provider generation. Events include FrameComplete, runtime/config reset, motion-catalog change, manipulation lifecycle and learned candidate completion.

Animation authority

Arbitration flags cover Arms, Hands, Weapon and combined ReloadPose. A nonzero lease expires after PAPER frame callbacks; zero persists until clear or owner unregistration. Authority coordinates an existing external animation owner—it does not submit pose/IK data.