Game engine & development

Build interactive systems without giving the model the world.

This public shelf covers simulation-first operations, spatial-temporal reconstruction, and bounded physical-AI development. The host runtime remains authoritative; a model, planner, or evaluator can observe, propose, and be measured without silently mutating the world.

Core rule

Simulation is a development and evaluation surface, not proof of hardware capability. A replay, mock run, or MuJoCo result can demonstrate a bounded contract while leaving real hardware, trained-model performance, and deployment readiness as separate questions.

Public development work

Three projects, three complementary roles.

Simulation, reconstruction, and physical-AI development each keep their evidence and authority boundaries visible.

Industrial operations simulation

CHAINSIGHT

C++23 · simulation-first public foundation

CHAINSIGHT models an industrial operations world for observe, validate, forecast, simulate, govern, commit, verify, and reconcile loops.

It is not an ERP, MES, WMS, TMS, safety controller, or physical-autonomy claim.

Spatial-temporal reconstruction

STRATA

Python / C++ · local-first public engine

STRATA reconstructs the same physical place across time from maps, photographs, terrain, records, geometry, and historical documents while keeping evidence, uncertainty, and competing branches separate.

A source or assertion is not silently promoted into historical truth.

Physical-AI development

OMNI-Q Weird Stuff Machine

Python · MuJoCo · public research work

A bounded development surface for objective-to-capability-graph planning, simulated bimanual table operations, vision, routing, verification, and evidence receipts.

The public evidence covers mock mode and simulation. Hardware performance, trained-VLA capability, and universal household behavior remain outside the claim.

Evaluation harness

Open World Model Harness

Public research software · replay and evaluation

A bounded evaluation surface for long-horizon behavior under partial information, with evaluator-held ground truth and host-owned world state.

Harness evidence is not a production deployment or universal model capability claim.

Development loop

Keep the roles visible.

The public development story is strongest when every step has an owner and an evidence tier.

01 · Observe

Bounded input

The system receives an explicit observation or fixture instead of an unexamined world snapshot.

02 · Propose

Model or planner

A model or planner produces a candidate action, capability graph, or explanation—not authority.

03 · Validate

Host-owned decision

Policy, environment rules, and the selected host runtime validate whether an action can be applied.

04 · Evaluate

Replay the evidence

Receipts, replay, and outcome analysis test the chain without upgrading a simulation into a deployment claim.

What is not claimed

No hidden engine, no universal capability.

This page does not claim a proprietary public game engine, a trained household robot, a hardware-ready controller, or a production deployment. It describes the public development and evaluation surfaces that are actually exposed.