Checking a result
Every number the studio computes itself comes from sigscape-core, one Rust crate. The page runs it as WebAssembly; the local runner links the same crate natively. So the runner can recompute anything the page computed and say whether it agrees, with nothing else to install.
Check on runner
With the runner connected, Check on runner in a function's toolbar sends its recipe to the runner, which verifies every input against the checksum the page wrote, fetches the catalogs the recipe names from this site (and checks their checksums too), recomputes the numbers and reports the largest difference. It recomputes the spectrum comparison, the signature diff and the artifact screen; for the other functions the recipe records the numbers and the parameters behind them.
From a terminal
sigscape-daemon recipe check compare-spectra.recipe.json
sigscape-daemon open "https://sigscape.org/#d=…" --out inputs/
recipe check exits with 0 when every number agrees to 1e-9; open writes a share link's inputs as files (the tables the studio read) and prints the function and view it opens.
Parity
Recipes written by the page with sigscape-core 0.1.0 recompute exactly (largest difference 0.0) on the runner built with 0.6.0. The crate's own parity test runs the same inputs through the WebAssembly build and a Python build of it and compares every exported function; the largest difference has been 0.0 at every release.
Methods text
Methods in any function's toolbar copies a paragraph for a paper's methods section, written from the recipe: the function, sigscape-core's version, the parameters and seeds, and the catalogs with their checksums. It states only what the recipe holds.