Use this page to find which results to inspect when you run Lispex. For available features, commands, and platforms, open the current product catalog.
For example, when comparing two execution methods, read the result, output, diagnostics, and resource usage together. The runtime comparison guide explains how to read agreement and differences.
What to inspect
| Product or task | Results to inspect | Reference |
|---|---|---|
| Native source execution | Returned values, standard output, warnings, diagnostics, created files, and exit status | CLI |
| Meaning Graph and Meaning Environment v1 | Results for shared variables, mutation, tail calls, escape control, and cleanup. Native provides lower, eval-graph, and meaning-diff. | Core IR |
| Lispex VM | Bytecode acceptance, agreement with the reference interpreter, diagnostics, and resource usage | Bytecode and VM |
| npm | Source evaluation, file inspection, Vouch authentication, and SICP command selection | CLI |
| WASM and Playground | Browser results, language profile selection, and image creation, recovery, and explicit execution | Lispex Images |
| Embedded evaluation | Preparation and evaluation results, resource termination, and portable execution records. The decision evaluator and full evaluator have separate component identities. | Embedded evaluator |
| Decision exchange | Issuer authentication under the recipient's policy and the recorded decision | Decision workspace |
| Lispex Vouch | Key identifiers, issuer authentication, source and input matching, current execution, and the local decision gate. Native issues and gates; npm authenticates. | Vouch records |
| SICP | Native and WASM results, execution traces, chapter examples, and course navigation | SICP |
Read comparison reports
A comparison report identifies the source, intermediate files, and executor used. It records results, diagnostics, and resource usage for the named execution methods. Read the report's case set and implementation identifiers to see what was compared.
The runtime comparison reference explains the recorded cases. The product catalog lists current support.
Find release changes
History separates published releases from development checkpoints. Use it to find when a behavior changed, then consult the current reference for its present rules.