phimotion
Docs KO
phimotion
FIND YOUR NEXT MOVE
YOUR BODY. YOUR PLAY.KO
Browse documentation
ENGINEERING DOCUMENTATION

Validation & QA

What each evidence layer establishes, and what it does not.

IMPLEMENTEDSOURCE REVIEW / 2026.09.09

Evidence layers

Source review
Confirms that types, gates, state transitions and tests exist. It is not execution evidence.
Automated / synthetic
Checks deterministic behavior for defined inputs. It does not represent the distribution of real human movement.
Editor integration
Can exercise the recognizer, bridge and game controller together. Synthetic input must remain labeled as such.
Device runtime
Export, signing, installation, execution and camera state each need direct evidence. Process liveness alone does not establish correct gameplay.
Physical acceptance
A person’s actual performance and visible outcomes are assessed through a separate protocol.

Evidence used here

Motion, provider, image-geometry, V3 action and Runner bridge test sources were inspected together with the current-state documents. Checkpoint records contain historical automated results and known failures. Unity tests were not rerun while building this site; historical counts are not presented as fresh passes.

Record recognition and action separately

Recognized intent, command receipt, game acceptance or rejection, and observed controller action start should be recorded separately to locate failures. A machine event must not automatically create a label asserting that a person performed an action.

Outstanding evidence

The supplied gameplay clip documents a prototype demonstration. Physical acceptance for the current candidate and release approval still require their own evidence. Read known limitations before defining the next validation scope.