Skip to content

Install and use domain adapters

The native anarres binary validates and compares versioned environment records. Domain adapters are separate tools that translate released robotics, legal, materials, molecular, finance, formal-verification, or vulnerability sources and measurements into those records without changing their scientific meaning.

Homebrew and the standalone installer provide the native binary. They do not install every domain runtime. Install only the adapters needed for the studies you intend to inspect.

Install from a checkout

Clone the repository and install an adapter with uv tool install. The repository's workspace metadata resolves the shared Anarres packages from the checkout.

git clone https://github.com/anarres-organization/anarres.git
cd anarres

# Choose one or more adapters.
uv tool install ./data/formal-verification/vero
uv tool install ./experiments/robotics/environment-selection/prospective-cupid-can-v141
uv tool install ./packages/legal
uv tool install ./experiments/ai-for-science/materials-science/mlip-phonon-environment-selection/adapter
uv tool install ./experiments/ai-for-science/molecular-design/reaction-environment-selection
uv tool install ./packages/finance
uv tool install ./packages/vulnerability

If uv reports that its executable directory is not on PATH, run uv tool update-shell and restart the shell.

Confirm what the native CLI can discover:

anarres adapter list
anarres adapter doctor legal
anarres legal status --repository .

The explicit --repository argument points the installed adapter to the released evidence in the checkout. Adapter discovery never searches a checkout or downloads scientific artifacts implicitly.

What each adapter can do

Installing an adapter makes a domain command available. It does not imply that the domain's measurements have predicted a new training outcome.

Adapter Start here Then inspect Available now
Formal verification anarres formal status --repository . anarres formal qualification --repository .
anarres formal qualify-runtime --help
Source and model-free runtime qualification are available; policy probing, containment requalification, and RL remain blocked
Robotics anarres robotics status --repository . anarres robotics can-results --repository . Can v1.4.1 candidate measurements and prospective result
Legal reasoning anarres legal status --repository . anarres legal regressions --repository . SylloGym candidate profiles and a separate LAB regression report
Materials science anarres materials status --repository . anarres materials results --repository . Native OMat24 bank qualification, MLIP candidate measurements, and the scored prospective result
Molecular design anarres molecular status --repository . anarres molecular verify --repository . Qualified Q07820 reaction-bank measurements; training outcomes remain sealed
Agentic finance anarres finance status --repository . anarres finance decide <panel.json> Starting-policy qualification and released retrospective checks
Vulnerability exploitation anarres vulnerability status anarres qualify <source> Sanitized CyberGym source qualification; task execution and policy probing remain gated

All maintained adapters declare a native source format. After installing one, use anarres adapter doctor <name> to inspect its exact contract, then run anarres init, anarres inspect, and anarres qualify. These commands route the native files without flattening their domain-specific structure.

Only the molecular adapter currently declares the portable policy-probe capability. Its probe remains dry-run unless execution is requested explicitly. The other adapters stop at source or runtime qualification in the shared path; study-specific execution commands retain their own completeness and safety gates.

Use status to inspect the released stage, profile to export supported candidate records, and verify to regenerate the adapter's maintained output. Some adapters expose additional study-specific reports. Run anarres <adapter> --help for their exact commands.

Add another domain

An unlisted domain needs a versioned native measurement record and a small adapter. The adapter preserves identifiers, failures, costs, measurement definitions, units, estimators, and artifact digests. It does not need to reimplement the domain's science in Rust.

Start with the adapter authoring guide and the scientific preservation guide. The native conformance path is:

anarres qualify candidate.profile-input.json
anarres measure candidate.profile-input.json --output candidate.profile.json
anarres validate candidate.profile-input.json candidate.profile.json

Two candidates can enter anarres design only when their domain, starting model or system, measurement setup, adapter revision, and coordinate definitions match. Predictive claims require a separate validation against later outcomes under the originating study's rules.