NONLIMI

The validation layer for physical AI.

We build the layer that turns simulation into release evidence: a machine-checkable verdict on whether a change to an autonomous system is fit to ship.

A result you can reproduce, hand over, and be held to.

FIG. 01 · THE VERDICT

— the same input, the same answer, on the same machine

SUBJECTAUTONOMOUS SYSTEMS UNDER CHANGE

METHODDETERMINISTIC SIMULATION · RECORDED BASELINE

OUTPUTREASON-CODED PASS / FAIL VERDICT

NATURAL PREDATORTHE REGRESSION NOBODY CAUGHT

LICENCEAPACHE–2.0 CORE · SOURCE TO PARTNERS AS THE PROGRAM OPENS

01 · THE PROBLEM

Physical AI has no release process.

Software solved this twenty years ago. Write a test, gate the merge, ship on green. The evidence is produced by the pipeline, it is the same every time, and nobody has to be in the room for it to count.

Autonomous systems still ship on judgement. A demo that went well. A field trial that did not crash. A simulation job that someone re-ran until it passed. Each of those is an impression of safety, and none of them survives being asked to prove it — to a customer, to an insurer, or to yourself at three in the morning after an incident.

That does not scale with fleet size, and it does not transfer between teams. It is the bottleneck between a machine that works and a machine you can ship.

02 · WHAT WE DO

We make simulation produce evidence, not impressions.

FIG. 02

Deterministic verdicts

Same seed, same architecture, same answer. A result you cannot reproduce is not evidence — it is an anecdote with a chart attached.

— measured on same-architecture runs

FIG. 03

Reason codes, not red

A failure names what moved against a recorded baseline. “The build is broken” is not a finding. “Minimum clearance fell below baseline” is.

— the diagnosis, not the alarm

FIG. 04

Evidence that travels

Verdicts, reason codes and the runs behind them are artifacts you can hand to someone else. Designed to support the safety case you have to make — never a claim to have made it for you.

— a record, not a reassurance

PLATE

FIELD NOTE

RUN RECORD

REV D · CURRENT

03 · WHAT’S NEXT — LABELLED AS NEXT, NOT AS NOW

One engine. Everything else descends from it.

Everything above the line is direction, not availability. What ships today we publish in full to the teams we work with, item by item, including what is not in hand — we do not summarise it here, because a summary of a build state is how a build state starts drifting.

// NO DATES. COMMITMENTS WE CANNOT GOVERN DO NOT GO IN PRINT.

01

Nonlimi Cloud

Parallel execution, scenario generation, CI-native team workflow.

02

Evidence

Published run series with N stated. A reason-code taxonomy broad enough to describe what actually goes wrong.

03

Incident replay

Becomes a product job only when the sim-to-real evidence supports it — not before.

04

Nonlimi Market

A shared scenario and asset exchange.

05

Sovereignty

A deployment option under no non-EU corporate control.

04 · CONTACT

If release confidence is your bottleneck, we would like to hear about it.

We work with a small number of teams at a time, closely, and we would rather tell you early that it is not a fit than find out slowly together.

sp@nonlimi.com