VibeScript In-Browser WASM Verification & Purpose Clocks
These interactive micro-benchmarks measure the shipped vibe-wasm WebAssembly lifecycle directly in your browser tab:
Checked cell (static type, capability-lease, and IDF-04 firewall verification),
CompiledCell.compile (compiling source into a retained VBC1 bytecode handle),
and run() ×2 (executing the compiled handle repeatedly without re-parsing or re-decoding source).
Checked cell
Type-check & verify capability leases before run
CompiledCell.compile
Compile once · keep reusable bytecode handle
CompiledCell.run
Run ×2 · no re-decode on retained handle
Edit source, no host rebuild
Update script cells live without recompiling the host binary
Benchmark Methodology & Architectural Tradeoffs
VibeScript is designed as a capability-bounded, zero-heap semantic scripting layer rather than a general-purpose JIT engine competing on raw scalar loop throughput. When interpreting these measurements for research or production integration, keep four lifecycle stages distinct:
| Lifecycle Stage | API Surface | What Is Measured & Guaranteed |
|---|---|---|
| 1. Checked cell | check_cell_src / vibe::diagnose |
Lexing, parsing, dimensional unit checking, capability lease verification, and compile-time IDF-04 identifier firewall validation before any bytecode executes. |
| 2. Compile once | CompiledCell.compile(src) |
One-shot lowering of validated AST into compact, relocatable VBC1 stack bytecode held in a reusable handle. |
| 3. Run ×2 (Hot Evaluation) | cell.run() |
Repeated zero-heap stack VM execution on the retained bytecode handle—eliminating source parsing and AST lowering overhead on high-frequency UI/continuum ticks. |
| 4. Edit source, no host rebuild | Hot cell replacement | Modifying a VibeScript formula or agent policy re-checks and re-compiles only the cell in microseconds, requiring zero Rust/WASM host recompilation. |
SlgArena query throughput, ADR 0003 ExactnessProfile overhead, and GPU/WASM kernel timings), see the main QualiaDB Benchmark Hub (benchmark.html#vibescript) and VibeScript Execution Profiles.