NATURAL MOVEMENT.EXPLICIT ENGINEERING.
Body movement is continuous. Game decisions need to be explicit. PhiMotion connects them through layers of pose, geometry, time and intent.
Explicit boundaries
The pose provider delivers joints, the recognizer decides actions, and the game bridge maps inputs.
Traceable decisions
Evidence and state transitions travel together. A recognized action and an accepted game command remain distinct.
Evidence with scope
Passing automated tests does not replace physical acceptance. Experimental paths and known limitations stay documented.
FROM CAMERA TO GAME.
Select a layer to follow the data.
Camera
Observe a frame containing body movement.
Capture & pose
Native frames to a provider-neutral joint model.
Calibration
Neutral stance and reference body scale.
Geometry & signals
Coordinates, normalization, temporal change and evidence floors.
Motion intent engine
A clear distinction between legacy, V3 and Demo Assist.
Game integration
Command mapping, expiry and duplicate suppression.
Native iOS runtime
Camera ownership and the Unity native boundary.
Validation & QA
Evidence layers from tests to human acceptance.
Known limitations
Current research limitations and outstanding acceptance.
THE ENGINEERINGUNDER THE PLAY.
Architecture, equations and implementation evidence. A technical reference for the people building PhiMotion.
Explore Engineering Docs↗