Runs a ChainGraph decision kernel's compute(policy_parameters) inside a sandboxed, hermetic, in-browser QuickJS-ng WebAssembly VM under the ocg-deterministic-compute@2 profile (SPEC.md §24). The VM is a fifth compute surface beside the worker, embed bundle, composer, and zkVM guest: this page runs the SAME kernel source twice, once in this VM and once natively in your browser's JavaScript engine, and shows whether the two execution_hash values agree.
import() of the SAME kernel source with no sandbox. It is a same-tab parity check, not a live call to the Cloudflare Worker (this page makes zero network calls). The CI gate additionally diffs the VM against the worker's own kernel registry on every push.Paste any kernel's compute(policy_parameters) source and its parameters below and run it in the SAME sandboxed VM used above. Because you supply every byte yourself, this box makes zero network calls too — the pasted source is never fetched, only executed inside the QuickJS-ng guest. It is also never handed to this page's own JavaScript engine: the guest sandbox is the only thing that ever runs it, exactly like the demo kernels above.
298 gpu:false kernels in the catalog are runnable via the catalog and the MCP server — this page's 10-kernel dropdown above is a curated demo subset, not the full set, and CI verifies every one of the 298 byte-identical in this same VM (chaingraph/kernels/vm-parity-gate.mjs) on every push. Browse the full catalog on the ChainGraph catalog or call it over MCP at mcp.ainumbers.co. See also the decision boundary explorer, which sweeps a kernel's inputs the same way the worker does.