Evaluation walkthrough

Evaluation walkthrough

Govern one consequence. Inspect and verify the evidence.

Install Aarmos, configure one supported path, govern one consequential action, inspect the resulting evidence, and verify it against the supplied trust root. The CLI is distributed to authorized workspaces only and is not publicly issued; commands here are reference examples.

Start with installation

  1. 01

    Get Aarmos ready.

    Follow the installation guide to acquire and verify the signed CLI artifact, install it, and associate this device with your workspace.

  2. 02

    Configure one supported path.

    Scaffold the shipped Python example. It makes one outbound request through the local runtime using the included policy source.

    mkdir aarmos-evaluation && cd aarmos-evaluation
aarmos init --template python
python -m pip install -r requirements.txt

    Review policy.aarmos.toml, agent.py, and the generated signing material before running them. For path-specific coverage and evidence depth, read Run.

  3. 03

    Govern one consequence.

    Route the example’s supported outbound consequence through Aarmos and evaluate it under policy before governed execution.

    aarmos run python agent.py

    The command prints the receipt path written by this run. Keep that exact path for the inspection and verification steps below.

  4. 04

    Inspect the evidence.

    aarmos activity --runs

    Inspect the Decision and any applicable Authority separately, then distinguish the recorded Attempt from Effect evidence available at this boundary.

    Illustrative output

    run recorded · policy identified · receipt path shown

  5. 05

    Verify the evidence.

    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. Verification establishes only the claims supported by that artifact; it does not establish complete path coverage or a downstream business outcome. The standalone verifier binary is not publicly distributed.

    Illustrative output

    verified · artifact integrity and recorded chain checked

Honest limits

What this evaluation demonstrates—and what it does not.

What this evaluation demonstrates

  • Installing and configuring Aarmos on one supported path.
  • One governed consequential action.
  • Decision and applicable Authority kept separate.
  • Recorded Attempt and available Effect evidence.
  • Evidence verification against the supplied trust root.

What it does not demonstrate

  • Production rollout or enterprise fleet administration.
  • Complete path coverage or support for every framework or protocol.
  • Every consequence class or downstream business outcome.
  • Safety, compliance, or certification.

Understand the result.

Use the technical reference for the same command sequence, or review the pages below for current supported-path and evidence details.

Command referenceSupported boundariesEvidence and verification
GovernCan this agent do this?RunWill this work with my stack?ProveCan I prove what happened?
Govern. Run. Prove. Three distinct jobs across the governed lifecycle.