Domain integration status¶
Anarres separates software support from scientific validation. Format support means the software can read and validate the data. Predictive evidence means a measurement or decision was tested against later outcomes. One does not imply the other.
Conformance levels¶
- Protocol: the domain has a public measurement or experiment contract.
- Profile fixture: synthetic records exercise domain-shaped coordinates through schema validation and the native CLI.
- Native adapter: released evidence is projected into profiles with exact provenance and adapter conformance tests.
- Source runtime: the adapter can qualify a declared native source format through the unified source envelope and, when released, run a pinned starting-policy probe.
- Predictive evidence: a domain study evaluates a frozen measurement or decision against downstream outcomes under its native contract.
The first four levels concern interoperability. The fifth is scientific evidence and remains specific to the study, policy, target, and budget.
Native-adapter status does not imply source-runtime status. Most current
adapters reproduce released evidence. They become raw environment runners only
after declaring accepted source formats and passing qualification and probe
conformance on the real domain runtime. An adapter may release source
qualification before it releases policy execution. anarres inspect <source>
reports both capabilities separately, and anarres adapter doctor <name> is
the authoritative adapter-level check.
Current status¶
| Program | Example records | Installed command | Works with native files | Outcome evidence |
|---|---|---|---|---|
| Mathematics | Grouped-probe path and reference conformance | Native grouped-probe processor | Completed raw-attempt streams | Four-scale environment-utility release |
| Formal verification | Real Vero profiles | Installable Vero adapter with source and model-free runtime qualification | Runtime preflight available; sanitized policy execution pending | Positive external training-environment grids across Dafny and Verus; local Vero support and containment qualification remain pre-RL |
| Robotics | Real Can v1.4.1 candidate profiles | Installable CUPID candidate-measurement and result adapter | Can v1.4.1 HDF5 qualification is available; policy probing remains study-specific | Prospective PushT and Can results, plus retrospective multi-source records |
| Legal reasoning | Real SylloGym policy-response profiles | Installable SylloGym mixture adapter with a separate LAB regression report | Pinned public LAB task-set qualification; judge-backed policy probing remains gated | Prospective SylloGym and separate LAB regression-risk records |
| Materials science | Real MLIP candidate profiles | Installable cost-matched-panel adapter | OMat24 atomistic-bank qualification is available; Nequix policy probing remains in the native study runtime | Supervised phonon tests and a scored MLIP prospective test; the learned selector missed while deterministic baselines succeeded |
| Vulnerability exploitation | Public qualification protocol and released scaffold study | Installable qualification-only CyberGym adapter | Sanitized level 0--2 CyberGym panel qualification; execution and policy probing remain gated | Policy-relative measurement released; no environment comparison |
| Agentic systems | Public research protocols | Concrete domains use their own adapters | No umbrella runtime | Domain experiments remain study-specific |
| Molecular design | Real Q07820 reaction-bank profiles | Installable RxnFlow development adapter | Native reaction-environment qualification and a pinned, dry-run-by-default policy probe are available | Selector-fidelity confirmation passed; matched target-training outcomes remain unopened |
| Agentic finance | Real Business Bench qualification profile | Installable starting-policy qualification adapter | Pinned Business Bench process qualification; portable policy probing remains gated | Frozen retrospective source tests; no prospective environment outcome opened |
The profile schema can transport additional namespaced coordinates without a Rust change. That extensibility is not evidence that an unlisted adapter works or that one domain's predictor transfers to another.
Release rule¶
A domain moves to native-adapter status only when its checked-in workflow:
- reads a pinned native measurement artifact
- verifies source, subject, contract, and artifact identity
- preserves invalid, missing, and infrastructure outcomes
- emits versioned coordinate definitions with units and estimators
- passes schema and native CLI conformance tests
- retains the originating scientific record as authoritative
Predictive status requires a separate outcome-bearing experiment. Synthetic fixtures never satisfy that requirement. Umbrella programs do not receive generic adapters; their concrete studies expose domain-specific commands when a stable native producer is available.