Downloads

Install the native Lispex reference interpreter, verify its checksum, or choose the npm and Playground surfaces.

Lispex manual v1.21. Every link on this page is pinned to the release shown below. The install scripts find the current release and compare the downloaded binary with the SHA-256 checksum file published beside it.

Download file version v1.20.0

All platforms

PlatformBinaryChecksum
Linux · x86_64lispex-linux-x86_64.sha256
Linux · aarch64lispex-linux-aarch64.sha256
macOS · Apple siliconlispex-macos-aarch64.sha256
macOS · Intellispex-macos-x86_64.sha256
Windows · x86_64lispex-windows-x86_64.exe.sha256
Release manifestmanifest.jsonfile names, sizes, addresses, and SHA-256 checksums

Typesetting rule workspace

Send a heading placement decision to the printer

Prepare a rule and input, sign its decision, and let the recipient authenticate and rerun it. The guide includes the complete files and commands.

The resource-controlled rule engine, exact bytes

Applications can pin the exact bytes of the engine embedded in Native. It runs one rule under the declared resource profile. Its manifest fixes capabilities, metering, value exchange, receipt fields, memory limits, and checksum. Recorded request and result bytes let every consumer compare the exact observation.

ItemFileChecksum
Resource-controlled rule engine WASMlispex-embed-evaluator.wasm.sha256
Rule engine manifestlispex-embed-evaluator-manifest.json.sha256
Recorded request and result byteslispex-embed-evaluator-golden-vectors.json.sha256
Rule engine redistribution packagelispex-embed-evaluator-redistribution.zip.sha256

The whole-language rule engine, exact bytes

A separate component covers the complete lispex-profile-1.5 and carries its own capability, metering, component, and artifact identities. It reuses the established value exchange, run transcript, and portable record format. Native selects it through explicit embed full commands and creates a fresh instance for every operation.

ItemFileChecksum
Whole-language rule engine WASMlispex-full-embed-evaluator.wasm.sha256
Whole-language rule engine manifestlispex-full-embed-evaluator-manifest.json.sha256
Recorded vectors for the whole-language enginelispex-full-embed-evaluator-provider-vectors.json.sha256
Redistribution package for the whole-language enginelispex-full-embed-evaluator-redistribution.zip.sha256

One-line install

SHELL
# macOS / Linux
curl -fsSL https://www.lispex.com/install.sh | sh

# Windows (PowerShell)
irm https://www.lispex.com/install.ps1 | iex

# npm (Node 18+)
npm install -g lispex

Check the installed command

A successful install prints the exact product version. You can repeat the check at any time.

SHELL
lispex --version
# Expected: lispex v1.20.0

If the command is not found

  • macOS and Linux install to ~/.lispex/bin by default. Add that directory to PATH, then restart the shell.
  • Windows installs to %LOCALAPPDATA%\Lispex\bin by default. Add that directory to the user PATH, then open a new PowerShell window.
  • If you chose npm, confirm that Node 18 or newer is active and that the global npm binary directory is on PATH.

Which one should I use?

  • Choose the native binary for the widest set of tools. It includes the source interpreter, a resource-controlled rule engine, the Rust virtual machine for verified bytecode, intermediate-form commands, exact Lispex Images, and the complete Lispex Vouch workflow. Native owns evidence issuance, current re-execution of the pinned request, and the local gate. It can also derive a compiled artifact from the same exact source and record Rust VM agreement.
  • Choose npm when Node is already available. It runs source, provides the same exact Lispex Image commands through Rust compiled to WASM, authenticates Vouch evidence with the same checker as Native, and replays decision corpora offline. Native owns intermediate forms, verified bytecode and the Rust virtual machine, evidence issuance, current re-execution, and the local gate.
  • Use the Playground to run source and to create, open, page through, recover, download, and explicitly run exact images directly in your browser. Native provides intermediate forms, bytecode and the Rust virtual machine, while Native and npm provide the Vouch artifact and policy tools.

Lispex Images

Carry exact source as an image that always comes back the same

Native and npm share the same image commands, and public WASM and the Playground run the same Rust codec locally. Each restores source byte for byte after the format, integrity, parity, and regeneration checks. Native connects the recovered source to the full Vouch workflow, and npm connects it to identity, policy, and authenticated verification.

Lispex Vouch

Use Native when a decision must reach a local gate

Native binds authenticated evidence to the exact source and input supplied outside the bundle, runs the rule again on your machine, and records the matching local decision. On request it also derives a compiled artifact from that source and records verified Rust VM agreement. The local gate consumes current request-bound evidence, and the host application consumes the gate result.