You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Rust core design says WASM is the portable capability ABI, but portability
collapses if WASM modules receive different ambient host powers in Rust and
Node. Host functions need a deny-by-default policy before serious portable
capabilities exist.
Hill
A WASM capability can declare its host imports, and Rust/Node hosts can enforce
the same policy or reject the capability before execution.
Done looks like
define the first pure host-function profile
deny filesystem, network, env, process, and ambient clock access by default
define how future host imports are named, versioned, and reported
record fuel/time/memory policy expectations for Rust and Node hosts
execution reports list requested imports, granted imports, denied imports,
and host profile
fixture proves a module requiring an unavailable import is rejected before it
runs
The first pure host-function profile now exists in Rust and rejects unavailable
WASM host imports before execution. Remaining work is host-runtime integration,
resource budgets, and shared Rust/Node report emission.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Migrated from a local Wesley Method backlog card after adopting METHOD v2.1.0 tracker doctrine.
docs/method/backlog/up-next/RUNTIME_wasm-host-function-governance.mdup-nextlane:asapRUNTIMEOriginal Local Backlog Card
WASM host function governance
up-nextRUNTIMEWhy now
The Rust core design says WASM is the portable capability ABI, but portability
collapses if WASM modules receive different ambient host powers in Rust and
Node. Host functions need a deny-by-default policy before serious portable
capabilities exist.
Hill
A WASM capability can declare its host imports, and Rust/Node hosts can enforce
the same policy or reject the capability before execution.
Done looks like
purehost-function profileand host profile
runs
Repo Evidence
docs/design/0009-rust-core-and-wasm-capability-abi/rust-core-and-wasm-capability-abi.mdcrates/wesley-core/src/domain/capability.rscrates/wesley-core/tests/module_capability_registry.rsdocs/method/backlog/bad-code/RUNTIME_module-loading-trust-boundary.mdpackages/wesley-runtime-node/src/ModuleEntryLoader.mjsCurrent Slice Status
The first pure host-function profile now exists in Rust and rejects unavailable
WASM host imports before execution. Remaining work is host-runtime integration,
resource budgets, and shared Rust/Node report emission.