mirror of
https://github.com/marcoallegretti/WEFT_OS.git
synced 2026-03-26 17:03:09 +00:00
WEFT OS is a Wayland compositor and application runtime where every app is a WebAssembly component rendered in an isolated Servo WebView.
Specifies the concrete steps needed to replace the current READY stub with real Wasm module execution: - Optional cargo feature gate (wasmtime-runtime) to keep default builds fast; production service unit uses the feature-enabled binary. - Engine + Module setup from wasm file path. - WasiCtxBuilder with inherited stdout/stderr for READY signal passthrough. - READY signal timing: Option A (print before _start) vs Option B (explicit weft_ready() export); Option A is the initial implementation. - Entry point: _start (standard wasm32-wasi target output). - Error handling: module load failures, trap handling, missing _start. - Explicit non-scope: host imports beyond WASI, memory caps, component model, Wasm threads, fuel metering. - Prerequisite: confirmed wasm32-wasi app SDK before integration. |
||
|---|---|---|
| .github/workflows | ||
| crates | ||
| docs | ||
| infra | ||
| protocol | ||
| scripts | ||
| .gitattributes | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| justfile | ||
| README.md | ||
| rust-toolchain.toml | ||
WEFT OS
WEFT OS is a Linux-based operating system effort built around a Smithay compositor, a Servo-rendered system shell, and a Wasmtime-based application runtime.
Current repository scope
This repository currently contains:
- the baseline Rust workspace
- public engineering documentation derived from the authoritative blueprint
- initial design documents for the shell protocol boundary and the Wasm–Servo channel
- local and CI validation paths for repository bootstrap work
It does not yet contain a compositor, shell, or application runtime implementation.
Source of truth
The authoritative technical reference for this repository is docu_dev/WEFT-OS-COMPREHENSIVE-BLUEPRINT.md.
Historical blueprint documents exist in docu_dev/, but they are not implementation authority where they conflict with the comprehensive blueprint.
Privacy boundary
docu_dev/ is a private coordination area used during development. It is intentionally ignored by git and is not part of the tracked public repository surface.
Development model
- Primary development host: Windows workstation
- Primary runtime target: Linux VM or QEMU guest
- Core system language: Rust
Validation
On Windows PowerShell:
./infra/scripts/check.ps1
On Linux:
./infra/scripts/check.sh
Repository layout
crates/ Rust workspace members
docs/ Public engineering documentation
infra/ Validation scripts and VM workflow material