The engine is WebAssembly on this page, and the corpus subtree is the unit: every statute, regulation, and manual section is a root you can slice at. Pick one — its import closure compiles to an artifact in this tab and runs. State the facts you know; everything you don't state is a screening presumption you can open and correct. Your answers never leave the page. Every slice wears its certification status — "certified" when the ledger vouches for its full closure, "encoded — not certified" otherwise.
Or in your terminal
└─ the SNAP benefit computation of 7 CFR 273.10, sliced straight from the corpus and executed by the vendored engine — $478 for this household is pinned by this repo's tests
The repo is the distribution: the engine is checked in, and the corpus is regenerated from the pinned commit. No Rust toolchain, no API key, no network at run time. From here, the same command does everything:
What ships in the clone
| engine/ | the RuleSpec compiler + evaluator, WebAssembly, browser and Node builds |
| public/corpus/ | the sliceable corpus — regenerated from TheAxiomFoundation/rulespec-us@5cc39ed (corpus.lock.json) |
| public/corpus/ledger.json | the certification ledger (fixture-us-ny-snap) — the status authority every slice is checked against |
There is no program registry and no pre-composed bundle: the subtree is the unit, and what runs is exactly what the corpus says, compiled on your machine.