Runtime and Backends

Runtime families

All 205 registry rows carry profile-required. Each backend reports its implemented rows through the same versioned observation contract. LIT returns an explicit capability status for the remaining 121 rows, which gives Topaz a precise implementation queue.

The historical family receipt binds 144 named cases to executed Rust, LIL, and LIT product-runner artifacts, resource profiles, observations, and replay.

Rust product surfaces

Native, npm, Public WebAssembly, and Playground share the whole-source interactive projection. They read and normalize the complete source, render explicit output and each successful form in order, and report terminal status as 0, 1, or 2. Ordinary runtime faults retain output already committed by earlier forms. Resource termination returns empty output, one resource diagnostic, and status 2. Browser results expose output, diagnostics, ok, and exit_status directly.

lispex fmt, fmt --check, and fmt --write use the installed Native binary. The VS Code and Open VSX extension delegates Format Document to that binary.

lispex mcp serve uses local stdio to provide the current language and primitive registry, authoring evaluation of trusted source under declared byte and time limits, diagnostics, and fixed route comparisons. Native owns this authoring surface.

Core IR and compiled execution

Native lowers the complete current profile to canonical lispex.core-ir/v1, strictly validates it, and exposes resolved cells, captures, tail positions, requirements, source anchors, and identities.

Strict Core IR compiles to canonical lispex.bytecode/v1. The verifier checks the artifact before VM state is created, and lispex-rust-vm/v1 executes all 205 primitive rows, including the 18 guest-calling rows through iterative VM state machines. Rust tree remains the default engine; --engine vm selects the VM explicitly.

On Native macOS ARM64, the installed lispex-topaz-vm/v1 product reads the same bytecode through its own Topaz reader, verifier, and explicit-control VM. The request records exact source, Core IR, bytecode, input, product identity, full-u64 transition limit, transport caps, and five zero fallback counters.

The Topaz AOT route emits a readable static control graph, compiles it with the installed Topaz 5.11 toolchain, and creates a source-free product. Its product, source map, executable, tool identities, input, resource request, and observations remain bound through aot build, inspect, validate, and run.

compare-engines, compare-vms, and compare-routes publish atomic diagnostic reports for explicitly selected routes. Each report keeps semantic, resource, and lineage observations in separate fields.

Vouch integration

Core IR and bytecode provide canonical meaning and execution artifacts. Native Vouch creates a source-bound lispex.vouch-compiled-artifact/v1, authenticates the request, derives Core IR and bytecode again from the recipient-selected source, records current tree and Meaning agreement, compares the verified Rust VM observation, and passes the result to the local gate.

Topaz VM, AOT, and route-comparison reports remain engineering routes with their own product identities. The compiled Vouch path uses the Rust VM artifact derived from the exact recipient-selected source.

Runner admission record

These fields keep every comparison attached to the product that produced it and give later releases a precise continuation point.

Bytecode and Rust VM · Backend Observation Matrix · Choosing Where to Run