DOWNLOAD
THE
ENGINE.
One file. 13 MB. No runtime to install, no account to create, no API key to paste. The model weights are pulled once by --setup and are never bundled into the executable. Everything you need to verify what you received is on this page.
VERIFY BEFORE
YOU RUN IT.
● AVAILABLE NOW — the binary is built and validated, and the checksum below is of that exact artefact. Download it below and verify the SHA-256 before you run it. The source repository stays private; the artefact is served directly.
WHAT IT NEEDS
TO RUN.
Windows
Windows x64. This is the only platform the engine has been built and run on — never macOS, Linux, tablet or phone.
RAM
The reference machine is a 16.8 GB consumer laptop, and every figure this project publishes was produced on it. The largest local model is 9.6 GB; smaller ones need less.
Free Storage
13 MB for the engine plus room for open weights. The reference install holds 42 GB across eight models — you choose how many to pull.
Network, After Setup
--setup pulls the weights once. After that the inference endpoint is on loopback and remote egress is off.
THREE STEPS.
NO INSTALLER.
Windows SmartScreen will show a "Windows protected your PC" warning the first time you run it, and you will need More info → Run anyway. That warning is telling you the truth: nothing vouches for this binary except the checksum on this page. Compare it first. A SHA-256 detects a changed or corrupted file — it is not a signature and does not prove who built it. If you are deploying this inside an organisation, that distinction is the one your security team will ask about.
MEASURED,
NOT ASSERTED.
Reproduce every figure with python asura_model.py, or run the suite inside the binary itself.
Tests Inside The Binary
219 pass from source; 180 pass inside the artefact, run from a temporary directory with no source tree beside it. The in-artefact number is the one that says anything about the file you downloaded.
Sovereignty Conditions
Loopback endpoint, remote egress off, weights present locally, no API key — re-checked at call time rather than asserted once at install.
Agent Specifications
42 department + 15 engineering + 12 job + 20 elite. Run sequentially — there is no concurrent scheduler over the four rosters.
Local RPC Methods
route, parse, health, introspect, departments, cluster, tenants — read-only, allowlisted, loopback only, and unauthenticated because nothing is exposed off the machine.