Run Lispex in the Playground, install the npm CLI, or download a native binary. Native and npm authenticate exact request-pinned bundles through shared Rust; Native re-execution and gate additionally require those external source and input paths.
At a glance
LISPEX
(define answer (* 6 7))
answerResult
OUTPUT
42Working method
- The Playground needs no installation and runs the public WASM build.
- Use
npm install -g lispexfor the Node-distributed CLI, or open Downloads for a platform binary and checksum. - A file or stdin is evaluated top to bottom; the final result is written canonically.
- Install Lispex, derive and review the exact identities, create/check policy v1, and supply the intended source and input outside every bundle re-execution or gate invocation.
- Opening the bare website negotiates the browser Accept-Language preference on the server: Korean lands on
/v1.7/ko, Russian on/v1.7/ru, and every other language on/v1.7/en. The public minor namespace stays in every localized landing, manual, download, and Playground URL. Quality weights and region subtags are honored; an explicit switcher choice takes priority, while old unversioned and v1.6 locale URLs redirect to the current minor. - Native and npm can turn a named
.lspxfile into an exact Lispex Image, inspect it without printing source, recover the original bytes, and explicitly run it after canonical proof. The Playground provides the same flow locally without installation. - A proved Lispex Image can stand in for the exact source path in the Vouch workflow. Use
--source-image IMAGEtogether with the same separately supplied input; the image does not choose the request or grant authority.
Boundaries
- Native alone exposes
lispex vouch issue,vouch verify --reexecute, andvouch gate --require-decision. Native and npm both expose authenticated flag-freevouch verify; npm also exposes structuralvouch inspectand corpusvouch replay. - Runtime resource ceilings can differ between native and WASM profiles.