Deploy Offline Motion
Treat the current repository documentation, deployment profile, launcher, and
runtime CLI as the source of truth. Discover their current locations and
interfaces before constructing commands; do not reuse paths or flags from a
remembered release.
Safety boundary
Separate no-action validation from any command that can publish control. Never
start an actuating runtime or change robot mode without explicit user
confirmation immediately before the action. State the exact resolved command,
target robot, artifact, motion source, fixture state, and stop method.
Workflow
- Resolve the supported robot contract, DOF ordering, runtime environment,
deployment profile, network interface, controller states, and stop path.
- Resolve the current no-action preflight from the CLI help, launcher, and
documentation. Verify artifact readability, schemas, providers, dimensions,
and configuration without starting the controller.
- Continue only when the preflight explicitly succeeds and evidence confirms
that no action publisher or robot process was started.
- Hold model, motion, profile, and runtime constant for the first active test.
Prefer repository-provided baseline artifacts before substitutions.
- Obtain confirmation immediately before the resolved actuating command.
- Observe every controller transition and stop on unexpected state or motion.
Custom motion
Resolve the current motion schema from the checked-in specification, loader,
and validator. Check required fields, shapes, ordering, units, rotations,
timestamps, finite values, and semantic plausibility. Validate the same file
with the deployed loader and test it in visualization or simulation before
real-robot use.
Run the bundled motion successfully before substituting a custom clip or custom model. Change one variable at a time.
Diagnose by stage
Localize failures in this order:
- package or image and target architecture;
- accelerator and container runtime;
- resolved profile, mounts, and network;
- model loading and execution provider;
- motion schema and preprocessing;
- controller readiness and state transition;
- policy timing and output validity;
- physical behavior.
Do not bypass a failed no-action gate. Report the last successful stage, first
failing boundary, exact resolved artifacts and interfaces, relevant evidence,
and whether any robot action was sent.
1---2name: deploy-offline-motion3description: Deploy and troubleshoot a HoloMotion policy for offline real-robot motion tracking. Use for deployment preflight, no-action validation, model or motion substitution, controller startup, and offline robot-runtime diagnosis.4---56# Deploy Offline Motion78Treat the current repository documentation, deployment profile, launcher, and9runtime CLI as the source of truth. Discover their current locations and10interfaces before constructing commands; do not reuse paths or flags from a11remembered release.1213## Safety boundary1415Separate no-action validation from any command that can publish control. Never16start an actuating runtime or change robot mode without explicit user17confirmation immediately before the action. State the exact resolved command,18target robot, artifact, motion source, fixture state, and stop method.1920## Workflow21221. Resolve the supported robot contract, DOF ordering, runtime environment,23 deployment profile, network interface, controller states, and stop path.242. Resolve the current no-action preflight from the CLI help, launcher, and25 documentation. Verify artifact readability, schemas, providers, dimensions,26 and configuration without starting the controller.273. Continue only when the preflight explicitly succeeds and evidence confirms28 that no action publisher or robot process was started.294. Hold model, motion, profile, and runtime constant for the first active test.30 Prefer repository-provided baseline artifacts before substitutions.315. Obtain confirmation immediately before the resolved actuating command.326. Observe every controller transition and stop on unexpected state or motion.3334## Custom motion3536Resolve the current motion schema from the checked-in specification, loader,37and validator. Check required fields, shapes, ordering, units, rotations,38timestamps, finite values, and semantic plausibility. Validate the same file39with the deployed loader and test it in visualization or simulation before40real-robot use.4142Run the bundled motion successfully before substituting a custom clip or custom model. Change one variable at a time.4344## Diagnose by stage4546Localize failures in this order:47481. package or image and target architecture;492. accelerator and container runtime;503. resolved profile, mounts, and network;514. model loading and execution provider;525. motion schema and preprocessing;536. controller readiness and state transition;547. policy timing and output validity;558. physical behavior.5657Do not bypass a failed no-action gate. Report the last successful stage, first58failing boundary, exact resolved artifacts and interfaces, relevant evidence,59and whether any robot action was sent.
horizonrobotics