Build in the open
Contribute fixes, reproducible evidence, and clearly scoped interface proposals.
Start with a reproducible change
Include the affected revision, platform, smallest module or component, expected behavior, and actual result. Keep security-sensitive reproductions private. Runtime work belongs in Wasmd; Registry UI, storage, and account work belongs in the Registry repository.
Run the workspace checks
From the Wasmd repository, run the relevant checks below. Full spec validation additionally requires the pinned WebAssembly/spec checkout described in README.md.
cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
cargo test --workspace --all-features --lockedFollow the ecosystem boundaries
WASI follows upstream standards. Native package and orchestration specifications remain design directions, while the Registry implementation is available independently. Future scheduling, replicas, upgrades, and recovery must not be presented as runtime features already delivered.
Based on the current repository documentation. Check your installed version and the linked acceptance records when adopting development features.
Read the Wasmd source document ↗