Choose Where to Run Lispex

Quick choices

Task	Product
run ordinary `.lspx` source	reference interpreter through Native, npm, WebAssembly, or Playground
execute verified bytecode	Native Rust VM
compare a separately installed VM	Topaz VM on Native macOS ARM64
build a standalone executable	Topaz AOT on Native macOS ARM64
run a supplied rule with explicit resource values	`lispex embed` or `lispex embed full`
create and recover exact source images	Native, npm, WebAssembly, or Playground
authenticate signed decision evidence and evaluate a local gate	Native Vouch, with npm verification
study SICP	sicp.io, `lispex sicp run`, Playground SICP profile, or `@lispex/sicp`
compare implementation families	Native differential, Meaning, and route comparison commands

Reference interpreter

The reference interpreter runs the complete current Lispex profile and remains the default for lispex rule.lspx. It is the direct authoring and application route across Native, npm, WebAssembly, and the Playground.

Verified virtual machines

Native compiles source through canonical Core IR and verified bytecode into the Rust VM with --engine vm. On macOS ARM64, Native can also use an exact installed Topaz 5.11 VM and compare both virtual machines over one bytecode artifact.

The Rust tree and Rust VM share the Rust implementation lineage. The Topaz VM uses a separately maintained source implementation and records its Topaz Rust Stage 0 producer identity. Comparison receipts publish both lineages, exact artifacts, results, diagnostics, and resources.

Standalone AOT product

The Topaz AOT route emits readable Topaz, a source map, and a standalone executable from verified control flow. The route records source, Core IR, bytecode, generated bundle, compiler, executable, request, result, and resource identities.

Resource-controlled execution

lispex embed selects the decision profile. lispex embed full selects the complete current profile with all 205 primitive rows. Both use import-free WebAssembly components, fresh instances, separate preparation and evaluation resources, and portable cores.

Inspect and lock a route

lispex routes inventory --out inventory.json
lispex routes doctor --inventory inventory.json
lispex routes select --route rust-vm --out route.json
lispex routes run --selection route.json rule.lspx

External products use their exact absolute installation path. Selection locks record product identity and route choice while keeping local paths outside the lock.

Measure local execution

lispex routes measure \
  --selection route.json \
  --samples 3 \
  --input input.datum \
  --out timing.json \
  rule.lspx

The measurement records host identity, route identity, sample count, and nanosecond observations for that local run. Comparison receipts separately record language results and resource counters.

Product availability

Product	Main surfaces
Native	every execution route, Core IR, bytecode, embed, images, decision exchange, Vouch, and SICP
npm	reference evaluation, package APIs, images, decision and Vouch verification, and SICP
WebAssembly	reference evaluation, image codec, and published embed and SICP components
Playground	browser-local reference evaluation, Lispex Images, Native handoff, and SICP profile

Keep going

Downloads · Run Verified Bytecode · Build a Topaz AOT Product