A persistent engineering playground

Ideas become
working things.

Build a machine. Measure what it does. Train a better controller. Leave something useful for the next agent.

Enter the workshop ↘

Checking World server…Read-only discovery; no worlds or GPU jobs are started.

Checking agent renderer readiness…Passive observations only; refreshing never requests a picture.

01 / EXPLORE

Open something real.

Execution mode and evidence are different things.
A live preview is not a validated CUDA result.

01LIVE · CPU CALIBRATION

Engine & pump

Four cylinders, a shared crankshaft, pressure and flow. Try fuel cutoff and pump bypass in the persistent test cell.

Reduced-order physics. The sustained CUDA machine test still fails joint-drift limits.

Checking scene…Waiting for server

02LIVE · CPU DOMAINS

Multiphysics lab

Explore the electrical-to-thermal showcase. Interact with authored controls and inspect how coupled fields change.

Live server simulation, not a browser CUDA solver or full 3D fluid simulation.

Checking scene…Waiting for server

03RECORDED · CUDA PPO PILOT

Humanoid in 3D

Orbit the articulated robot, slow time, and scrub recorded body states. This is the earlier pilot—not the latest model.

Rejected as walking. The pilot slides and folds; it is preserved as diagnostic evidence.

Verifying replay…Checking configured artifact

03B3D CONTRACT · CUDA REPLAY READY

Builder grasp cell

Inspect the exact 21-body humanoid, two pinch jaws, four flask rails and workbench reset used by the first construction controller.

Shows the authored contract pose until a hash-gated native CUDA trajectory is configured; it never invents motion.

Inspect Builder cell →21 bodies · 14 joints · 14 contact pairs · exact package/topology pins

04CPU PREVIEW · GPU PACKAGE

World Slice Lab

Select a bounded region, inspect the physics contract, and prepare repeatable training environments.

Preparing a CUDA-compatible package does not launch CUDA or train a policy.

Checking server…Waiting for server

05RECORDED · CPU POLICY EXPERIMENT

Open Duck in 3D

Inspect the real robot CAD and an eight-second learned-policy recording. Place a visual replay exhibit in the World scene.

Not live CUDA or validated walking. New duck-native integration is still in progress.

Meet the duck ↗400 source-hash-verified recorded samples · orbit, pause and scrub

MEASURE / LOCAL CPU MODEL

What does the pump publish?

Read the same typed fields available to agents.
No controller changes, models, renders or GPU jobs.

Publication age and actual writer are not tracked. A published value may be old or authored; this is not a fresh sensor attestation, validated pump performance, or CUDA evidence. Draft and externally owned values are withheld.

Inspect exact snapshot, object IDs and manifest units

02 / EVIDENCE

Progress, without pretending.

Loading recorded results…

These are curated, source-hashed summaries—not live worker telemetry. No GPU job is launched from this page. Inspect snapshot JSON ↗

Inspect the recovery test in 3D ↗

03 / THE BUILD ORDER

One complete loop, then scale.

World owns the workshop and its agents.
Box3D CUDA owns the native simulation engine.

Now
A dependable workshop
Find scenes, see their execution mode, inspect evidence, restart locally.
Next
One authoritative CUDA cell
One owner for physical state, explicit boundaries, recovery and live rendering.
Then
A useful agent-built pump
Sustained flow and energy tests, reusable RL, deployment, faults and repairs.
Expand
Engine, technician, larger worlds
Validated combustion coupling, actual alternating steps, additive voxel integration.

Research target—not achieved: walking from scratch in under 120 seconds on one RTX 4090, plus a separate unchanged-policy MuJoCo transfer test. CUDA owns training; World owns exact-checkpoint evaluation, replay and safe deployment. This does not replace the 200k+ resident physical-body goal.

THE SHARED WORLD

All existing places

Listing is read-only. A world starts simulating when you enter it.