mirror of
https://github.com/ruvnet/RuVector.git
synced 2026-05-23 04:27:11 +00:00
4bec65135f
Add the WASM_SEG segment type and complete self-bootstrapping architecture that allows RVF files to carry their own execution runtime. When an RVF file embeds a WASM interpreter alongside the microkernel, the host only needs raw execution capability — making RVF "run anywhere compute exists." Changes: - rvf-types: Add SegmentType::Wasm (0x10), WasmHeader (64-byte), WasmRole, WasmTarget enums, and feature flag constants - rvf-runtime: Add embed_wasm(), extract_wasm(), extract_wasm_all(), is_self_bootstrapping() methods on RvfStore, plus write_wasm_seg() in the write path - rvf-wasm: Add bootstrap module with resolve_bootstrap_chain() that discovers WASM_SEGs, parses headers, and resolves the optimal bootstrap strategy (None/HostRequired/SelfContained/TwoStage/Full) - docs: Add spec/11-wasm-bootstrap.md with complete wire format, bootstrap protocol, size budget analysis, and security model The three-layer bootstrap stack: Layer 0: Raw bytes (.rvf file) Layer 1: Embedded WASM interpreter (~50 KB) Layer 2: WASM microkernel (~5.5 KB) Layer 3: RVF data segments All 131 rvf-types tests and 72 rvf-runtime tests pass. https://claude.ai/code/session_01RnwD4x5cbpB7FPvoyYQz8G |
||
|---|---|---|
| .. | ||
| 00-overview.md | ||
| 01-segment-model.md | ||
| 02-manifest-system.md | ||
| 03-temperature-tiering.md | ||
| 04-progressive-indexing.md | ||
| 05-overlay-epochs.md | ||
| 06-query-optimization.md | ||
| 07-deletion-lifecycle.md | ||
| 08-filtered-search.md | ||
| 09-concurrency-versioning.md | ||
| 10-operations-api.md | ||
| 11-wasm-bootstrap.md | ||