Kinewright Wheels: the map

Kinewright is a house of motion engines, and Wheels is its second engine, designed to determine how a four-wheeled vehicle moves. This article outlines the plan for Wheels as it stood in October 2026, detailing what the engine does, what it takes from outside, the criteria and data it uses, and the order of stages and why. The article is a permanent record, with updates made on the r/Kinewright pinned post.

The engine creates motion state, not pixels, through physics-informed kinematic motion bounded by specific physical identities. It checks static balance, dynamically checked momentum and contact forces, and simulates on a named slice using a named dynamics provider. The engine is hardware validated on a specific hardware setup through a separate physical stack.

A drive that passes a kinematic or visual gate is not described as physically validated. The engine owns the shell, four wheels in a 2x2 layout, wheelbase, tracks, wheel radius, width, steering layouts, and the negotiation of manoeuvre-and-shell pairings. It accepts commands, determines native, adapted, fallback, or unsupported resolutions, and predicts answers before running the code.

The engine uses closed-form arc integration, a fixed tick, a versioned journal, and replay verification for determinism. It has honesty bounds based on two assumptions, reports them every frame, and includes mount points for rigid transforms. The engine does not claim to drive a robot from a browser and relies on intent contracts with expiration.