The product today
Lispex is a deterministic decision language. The Rust reference interpreter defines the runtime behavior and supports all 205 tracked primitive rows. The same source and input produce the same observable result under the selected resource profile.
Native, npm, WebAssembly, the Playground, and sicp.io provide distinct ways to use the language. Exact source and input identities, canonical artifacts, stable diagnostics, and typed observations connect those surfaces.
| System | Product role |
|---|---|
| Reference interpreter | Runs Lispex source directly with the complete current language profile. |
| Meaning Graph and Meaning Environment v1 | Project Core IR into an explicit semantic graph and evaluate control flow, shared cells, mutation, tail calls, one-shot escape continuations, dynamic cleanup, stdout, values, warnings, and errors. |
| Core IR and verified bytecode | Resolve bindings and tail positions once, compile canonical bytecode, and execute it in the Rust virtual machine. |
| Native execution routes | Select and inspect tree, Rust VM, Topaz VM, and Topaz AOT products through exact route identities and path-free selection locks. |
| Resource-controlled embed | Runs the decision profile with configured work and memory values and produces a portable core for eligible outcomes. |
| Full embed | Runs all 205 primitive rows through a separately identified import-free WebAssembly component and a fresh instance for every operation. |
| Lispex Images | Encode exact source bytes into canonical PNG or ZIP artifacts and recover those bytes across Native, npm, WebAssembly, and the Playground. |
| Decision exchange | Packages canonical decision artifacts, issuer envelopes, recipient policies, request binding, inspection, authentication, and replay. |
| Vouch | Authenticates signed decision evidence and lets Native evaluate a consumer-pinned request through the local decision gate. |
| SICP | Provides the @lispex/sicp@1.0.0 educational runtime, lispex sicp run, typed observations, exact execution traces, and the chapter course at sicp.io. |
| LIL and LIT | Run Lispex through implementations written in Lispex and Topaz. LIL covers 205 of 205 tracked primitive rows and LIT covers 84 of 205. |
Current direction
Complete semantic structure
Meaning Graph and Meaning Environment v1 establish an explicit-control foundation for shared lexical cells, mutation, tail execution, escape control, and exact observations. The next semantic work extends this foundation through direct runtime behavior and keeps Core IR as the single resolved authority.
Grow LIT coverage
LIT currently implements 84 of 205 tracked primitive rows. Meaning Graph v1, Core IR, and the conformance corpus provide reusable execution observations for the Topaz implementation. Each added row ships with its direct behavior, diagnostics, and resource accounting.
Make exact execution easier to use
Native continues to unify inventory, installation, route selection, diagnostics, measurement, locked execution, and relocation. npm and WebAssembly carry the same canonical artifacts and typed results into application workflows.
Strengthen decision workflows
Decision exchange and Vouch continue around exact source, exact input, recipient-owned policy, authenticated issuer identity, fresh re-execution, and an explicit application handoff. The receiving application owns the final business action.
Expand learning paths
The six-step Lispex course, reference manuals, Playground, and SICP course grow together. English, Korean, and Russian pages use one terminology system, and each lesson connects source to an exact result or typed observation.
Release discipline
Feature work proves its behavior in the module that owns it. A release candidate then builds immutable Native and package artifacts, exercises one installed product journey, publishes those bytes, and confirms the public channels. Roadmap items receive a version when implementation begins.
Keep going
Use History for the exact chronology and Philosophy for the product principles.