Lispex exposes bounded LIL and LIT execution paths beside the Rust reference, with capability limits and measured divergences kept visible.
Current guarantees
- Lispex-in-Lispex, or LIL, is a Lispex-written interpreter that runs as hosted source. It currently supports 85 of the 205 primitive capability rows and rejects the other 120 loudly.
- Lispex-in-Topaz, or LIT, is a Topaz-written transliteration of the pinned Lispex profile. It remains at the independently tracked 84-of-205 capability boundary; internal evidence seals a versioned four-host check surface across the interpreter, generated Rust, generated Python, and Web routes.
- The joint Rust/LIL/LIT receipt covers 144 cases and 432 installed-backend executions. It records 59 all-family agreements, 253 agreeing family pairs, and 179 disclosed pair divergences.
- A separate same-Rust-lineage campaign stores 11,088 generated cases with zero natural divergence and zero infrastructure failure.
Planned implementation line
| Line | Current status | Completion signal |
|---|---|---|
| Rust reference | current operational reference | all 205 primitive capability rows supported with the native/npm/WASM/Playground distribution lineage identified |
| Lispex-in-Lispex | released as a bounded LIL execution line | Lispex-written hosted interpreter supports 84/205 primitive rows and 6/18 guest-calling rows, rejecting the rest loudly |
| Lispex-in-Topaz | released as a bounded LIT transliteration line | Topaz-written interpreter supports the same 84/205 and 6/18 capability boundary with no source-independence claim |
| LIT host agreement | sealed by internal evidence | interpreter, generated Rust, generated Python, and Web routes agree on the exact versioned four-host check surface |
| Rust/LIL/LIT joint receipt | current-bounded on 144 cases | 432 installed-backend executions yield 59 all-family agreements, 253 pair agreements, and 179 disclosed pair divergences |
| Scaled generated campaign | sealed at 11,088 stored cases | native and WASM routes of the same Rust lineage report zero natural divergence and zero infrastructure failure |
| Hosted capability expansion | current incremental work | grow the independently tracked LIL 85/205 and LIT 84/205 boundaries without weakening Rust semantics or hiding unsupported rows and divergences |
| Mechanization | long-term research direction | a named machine-checked artifact closes only its explicitly stated model and assumptions |
Boundaries
- Roadmap items are implementation directions, not promised release dates or assigned version numbers.
- The internal Topaz integration seal is evidence for LIT host agreement, not a public Topaz release.
- LIT is a separate implementation family, but this release makes no source-independence claim for it. Generated host routes are variants of one LIT source, not additional independent implementations.
- The 11,088-case zero-divergence result is not the three-family N-way result. It compares native and WASM packaging of the same Rust implementation lineage.
- These bounded receipts do not establish whole-language equivalence, formal verification, reproducible builds, or unscoped absence of divergence.