ARP Agent Runtime Proof

Local runtime identity verification

Prove the agent runtime you launched is the artifact you approved.

A replaced executable does not replace yesterday's process. ARP inspects the live local runtime, binds it to an explicit artifact expectation, and preserves uncertainty when the evidence is incomplete.

Download the latest release Run the reproducible demo
An approved artifact compared with a still-running process, resulting in an explicit unknown verdict.
ARP compares process evidence with the artifact you named. It never treats new bytes on disk as proof of loaded code.

The gap ARP closes

The file is current. Is the process?

  1. ApprovedArtifact expectationsha256: 7e31…a08c
  2. ObservedLive process identitypid 4812 · started earlier
  3. ReportedUNKNOWNPOSSIBLE_STALE_AFTER_REPLACEMENT

Narrow by design

Evidence without intervention

ARP observes. Your host remains in control.

Local only

No network listener, telemetry, or upload path. Raw arguments, environments, code, secrets, and transcripts stay out of MCP responses.

Read only

ARP does not stop processes, repair installations, rewrite Agent configuration, or promote an uncertain result to a match.

Host ready

Use the CLI, local stdio MCP server, launch Witness, or embedded Go SDK on macOS arm64, Linux amd64, and Windows amd64.

Five-minute check

Inspect before you trust

Download a signed release asset, verify its checksum, then inspect one explicit process or a bounded current-user inventory.

agent-runtime-proof doctor --format json
agent-runtime-proof inspect --all --limit 20
agent-runtime-proof verify \
  --expectation /absolute/path/expectation.json \
  --pid 1234 --format json
Open the complete quickstart →

Trust boundary

One proof, not a certification

ARP complements checksums, signatures, build attestations, SBOMs, sandboxing, and host policy. It answers one narrower question: does the live local process match the artifact expectation you approved?

Data handling Threat model Security policy