Backend Observation Matrix

The v1.5 observation contract compares the Rust reference, LIL, and LIT as three implementation families while retaining exact runner, artifact, host-route, and provenance labels.

Current guarantees

  • Every runner exposes value/output, diagnostics, status, warnings, declared resource observations, artifact identity, limits, and provenance through the versioned observation contract.
  • LIL is a Lispex-written hosted interpreter and LIT is a Topaz-written transliteration. Each currently supports 84 of 205 primitive capability rows and rejects the remaining 121 explicitly.
  • The installed-product receipt runs one host route per family over 144 cases. It records 253 family-pair agreements and 179 divergences; pairwise results are Rust/LIL 61/83, Rust/LIT 65/79, and LIL/LIT 127/17, with 59 all-family agreements.
  • Separate internal Topaz 5.7.0 evidence seals LIT host agreement across interpreter, generated Rust, generated Python, and Web routes on a versioned four-host check surface.

Current backend status

SurfaceImplementation / provenanceCurrent evidence boundary
Native CLIRust reference interpreter; same-origin-referencecurrent; full native CLI and named receipts
Public WASM / Playgroundsame Rust lineage compiled to WASMcurrent same-origin observations; profile-specific limits
npm CLINode packaging around public WASM/JS surfacecurrent packaging; command subset differs from native
Lispex-in-LispexLispex-written hosted interpreter; one LIL implementation family84/205 primitive capability rows; joint receipt pair Rust/LIL agrees on 61 cases and diverges on 83
Lispex-in-Topaz interpreter routeTopaz-written transliteration; one LIT family with no source-independence claim84/205 primitive capability rows; joint receipt pair Rust/LIT agrees on 65 cases and diverges on 79
Lispex-in-Topaz host routesthe same canonical LIT source through interpreter, generated Rust, generated Python, and Webinternal Topaz 5.7.0 evidence seals a versioned four-host check surface; public Topaz remains v5.6.3
Rust/LIL/LIT joint receiptthree implementation families and one installed product route per family144 cases and 432 executions; 59 all-family agreements, 253 pair agreements, and 179 disclosed pair divergences
Scaled generated campaignnative and WASM routes of the same Rust implementation lineage11,088 stored cases; zero natural divergence and zero infrastructure failure; not the three-family receipt

Boundaries

  • Host variants within the Rust reference, LIL, or LIT family are not independent witnesses.
  • No source-independence claim is made for LIT. The matrix is bounded to its recorded surface and does not establish whole-language semantic equivalence or no-divergence beyond it.