An interface is a contract for interaction: it names the functionality a component must provide and specifies the parameters and outputs used to call it. A host can call a WebAssembly (Wasm) library through that contract without knowing how the library works. section 10.1
This boundary makes replacement practical. A different Wasm module can fulfill the same interface without changing or stopping the host application. The host still depends on the agreed interface, so its design determines how flexible the integration will be. section 10.1 section 10.4
Calling a module from a Rust CLI
A Rust CLI can register a Wasm file in a WasmEdge VM, then call an exported function such as `static_search` with `params!(0, 1)`. The module must provide the function the host calls; its internal implementation remains separate from the CLI. section 10.4
The same approach can bring existing logic compiled to Wasm into a Rust runtime without incorporating its source into the host build. The module remains a dependency, but it runs in isolation. section 10.4
