Skip to content

docs(rivet): comparison targets — spacewasm + DLR-FT (safety-critical Rust interpreter field) - #414

Merged
avrabe merged 2 commits into
mainfrom
chore/engine-comparison-targets
Jul 11, 2026
Merged

docs(rivet): comparison targets — spacewasm + DLR-FT (safety-critical Rust interpreter field)#414
avrabe merged 2 commits into
mainfrom
chore/engine-comparison-targets

Conversation

@avrabe

@avrabe avrabe commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

Lands REQ_ENGINE_COMPARISON (roadmap-only). Tracks benchmarking + differentially validating kiln against its true peers — the safety-critical Rust WebAssembly interpreters — besides the wasmtime JIT (the "unverified TCB" foil of #283).

Peer What it is
NASA spacewasm Flight-compliant ground-up Rust interpreter for on-board spacecraft; deterministic memory, streaming, CoreMark, libfuzzer. Draws on wasmi/wasm3/DLR-FT.
DLR-FT/wasm-interpreter Minimal in-place Rust interpreter for avionics (DO-178C/DO-332); passes full WAST (minus unfinished proposals); fuel halt/refill/resume (mirrors kiln); live migration. NASA spacewasm's reqs derive from it.

Two workstreams:

  1. Differential correctness (extends SR-35 / approach: make kiln a verified reference executable oracle (differential against an external verified interpreter) #401) — use both as additional differential oracles alongside wasmtime. Both Rust + embeddable (far cheaper than WasmRef-Isabelle); peer-engine agreement is high-signal.
  2. Competitive matrix — WAST conformance, perf (CoreMark + the executor-comparison micro methodology), peak/deterministic memory, resumable-fuel — and the verification-evidence axis where kiln leads (Verus + Lean proofs, witness MC/DC on the real Wasm, sigil attestation, rivet traceability). spacewasm/DLR are cert-designed but not proof-carrying / MC/DC-attested to this stack level.

"Outcompete" = lead decisively on verification evidence while matching or beating on conformance + determinism.

derives-from SR-35; rivet validate = 0 errors. Tracks #413.

🤖 Generated with Claude Code

avrabe added 2 commits July 11, 2026 08:07
…ewasm, DLR-FT)

Land REQ_ENGINE_COMPARISON: benchmark + differentially validate kiln against its
true peers — the safety-critical Rust WebAssembly interpreters — besides the
wasmtime JIT.

- NASA spacewasm (flight-compliant Rust interpreter for spacecraft; deterministic
  memory, streaming, CoreMark, libfuzzer).
- DLR-FT/wasm-interpreter (minimal in-place Rust interpreter for avionics,
  DO-178C/DO-332; passes full WAST minus unfinished proposals; fuel halt/refill/
  resume mirroring kiln; live migration). NASA's spacewasm reqs derive from it.

Two workstreams: (1) use both as additional differential oracles alongside
wasmtime (extends SR-35/#401 — Rust + embeddable, peer-engine agreement is
high-signal); (2) a competitive matrix on conformance / perf / memory /
resumable-fuel AND the verification-evidence axis where kiln leads (Verus + Lean
proofs, witness MC/DC on real Wasm, sigil attestation, rivet traceability).
Outcompete = lead on verification evidence while matching/beating on conformance
+ determinism. Sharpens #283 positioning. derives-from SR-35. Issue #413.

Trace: skip
…OMPARISON

The differential set is now {kiln, wasmtime, spacewasm, DLR-FT, WasmRef-Isabelle}
with tiered signal: WasmRef-Isabelle (PLDI 2023) is the machine-checked GOLD
oracle (a kiln-only disagreement is a correctness bug), the safety-critical Rust
peers are cheap cross-checks, wasmtime is the JIT baseline. Per SR-35, the
verified leg is load-bearing — an interpreter you also wrote is not its own
oracle.

Trace: skip
@github-actions

Copy link
Copy Markdown

🔍 Build Diagnostics Report

Summary

Metric Base Branch This PR Change
Errors 0 0 0
Warnings 5 5 0

🎯 Impact Analysis

Issues in Files You Modified

  • 0 new errors introduced by your changes
  • 0 new warnings introduced by your changes
  • 0 total errors in modified files
  • 0 total warnings in modified files
  • 0 files you modified

Cascading Issues (Your Changes Breaking Other Files)

  • 0 new errors in unchanged files
  • 0 new warnings in unchanged files
  • 0 unchanged files now affected

Note: "Cascading issues" are errors in files you didn't modify, caused by your changes (e.g., breaking API changes, dependency issues).

✅ No Issues Detected

Perfect! Your changes don't introduce any new errors or warnings, and don't break any existing code.


📊 Full diagnostic data available in workflow artifacts

🔧 To reproduce locally:

# Install cargo-kiln
cargo install --path cargo-kiln

# Analyze your changes
cargo-kiln build --output json --filter-severity error
cargo-kiln check --output json --filter-severity warning

@codecov

codecov Bot commented Jul 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@avrabe
avrabe merged commit f1a643f into main Jul 11, 2026
19 checks passed
@avrabe
avrabe deleted the chore/engine-comparison-targets branch July 11, 2026 06:53
avrabe added a commit that referenced this pull request Jul 11, 2026
… roadmap conflict)

Additive conflict in roadmap-requirements.yaml: kept both REQ_NOSTD_INTERP (this
branch) and REQ_ENGINE_COMPARISON (from #414 on main).

Trace: skip
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant