A DOM built from WebAssembly, without JavaScript

This page has no script. Its interface is a WebAssembly module that builds the document directly, calling host functions that operate on the browser's own node arena. There is no glue layer, and no JavaScript engine anywhere in the path between the program and the DOM.

In every shipping browser the DOM is a JavaScript API, so a WebAssembly program reaches it either through generated glue or by proxying mutations to another thread. Both pay a cost designed for a different language. This is what the arrangement looks like when the DOM was never a JavaScript API to begin with.

What the page requests

One thing: the module. Its own sections carry the templates it needs and the version of the reactive runtime it was compiled against. Both the shared template set and that runtime are provided by the engine, so neither is fetched.

demo.<hash>.wasm
the program, its templates, and its runtime requirement

If you are reading this, the module did not run. That is the expected result in a browser that cannot bind its imports, and it is deliberate: nothing here degrades into a partial interface. Compiled artifacts are immutable and content-addressed; only this document ever changes.