Checked Surfaces

The 144-case Rust/LIL/LIT receipt and the 11,088-case same-Rust-lineage campaign are separate measured surfaces with explicit inventories and provenance.

How to reason about it

  • The documentation corpus and targeted runtime tests check named examples and negative diagnostics.
  • The integrated denominator is exactly 144 cases: 38 differential, 61 conformance, 7 warning, 6 resource, and 32 bounded generated cases.
  • Receipts record exact inventory, runners, observations, replay, mismatch disclosure, provenance, artifact identity, delegation, capabilities, and limits.
  • A separate scaled campaign stores 11,088 generated cases across native and WASM routes of the same Rust lineage, with zero natural divergence and zero infrastructure failure.
  • A focused Rust engine court compares tree and verified-bytecode VM outcomes, exercises all 205 primitive dispatch rows, and records zero forbidden fallback. It is separate from the historical three-family receipt.
  • Synthetic drifts and mutation controls demonstrate that checkers can detect selected failure classes.

The conformance court has several layers

  1. Authored examples pin one behavior at a time.
  2. Generated cases explore a larger valid and deliberately invalid space.
  3. Mutation controls prove that selected contract damage is rejected.
  4. Resource cases keep bounded termination visible as an observation.
  5. Diagnostic cases compare error codes, messages, spans, bytes, and warning order.
  6. Differential runs compare the same case across admitted implementation families.

These layers complement one another. A generated count does not replace a clear authored example, and a mutation control does not prove that every defect is detectable. Any new pair mismatch begins as unclassified; the maintained court fails closed until its observation and primary reason are recorded.

Measured evidence lines

SurfaceInventoryStrongest honest reading
Documentation conformance122 result annotations plus diagnostic/TCO/control casesnamed examples match the reference interpreter
Integrated backend denominator38 differential + 61 conformance + 7 warning + 6 resource + 32 generated-bounded = 144 casesone exact inventory reused for LIL, LIT admission, and the N-way matrix; generated seed 550633217
LIL hosted backendcurrent contract: 205/205 primitive rows and 18/18 guest-calling rows; the 144-case released receipt records the prior 84-row boundaryfocused courts cover prior convergence, exact integers, higher-order callbacks, output, and 4 success plus 3 negative warning-alias observations for ordering, call-site deduplication, shadowing, warning-before-error, channel separation, and zero forbidden fallback; the historical receipt remains unchanged
LIT transliteration84/205 primitive capability rows and 6/18 guest-calling rows; one LIT product route in the 144-case receiptRust/LIT agrees on 65 cases and diverges on 79; no source-independence claim
LIT four-host sealTopaz interpreter, generated Rust, generated Python, and Web routes from one canonical sourcebounded evidence closes its exact versioned check surface; these are host variants, not four implementations
Three-family joint receipt144 cases, 432 installed-backend executions, and 432 family-pair comparisons59 all-family agreements and 85 cases with at least one divergence; 253 pair agreements and 179 pair divergences remain explicit
Scaled same-lineage campaign11,088 stored generated cases across native and WASM Rust routeszero natural divergence and zero infrastructure failure on that inventory; not a Rust/LIL/LIT campaign
Rust tree/VM courtfocused semantic and control programs, all 205 primitive dispatch rows, strict malformed-bytecode negatives, exact source/Core IR/bytecode identities, and zero fallback instrumentationthe explicit VM matches the tree observation on this maintained same-Rust-lineage surface; not an independent witness, Vouch receipt, or whole-profile proof

A common mistake

A zero mismatch count is scoped to its stored or executed inventory only.

Current boundaries

  • The 11,088-case zero-divergence campaign is not the Rust/LIL/LIT joint receipt and does not establish implementation independence or whole-language equivalence.
  • The focused LIL courts change current LIL coverage only. They do not recompute or upgrade the historical 144-case receipt.
  • The Rust tree/VM comparison report is diagnostic material. It does not join the backend denominator or grant execution authority.

Keep going

Use this page while writing code. For a guided explanation, return to the syntax map or the corresponding manual.

Bytecode and Rust VM · Syntax at a Glance · Learning Path