Robotics & simulation

Share scene state and decisions while keeping physical effects explicit.

Konjure’s first robotics example describes a workspace and an action proposal. It is a visualization and contract example, not a dynamics engine or a robot controller.

A useful boundary

An external system supplies observations with frames, clocks, sequence and provenance. A model or person proposes a scene change or action. The runtime validates its declared action and returns a receipt. A host adapter decides whether and how an external effect may execute.

This keeps simulation, human input and agent input on the same path without allowing scene authoring to directly drive a physical actuator.

Replay

Download an action recording from the playground. Its versioned steps contain explicit scene times and typed events. Use the same source or compiled document to replay it:

cargo run -p konjure-tools --bin kj -- replay /tmp/workspace.konjure /tmp/workspace-recording.json

The CLI emits sampled frames and receipts. It never repeats external tool or robot effects. Replaying recorded decisions is different from asking a model to infer new decisions.

Integrating simulation engines

Use Python or the C ABI to connect your simulator. Map units, handedness, rigid-body IDs and clocks at one boundary. Physics, collision detection, joint constraints, control rates and actuation remain owned by the simulator or controller.

ROS 2, OpenUSD and dedicated physics connectors are extension points. This release does not include a production ROS node, USD importer or certified robot control stack. Add one complete adapter with replayable fixtures before generalizing its interfaces.