chio evidence

Export an evidence package from the receipt store and verify it offline against pinned partner keys, with no access to either operator.

On this page

All command families · Global flags

chio evidence

Export an offline evidence package from the local receipt database.

Command synopsistext

chio evidence [OPTIONS] <COMMAND>

chio evidence export Export a verifiable local evidence package into a directory.
chio evidence verify Verify an exported evidence package offline.
chio evidence import Import a verified bilateral evidence package for later federated delegation.
chio evidence federation-policy Create a signed bilateral receipt-sharing policy document.

chio evidence export

Export a verifiable local evidence package into a directory.

Command synopsistext

chio evidence export [OPTIONS] --output <OUTPUT>

--output <OUTPUT> Output directory for the evidence package. Must not already contain files. Required.
--capability <CAPABILITY> Filter tool receipts by capability ID.
--agent-subject <AGENT_SUBJECT> Filter tool receipts by agent subject public key.
--since <SINCE> Include tool receipts with timestamp >= this Unix seconds value.
--until <UNTIL> Include tool receipts with timestamp <= this Unix seconds value.
--tenant <TENANT> Tenant read boundary for the export. Derived from operator auth in service paths.
--admin-all Explicitly export across all tenants as an administrative operation.
--policy-file <POLICY_FILE> Optional policy file to attach to the export package.
--federation-policy <FEDERATION_POLICY> Optional signed bilateral federation policy that constrains the export scope.
--require-proofs Fail the export if any selected tool receipt lacks checkpoint coverage.
--agent <AGENT> Agent to select, by the name you gave it (fixer) or its DID; resolved to the agent’s subject key from the operator’s agents.

chio evidence verify

Verify an exported evidence package offline.

Command synopsistext

chio evidence verify [OPTIONS] --input <INPUT>

--input <INPUT> Input directory containing a previously exported evidence package. Required.
--ledger Also replay every hold (reserved = committed + released + retained + outstanding) and check P + R + L + F = D for each funding source in an included work export, naming any hold or allocation that breaks.
--trust <FILE> Trust file to verify against instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). A trust file beside the input is never read on its own. Reads CHIO_TRUST.
--at <TIME> Evaluate freshness, expiry, and revocation epochs at this time (RFC 3339 or Unix seconds) instead of now.
--trusted-kernel-pubkey <KEY> One kernel public key to trust for this run, as a single-key override of the trust file’s receipt-kernel pins. Repeat to allow key rotation.
--partner <NAME> Partner name from chio partner add. Every co-signed receipt in the package must carry this partner’s signature, verified against the receipt signer pinned from its card; a package missing either side fails.

Example from the first-call project

Run from the first-call example project. For evidence verification, first export the evidence package.

first-call · evidence-verifytranscript

$ chio evidence verify --input ./evidence

evidence package verified
tool_receipts:          2
child_receipts:         0
checkpoints:            0
checkpoint_publications: 0
checkpoint_witnesses:   0
checkpoint_consistency_proofs: 0
checkpoint_equivocations: 0
capability_lineage:     2
inclusion_proofs:       0
uncheckpointed_receipts: 2
authorized_receipts:     1
trace_observations:      0
advisory_evaluations:    0
verified_files:         12
child_receipt_scope:    FullQueryWindow
transparency_preview_logs: 0
publication_state:      transparency_preview

exit 0in my-agent

chio evidence import

Import a verified bilateral evidence package for later federated delegation.

Command synopsistext

chio evidence import [OPTIONS] --input <INPUT>

--input <INPUT> Input directory containing a previously exported evidence package. Required.

chio evidence federation-policy

Create a signed bilateral receipt-sharing policy document.

Command synopsistext

chio evidence federation-policy [OPTIONS] <COMMAND>

chio evidence federation-policy create

Create a signed bilateral federation policy for receipt sharing.

Command synopsistext

chio evidence federation-policy create [OPTIONS] --output <OUTPUT> --signing-seed-file <SIGNING_SEED_FILE> --issuer <ISSUER> --partner <PARTNER> --expires-at <EXPIRES_AT>

--output <OUTPUT> Output JSON file for the signed policy document. Required.
--signing-seed-file <SIGNING_SEED_FILE> Persistent seed file used to sign the policy document. Required.
--issuer <ISSUER> Human-readable identifier for the issuing organization. Required.
--partner <PARTNER> Human-readable identifier for the receiving organization. Required.
--capability <CAPABILITY> Optional capability scope for the shared export.
--agent-subject <AGENT_SUBJECT> Optional agent subject scope for the shared export.
--since <SINCE> Optional lower timestamp bound for the allowed export window.
--until <UNTIL> Optional upper timestamp bound for the allowed export window.
--tenant <TENANT> Tenant read boundary for exports performed under this policy.
--admin-all Explicitly allow administrative exports across all tenants under this policy.
--expires-at <EXPIRES_AT> Expiration time for the policy document, in Unix seconds. Required.
--require-proofs Require full checkpoint coverage for any export performed under this policy.
--purpose <PURPOSE> Optional reason or purpose string embedded in the policy document.