Lispex compares backends through named source programs and exact observable results. Each matrix row identifies the implementation, capability registry, execution route, corpus, and receipt format.
Execution families
| Family | Implementation | Current observation |
|---|---|---|
| Rust reference | reference interpreter in Native and WebAssembly | 205 of 205 tracked primitive rows |
| LIL | Lispex interpreter written in Lispex | 205 of 205 tracked primitive rows |
| LIT | Lispex interpreter written in Topaz | 84 of 205 tracked primitive rows |
| Rust VM | canonical Core IR and verified bytecode executed by the Rust VM | exact source, Core IR, bytecode, result, diagnostics, and resource identities |
| Topaz VM | the separately installed Topaz 5.11 VM product | exact provider, request, bytecode, result, diagnostics, and resource identities |
| Topaz AOT | Lispex compiled into a standalone Topaz product | source map, generated bundle, executable, request, result, and resource identities |
| SICP | the explicit SICP profile in Native and @lispex/sicp WebAssembly | typed sicp-observation/v1 and exact lispex-trace/v1 execution trace |
Comparison records
| Record | What it compares |
|---|---|
csk.differential-receipt/v0 | the historical Rust, LIL, and LIT corpus |
lispex.rust-engine-comparison/v1 | Rust tree and Rust VM over one derived Core IR and bytecode artifact |
lispex.topaz-vm-comparison/v1 | Rust VM and the exact installed Topaz VM over one bytecode artifact |
csk.meaning-differential-report/v1 | Rust reference behavior and Meaning Environment v1 over the selected source |
sicp-observation/v1 | SICP profile termination, value, stdout, diagnostics, warnings, and artifact identity |
Every record carries the corpus or source, executor identities, profile, observable channels, and comparison status. Capability rows use explicit supported and unsupported results, so backend growth is visible one row at a time.
Reading the numbers
Primitive counts describe registry coverage. Corpus counts describe the named programs executed in a receipt. Engine comparisons describe exact routes and artifacts. Together they show implementation progress and the observations available to downstream tools.