From behaviorto evidence.
A 60-second tour of the HumanoidBehavior workflow: define a behavior, run a measured MuJoCo evaluation, replay the motion, and keep the result reproducible.
HUMANOIDBEHAVIOR / DEMO RUN MEASURED PATH
$ behavior pick-place@1.1.0
$ engine MuJoCo
$ seeds 42, 1337, 2026, 7, 99
→ validate specification
→ execute browser physics
→ persist measured result
✓ reproducible report ready
01 Define Reusable behavior contract
02 Version Explicit behavior revision
03 Measure MuJoCo physics execution
04 Replay Recorded motion frames
05 Report Metrics + validation + provenance
BUILT FOR A FAST TECHNICAL REVIEW
Demo → Evidence → Handoff A buyer can validate the core workflow, inspect the architecture, and move directly to the technical sale package.
01 See the workflow→ 02 Run the lab→ 03 Review the package→ 04 Talk to the owner
01 — THE RUN
One configuration. One trace. The demo mirrors the product's actual evaluation model: explicit behavior version, engine and seeds are attached to the measured result.
CONFIGURATION
Pick & Place Reference manipulation behavior used to demonstrate the measured execution path.
Behavior pick-place
Version 1.1.0
Engine MuJoCo
Seeds 5 explicit seeds
Execution Browser / WebAssembly
MEASURED RESULT · EXAMPLE VIEW
Evidence, not a static claim.
Each run keeps its configuration and measured output together. The values below are illustrative UI fields, not a claim of a live benchmark result.
5 runs
1.1.0 behavior version
MuJoCo engine
Replay motion frames
02 — REPLAY
See what produced the result. Measured browser runs can preserve motion frames for inspection instead of ending at a number.
MUJOCO · REPLAY FRAME 42 / 120
▶ Play ↺ Reset 1×
01 Configuration is retained Behavior ID, version, engine and seeds travel with the experiment.
02 Validation is separate Schema checks are not presented as physics measurements.
03 Provenance is visible Browser compute build and execution path can be inspected.
04 Results persist Completed experiment data is stored with the workspace record.
03 — ARCHITECTURE
A compact robotics infrastructure layer. The current MVP separates browser physics, API orchestration, persistence and the behavior contract.
01 Behavior layer Versioned task definitions, compatibility and success criteria.
02 Browser compute MuJoCo JavaScript/WASM execution for supported reference paths.
03 Worker API Cloudflare Worker orchestration with authenticated workspace access.
04 D1 persistence Experiments, results and product state retained for inspection.
Want to see the real run?
Open the live Experiment Lab, launch a supported benchmark, and inspect the resulting report and replay.