Playground
(Lispex)
KOENRU

Using Vouch Bridge

Vouch Bridge checks a report emitted by an external engine that binds declared source, target, route, engine identity, gates, and linked hashes.

How to reason about it

  • Run the external engine separately, preserve its source/target bytes, then run lispex verify-bridge on the report and supplied artifacts.
  • The checker validates report shape, byte bindings, declared gates, and proof-link hashes.
  • Bridge remains a different artifact class and verifier entrypoint from native differential receipts.

Check a report

SH
lispex verify-bridge \
  --source source.lspx \
  --target translated.output \
  bridge-report.json

A successful check prints a Bridge verification report. It says that the declared files and hashes are internally consistent; it does not rerun the external engine.

A common mistake

The checker does not run the external engine, inspect private implementation, or establish semantic equivalence.

Keep going

Keep the Vouch overview nearby: it separates authentication, request binding, current execution agreement, and a local grant.

Lispex Vouch overview · Choosing a Runtime Surface