See it work · representative traces

Watch it catch a hallucination.

A confident, plausible, wrong claim — and the grounding check that refuses to let it reach your systems. Same check, three kinds of work. Pick one and watch each move.

Representative traces of the grounding check — switch scenarios, or press Replay to run one again.

grounding-trace · trajectory_handoff.dat
TASKverify insertion burn → trajectory_handoff.dat
01Ingesthandoff received

Read the propulsion handoff — the impulse value from the upstream module, with the unit it was declared in. Nothing fetched from outside your perimeter.

02Draftmodel judges meaning

The model sets up the burn from the supplied number:

“Insertion impulse 4.45 — computing burn, assuming newton-seconds.”
03Groundcode checks a closed fact

Before the burn is allowed to stand, check the unit the upstream module actually declared for that value.

04Mismatchunits mismatch caught

The source declared pound-force-seconds. The draft assumed newton-seconds. Same number — roughly four-and-a-half times the force.

N·sassumed → declaredlbf·s
05Haltfail-closed

It refuses to compute a burn on mismatched units — the exact class of error that has ended real missions.

produced_by units.verify
decision dimension_mismatch
reason declared unit ≠ assumed unit
06Re-groundgrounded in declared units

Convert using the unit the source actually declared, then recompute the burn from there.

converted 4.45 lbf·s → 19.79 N·s
07Verifydimensionally consistent

The recomputed burn is checked for unit consistency end to end. This time it holds.

decision burn_computed
basis declared units, converted
verdict verified
08Emitrecorded with provenance

Released — with the unit provenance of every value on the record.

“Insertion burn recomputed on the source’s declared units.”
What you just watched

Five guarantees, in eight steps.

The model can be wrong. It proposed something plausible the source didn’t support — exactly the failure you’re worried about.
Code checked a closed fact. Does this exact thing appear in the source? A yes/no a machine answers without opinion — the Layer Law.
It halted instead of shipping. Unverifiable became a stop, not a guess — fail-closed.
It rebuilt from the real source. The correction came from what is actually there — grounding.
Every move is on the record. What it tried, caught, and corrected is all replayable — the audit trail.
One claim, one check

It does this for every claim, on every run.

You just watched one claim get caught and corrected. The same check runs on everything the agent produces — and you can replay all of it.