Skip to main content
Malformed state/history JSON is ignored by the model’s readiness gate. An accepted command does not prove that its values form a valid observation. Validate shape and finiteness before sending and respect the string-length limits. For diagnosis, log the release, prediction counter, executed-action count, camera capture indices, sampled state indices, and command/reply timestamps. The server pairs arrival order, not capture metadata. A network connection with no errors can still carry temporally misaligned observations. For a minimal support case, start with the synthetic example. If it passes while a rollout fails, inspect the observation/history adapter before changing the policy or its normalization.