Quickstart

One supported path. One governed consequence. Verifiable evidence.

This is the concise command reference for the Evaluation walkthrough. If the CLI is not installed and associated with your workspace, start at Install.

Current CLI contract: these commands are present in the shipped CLI. The CLI is distributed to authorized workspaces only and is not publicly issued — treat these as reference examples, not instructions you can run today. The example path remains subject to the support and qualification limits documented in Run.

1.
Create the example workspace
```
mkdir aarmos-evaluation && cd aarmos-evaluation
aarmos init --template python
python -m pip install -r requirements.txt
```
The shipped Python template includes one example target and its policy source. Review both before running them.
2.
Run one supported consequence
```
aarmos run python agent.py
```
The CLI starts or reuses the local runtime, routes the example request through it, and prints the receipt path.
3.
Inspect the local evidence
```
aarmos activity --runs
```
Use the printed receipt path for verification; activity is a read-only view of the local records.
4.
Verify the artifact
```
npm install @avar-standard/verify
```
Check the retained artifact with the in-browser verifier or the open verifier library on public npm — no Aarmos software required. The standalone verifier binary is not publicly distributed.

Read the result within its boundary.

A verified artifact establishes the integrity and recorded facts supported by that artifact. It does not establish complete path coverage, an unrecorded Effect, a downstream Outcome, safety, or compliance.

Continue with the CLI reference, supported boundary truth, or evidence and verification.

Create the example workspace

Run one supported consequence

Inspect the local evidence

Verify the artifact

Read the result within its boundary.