Claim 1
World continuity
One truck, one clock and one registry carry a mission from the
gate through the yard and the dock to departure.
- Shown today
-
A one-hour simulated shift of the truck mission ran 7
cycles and moved 32 pallets out. Every pallet is named in the
census, none are unaccounted for, mass is conserved, and no
deadlock was detected. Four runs with the same seed gave the
same fingerprint, and a replay matched byte for byte.
- Evidence
-
Campus mission record, 2026-09-11, item 6. The mission gate
passed 52 of 52 checks.
- Current limitation
-
The measured mission starts at the gate, not on the public
road. Sampled renders use simple box geometry, not finished
assets.
Claim 2
Sensor generation
Camera frames and their labels come from the same world state,
and the driver never receives ground truth.
- Shown today
-
Each frame carries instance IDs, masks, depth at 1/64 m
resolution, visibility and track IDs. Labels match the
world's ground truth to a residual of 2e-4 px, with zero
track ID swaps in the test. Ground-truth frames and sensor
frames are separate types, and a runtime guard refuses any
outgoing frame that carries a ground-truth field. In a scramble
test, a clean planner gave bit-identical results with ground
truth scrambled.
- Evidence
-
Label audit record, 2026-09-12. Sensor layer checks: 25 for
configuration and 31 for the ground-truth firewall.
- Current limitation
-
Sensor noise models are specified but not built. Camera
configurations are not yet calibrated. Transport separation
of sensor and ground-truth streams is not enforced at
deployment. Campus-render perception accuracy is not yet
claimed. Visualization overlays remain engineering
instrumentation, not production UI.
Claim 3
Virtual-silicon execution
Firmware and model weights run on virtual silicon inside the
loop, and each decision enters the simulation at a recorded tick.
- Shown today
-
Perception firmware images run on a SoC virtual platform. The
firmware lane is asked for a decision every 60 ticks (2 Hz),
and each decision is journaled with the firmware identity and
a stdout hash.
Neural network models run in the same loop, with their weight
hashes recorded at load. The RTL lane has passed 450 of 450
testbenches on its vector-in path.
- Evidence
-
Inference matrix record, 2026-09-12: 208 of 247 cells
produced, each with model and preprocessing identity bound.
RTL testbench record for the vector-in lane.
- Current limitation
-
Firmware operating point remains under evaluation. No camera frame reaches an
RTL decision yet, so RTL is not in the closed loop.
Claim 4
Closed-loop control
Each decision changes the vehicle, the vehicle changes the next
sensor frame, and the referee judges the result.
- Shown today
-
Four legacy factory exams re-hosted on the campus gave the
same verdicts as the factory scene in 3 of 3 comparisons,
with stop distances inside tolerance. Replay from the journal
reproduced the fingerprint in 4 of 4 cases. A decision that
arrives outside its freshness window is refused: in one test,
stale frames were offered 104 times and acted on 0 times. In
the forced case with a forklift in the trailer, the dock
interlock refused release.
- Evidence
-
Campus exam record, 2026-09-11, item 4. Decision freshness
record, 2026-09-11. Mission record, 2026-09-11, item 6.
- Current limitation
-
The actuated signal controller cannot see an exam ego, so the
graded exams declare fixed signals. No closed-loop pass rate
is claimed on held-out families yet. The driving gate does not
yet separate the five detector lanes it was run on.
Claim 5
Deterministic replay evidence
The same seed, scenario and build give the same run, and a
difference in one tick can be located by bisection.
- Shown today
-
A 144,000 tick run, which is 20 minutes of simulated time at
120 Hz, with 500 entities keeps 120 keyframes and a
hash-chained journal in 6.13 MB. When one pose was changed by
1e-9 at one tick, bisection found that tick in 10
comparisons. Injected 500 ms wall-clock stalls left the final
fingerprint unchanged. On the campus, state determinism
measured 0.000000000 mm. Nine math functions returned
bit-identical results over 10,000 inputs each across several
runtime engines and an independent reference implementation.
- Evidence
-
Simulation core record, 2026-09-08 (stall, registry and
keyframe tests). Campus integration record, 2026-09-11 (math
vectors and state determinism).
- Current limitation
-
Replay shows that the same inputs give the same run. It does
not show that the model matches a physical vehicle. Clock
alignment between GNSS, inference timestamps and recorded
video is not yet validated across runs.