CLI Reference

Synopsis

chio [OPTIONS] <COMMAND>

An entry names one command path. The block under it is its usage line: everything outside brackets is required, [OPTIONS] stands for the flags listed beneath it plus the 7 global flags, and a value in angle brackets is the placeholder for that argument. Every command answers --help with its usage, arguments, and options.

Global flags

These flags are declared on the root command. The second column says how far each one reaches: 7 of them are accepted by all 437 command paths, before or after the subcommand name. A command that gives one of them a different meaning lists it in its own entry instead.

Commands

45 top-level commands, and 392 subcommands under them. Each entry below carries the command that owns it in its heading, so the heading is the invocation.

chio key

Create and show the operator identity key.

chio key [OPTIONS] <COMMAND>

• chio key init Create the operator identity key if it is absent, then print the operator DID, the kernel key fingerprint, and where the key is stored.
• chio key show Print the public key, DID, and custody description for a key reference.

Example

Run once per operator. The key stays on this machine.

chio key init

operator   did:chio:z6Mkf3…Qp9
kernel     4f1c…a2e9
stored     ~/.chio/keys, mode 600

chio key init

Create the operator identity key if it is absent, then print the operator DID, the kernel key fingerprint, and where the key is stored.

chio key init [OPTIONS]

• --key <KEY> Key reference: a file path, keychain:<service>/<account>, secret-service:<name>, or credential:<name>. Without it, the key is a file under ~/.chio/keys.

chio key show

Print the public key, DID, and custody description for a key reference.

chio key show [OPTIONS]

• --key <KEY> Key reference: a file path, keychain:<service>/<account>, secret-service:<name>, or credential:<name>. Without it, the key is a file under ~/.chio/keys.

chio new

Create a computer: a versioned environment where authority, resources, and work live.

chio new [OPTIONS] [NAME]

• [NAME] Name of the computer and of the directory it is created in.
• --example <EXAMPLE> Create the directory from a published example bundle instead of an empty computer; the bundle’s checksum and the index signature are verified before it unpacks.
• --list-examples List the published examples: name, face, languages, and what each runs.

Example

Create the Quickstart computer and move into it.

chio new quickstart && cd quickstart

created    quickstart, 14 tests, 3 failing: issues #412, #413, #414
computer   quickstart, owned by did:chio:z6Mkf3…Qp9

chio agent

Run demonstration agents against a service you publish.

chio agent [OPTIONS] <COMMAND>

• chio agent demo Create a demonstration caller, or drive demo traffic from one.
• chio agent token Print the capability token a caller holds, for use as a bearer credential.

Example

Create a caller for the published pricing service.

chio agent demo --out caller.json

agent      did:chio:z6MkbY4…e1R
key        held by the agent, not by your kernel
connects   https://127.0.0.1:9440/pricing/mcp

chio agent demo

Create a demonstration caller, or drive demo traffic from one.

chio agent demo [OPTIONS]

• --out <OUT> Write the new caller’s connection file to this path.
• --traffic <TRAFFIC> Send demo traffic as the caller described by this connection file.
• --with-stranger Also send calls from a second agent that holds no grant.

chio agent token

Print the capability token a caller holds, for use as a bearer credential.

chio agent token [OPTIONS] <CALLER>

• <CALLER> Connection file written by chio agent demo --out. Required.

chio approvals

List approval requests waiting for a person.

chio approvals [OPTIONS] <COMMAND>

Example

A rule that requires approval pauses the matching call until a person signs for it.

chio approvals pending

pending    apr-01ac…5e2   z6MkbY4…e1R   quote sku-301 at 80%   waiting 12s

chio approvals pending

List pending approval requests: the approval ID, the caller, the request it binds, and how long it has waited.

chio approvals pending [OPTIONS]

chio approve

Sign an approval for one pending request.

chio approve [OPTIONS] <APPROVAL_ID>

• <APPROVAL_ID> Approval identifier from chio approvals pending, such as apr-01ac…5e2. Required.

Example

Approve the request that chio approvals pending listed.

chio approve apr-01ac…5e2

approved   apr-01ac…5e2, signed by did:chio:z6Mkf3…Qp9, binds request 9e1f…c2a0

chio partner

Add partners from their partner cards.

chio partner [OPTIONS] <COMMAND>

• chio partner demo Run a demonstration partner on this machine, with its own kernel, keys, policy, and agents, and write its partner card.
• chio partner add Add a partner from its partner card and pin its kernel key.
• chio partner status Print the stored record for a partner: pinned kernel key, handshake schema, assurance tier against your floor, admitted capabilities, ladder manifest, and the key-rotation deadline.
• chio partner handshake Run the kernel handshake with a partner now, re-verify its pinned key and ladder manifest, and renew the rotation deadline.

Example

Run a demonstration partner, then add its card over the optional iroh lane.

chio partner demo --out partner-card.json
chio partner add partner-card.json --name partner --transport iroh

partner    did:chio:z6MkpA7…c2T, named partner
kernel     9b07…d31c, pinned from its card
transport  iroh, endpoint 3fa8…91be, authenticated at handshake
lanes      signals · revocation · co-sign

chio partner demo

Run a demonstration partner on this machine, with its own kernel, keys, policy, and agents, and write its partner card.

chio partner demo [OPTIONS] --out <OUT>

• --out <OUT> Path for the partner card. Required.

chio partner add

Add a partner from its partner card and pin its kernel key.

chio partner add [OPTIONS] --name <NAME> <CARD>

• <CARD> Partner card file. Required.
• --name <NAME> Local name for the partner, used by Computer.connect. Required.
• --transport <TRANSPORT> Transport the two kernels use. Default https. Values https, iroh.

chio partner status

Print the stored record for a partner: pinned kernel key, handshake schema, assurance tier against your floor, admitted capabilities, ladder manifest, and the key-rotation deadline.

chio partner status [OPTIONS] <NAME>

• <NAME> Partner name given to chio partner add. Required.

chio partner handshake

Run the kernel handshake with a partner now, re-verify its pinned key and ladder manifest, and renew the rotation deadline.

chio partner handshake [OPTIONS] <NAME>

• <NAME> Partner name given to chio partner add. Required.

chio work

Run work commitments through the owner service.

chio work [OPTIONS] <COMMAND>

• chio work init Initialize a private work state directory from a host profile.
• chio work serve Serve the owner work service from a state directory until SIGINT or SIGTERM.
• chio work prepare Prepare one owner artifact, such as a Select or an Agreement, from a chio.work.preparation.v1 document.
• chio work fund Fund an agreement’s exclusive allocation on its configured rail and attach the funding reference to the commitment.
• chio work submit Submit one work command under its caller-supplied command ID.
• chio work inspect Read the work view for a handle, or for an original command or preparation ID.
• chio work collect Reconcile finished work and record its results, with no second dispatch.
• chio work export Export the signed records for a work commitment as an evidence package.

chio work init

Initialize a private work state directory from a host profile.

chio work init [OPTIONS] --config <CONFIG> --state <STATE>

• --config <CONFIG> Host profile. Required.
• --state <STATE> Private work state directory. Required.

chio work serve

Serve the owner work service from a state directory until SIGINT or SIGTERM.

chio work serve [OPTIONS] --state <STATE>

• --state <STATE> Private work state directory. Required.

chio work prepare

Prepare one owner artifact, such as a Select or an Agreement, from a chio.work.preparation.v1 document.

chio work prepare [OPTIONS] --state <STATE> <PREPARATION>

• <PREPARATION> Preparation document (chio.work.preparation.v1). Required.
• --state <STATE> Private work state directory. Required.

chio work fund

Fund an agreement’s exclusive allocation on its configured rail and attach the funding reference to the commitment.

chio work fund [OPTIONS] --state <STATE> <PREPARATION_ID>

• <PREPARATION_ID> Preparation ID printed by chio work prepare. Required.
• --state <STATE> Private work state directory. Required.

chio work submit

Submit one work command under its caller-supplied command ID.

chio work submit [OPTIONS] --state <STATE> <COMMAND>

• <COMMAND> Work command document (chio.work.command.v1). Required.
• --state <STATE> Private work state directory. Required.

chio work inspect

Read the work view for a handle, or for an original command or preparation ID.

chio work inspect [OPTIONS] --state <STATE> <ID>

• <ID> Work handle, or the original command or preparation ID. Required.
• --state <STATE> Private work state directory. Required.
• --costs Add production, verification, and coordination cost, and the verification-to-production ratio, from the receipts both kernels signed.

chio work collect

Reconcile finished work and record its results, with no second dispatch.

chio work collect [OPTIONS] --state <STATE> <ID>

• <ID> Work handle, or the original command ID. Required.
• --state <STATE> Private work state directory. Required.

chio work export

Export the signed records for a work commitment as an evidence package.

chio work export [OPTIONS] --state <STATE> --out <OUT> <ID>

• <ID> Work handle, or the original command ID. Required.
• --state <STATE> Private work state directory. Required.
• --out <OUT> Evidence package directory. Required.

chio recovery

Inspect, explain, and resume recovery workflows.

chio recovery [OPTIONS] <COMMAND>

• chio recovery inspect Read a recovery workflow’s state and its exact preview under current approval authority.
• chio recovery explain Read the signed, audience-safe explanation of a recovery workflow and the offers it carries.
• chio recovery resume Resume a workflow after its approval; the kernel rechecks current facts before dispatch.

chio recovery inspect

Read a recovery workflow’s state and its exact preview under current approval authority.

chio recovery inspect [OPTIONS] --capability <CAPABILITY> --workflow-id <WORKFLOW_ID>

• --endpoint <ENDPOINT> Recovery host endpoint: an https:// URL for a remote host, or unix:///path/to/host.sock for a process host on this machine. Exactly one of --endpoint and --state is required.
• --state <STATE> Process host state directory; the endpoint is the host socket recorded there.
• --capability <CAPABILITY> Capability token file that authorizes this operation. Required.
• --workflow-id <WORKFLOW_ID> Recovery workflow identifier. Required.

chio recovery explain

Read the signed, audience-safe explanation of a recovery workflow and the offers it carries.

chio recovery explain [OPTIONS] --capability <CAPABILITY> --workflow-id <WORKFLOW_ID>

• --endpoint <ENDPOINT> Recovery host endpoint: an https:// URL for a remote host, or unix:///path/to/host.sock for a process host on this machine. Exactly one of --endpoint and --state is required.
• --state <STATE> Process host state directory; the endpoint is the host socket recorded there.
• --capability <CAPABILITY> Capability token file that authorizes this operation. Required.
• --workflow-id <WORKFLOW_ID> Recovery workflow identifier. Required.

chio recovery resume

Resume a workflow after its approval; the kernel rechecks current facts before dispatch.

chio recovery resume [OPTIONS] --capability <CAPABILITY> --workflow-id <WORKFLOW_ID>

• --endpoint <ENDPOINT> Recovery host endpoint: an https:// URL for a remote host, or unix:///path/to/host.sock for a process host on this machine. Exactly one of --endpoint and --state is required.
• --state <STATE> Process host state directory; the endpoint is the host socket recorded there.
• --capability <CAPABILITY> Capability token file that authorizes this operation. Required.
• --workflow-id <WORKFLOW_ID> Recovery workflow identifier. Required.

chio process

Host durable agent processes backed by MCP tool servers.

chio process [OPTIONS] <COMMAND>

• chio process init Initialize an empty private state directory from a host configuration.
• chio process serve Serve authenticated workers until SIGINT or SIGTERM, then drain calls.
• chio process run Run a declared worker application with persistent, bounded restart attempts (Linux).
• chio process status Read the last native-runner snapshot while the host is running or stopped.
• chio process state Read retained application state without launching tools or issuing credentials.
• chio process logs Read bounded, private stdout and stderr logs from a retained worker attempt.
• chio process credential Issue a private connection descriptor while the host is stopped.
• chio process revoke Revoke a process’s worker credentials while the host is stopped.
• chio process revoke-capability Permanently revoke the issued capability and its descendants while the host is stopped.
• chio process cancel Permanently cancel a process subtree while the host is stopped.
• chio process export Retire the stopped host where it is and write the manifest that lets a copy be imported elsewhere.
• chio process import Re-anchor a copied host state directory at its new location and verify it against its manifest.
• chio process attest-call Observe one retained call and its continuation custody while the host is stopped (Linux).
• chio process verify-call Verify a retained call observation without opening host state.
• chio process attest-run Attest completed fixed fan-out results and the retained aggregate usage (Linux).
• chio process verify-run Verify completed fan-out evidence against operator pins.
• chio process attest-outcomes Observe finished workers, issued graphs, call outcomes, and durable family usage (Linux).
• chio process verify-outcomes Verify worker outcomes and their issued authority without opening host state.
• chio process qualify Run the confined-swarm qualification matrix on this Linux host and verify a matrix another operator ran.
• chio process prepare-broker-call Sign one provider request with the host’s retained process proof key.

Example

Initialize a host from its configuration, run the declared worker application, and read the runner snapshot.

chio process init --config host.json --state .chio
chio process run --state .chio --plan process.json
chio process status --state .chio

chio process init

Initialize an empty private state directory from a host configuration.

chio process init [OPTIONS] --config <CONFIG> --state <STATE>

• --config <CONFIG> Host configuration file. Required.
• --state <STATE> Private host state directory. Required.
• --local-tools Discover and authorize the configured local tools. Starts their commands; provides no OS confinement.
• --aggregate-invocations <AGGREGATE_INVOCATIONS> Signed invocation budget shared by the root and all descendants.
• --swarm-plan <SWARM_PLAN> Bind a bounded fan-out plan to this host’s issued capabilities. Requires --aggregate-invocations.

chio process serve

Serve authenticated workers until SIGINT or SIGTERM, then drain calls.

chio process serve [OPTIONS] --state <STATE> --socket <SOCKET>

• --state <STATE> Private host state directory. Required.
• --socket <SOCKET> Socket in a separate private directory exposed to worker sandboxes. Required.

chio process run

Run a declared worker application with persistent, bounded restart attempts (Linux).

chio process run [OPTIONS] --state <STATE> --plan <PLAN>

• --state <STATE> Private host state directory. Required.
• --plan <PLAN> Worker application plan. Required.

chio process status

Read the last native-runner snapshot while the host is running or stopped.

chio process status [OPTIONS] --state <STATE>

• --state <STATE> Private host state directory. Required.

chio process state

Read retained application state without launching tools or issuing credentials.

chio process state [OPTIONS] --state <STATE> --process <PROCESS>

• --state <STATE> Private host state directory. Required.
• --process <PROCESS> Process name from the host configuration. Required.
• --blob <BLOB> Read one immutable blob instead of the checkpoint.

chio process logs

Read bounded, private stdout and stderr logs from a retained worker attempt.

chio process logs [OPTIONS] --state <STATE> --process <PROCESS> --attempt <ATTEMPT>

• --state <STATE> Private host state directory. Required.
• --process <PROCESS> Process name from the host configuration. Required.
• --attempt <ATTEMPT> Worker attempt number. Required.

chio process credential

Issue a private connection descriptor while the host is stopped.

chio process credential [OPTIONS] --state <STATE> --process <PROCESS> --socket <SOCKET> --out <OUT>

• --state <STATE> Private host state directory. Required.
• --process <PROCESS> Process name from the host configuration. Required.
• --socket <SOCKET> Worker socket the descriptor connects to. Required.
• --out <OUT> New file in a private directory. Existing files are never replaced. Required.

chio process revoke

Revoke a process’s worker credentials while the host is stopped.

chio process revoke [OPTIONS] --state <STATE> --process <PROCESS>

• --state <STATE> Private host state directory. Required.
• --process <PROCESS> Process name from the host configuration. Required.

chio process revoke-capability

Permanently revoke the issued capability and its descendants while the host is stopped.

chio process revoke-capability [OPTIONS] --state <STATE> --process <PROCESS>

• --state <STATE> Private host state directory. Required.
• --process <PROCESS> Process name from the host configuration. Required.

chio process cancel

Permanently cancel a process subtree while the host is stopped.

chio process cancel [OPTIONS] --state <STATE> --process <PROCESS>

• --state <STATE> Private host state directory. Required.
• --process <PROCESS> Process name from the host configuration. Required.

chio process export

Retire the stopped host where it is and write the manifest that lets a copy be imported elsewhere.

chio process export [OPTIONS] --state <STATE>

• --state <STATE> Private host state directory. Required.

chio process import

Re-anchor a copied host state directory at its new location and verify it against its manifest.

chio process import [OPTIONS] --state <STATE>

• --state <STATE> Private host state directory. Required.

chio process attest-call

Observe one retained call and its continuation custody while the host is stopped (Linux).

chio process attest-call [OPTIONS] --state <STATE> --request <REQUEST> --context <CONTEXT> --response <RESPONSE> --out <OUT>

• --state <STATE> Private host state directory. Required.
• --request <REQUEST> Original caller request. Required.
• --context <CONTEXT> Runtime, process, and capability context of the call. Required.
• --response <RESPONSE> Response the caller received. Required.
• --out <OUT> Call attestation artifact. Required.

chio process verify-call

Verify a retained call observation without opening host state.

chio process verify-call [OPTIONS] --artifact <ARTIFACT> --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY> --runtime-id <RUNTIME_ID> --request <REQUEST> --context <CONTEXT>

• --artifact <ARTIFACT> Attestation artifact written by the matching attest command. Required.
• --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY> Kernel public key the verifier pins. Required.
• --runtime-id <RUNTIME_ID> Runtime identifier the artifact must name. Required.
• --request <REQUEST> Original caller request, independently retained by the verifier. Required.
• --context <CONTEXT> Original runtime, process, and capability context, independently retained. Required.
• --trusted-launch-policy-signer <TRUSTED_LAUNCH_POLICY_SIGNER> External operator pin for each native server, repeated as SERVER=PUBLIC_KEY.
• --trusted-broker-host-config <TRUSTED_BROKER_HOST_CONFIG> Independently retained, normalized host config for brokered calls.
• --trusted-keylog-verifier <TRUSTED_KEYLOG_VERIFIER> Independently synchronized verifier for governed parent issuance.

chio process attest-run

Attest completed fixed fan-out results and the retained aggregate usage (Linux).

chio process attest-run [OPTIONS] --state <STATE> --plan <PLAN> --out <OUT>

• --state <STATE> Private host state directory. Required.
• --plan <PLAN> Worker application plan. Required.
• --out <OUT> Run attestation artifact. Required.

chio process verify-run

Verify completed fan-out evidence against operator pins.

chio process verify-run [OPTIONS] --artifact <ARTIFACT> --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY> --runtime-id <RUNTIME_ID>

• --artifact <ARTIFACT> Attestation artifact written by the matching attest command. Required.
• --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY> Kernel public key the verifier pins. Required.
• --runtime-id <RUNTIME_ID> Runtime identifier the artifact must name. Required.
• --trusted-launch-policy-signer <TRUSTED_LAUNCH_POLICY_SIGNER> External operator pin for each native server, repeated as SERVER=PUBLIC_KEY.

chio process attest-outcomes

Observe finished workers, issued graphs, call outcomes, and durable family usage (Linux).

chio process attest-outcomes [OPTIONS] --state <STATE> --plan <PLAN> --out <OUT>

• --state <STATE> Private host state directory. Required.
• --plan <PLAN> Worker application plan. Required.
• --out <OUT> Outcome attestation artifact. Required.

chio process verify-outcomes

Verify worker outcomes and their issued authority without opening host state.

chio process verify-outcomes [OPTIONS] --artifact <ARTIFACT> --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY> --runtime-id <RUNTIME_ID>

• --artifact <ARTIFACT> Attestation artifact written by the matching attest command. Required.
• --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY> Kernel public key the verifier pins. Required.
• --runtime-id <RUNTIME_ID> Runtime identifier the artifact must name. Required.
• --trusted-launch-policy-signer <TRUSTED_LAUNCH_POLICY_SIGNER> External operator pin for each native server, repeated as SERVER=PUBLIC_KEY.

chio process qualify

Run the confined-swarm qualification matrix on this Linux host and verify a matrix another operator ran.

chio process qualify [OPTIONS] <COMMAND>

• chio process qualify run Run the seven qualification scenarios: two under the cage, five with confined tools and worker containers supervised by chio process run.
• chio process qualify verify Verify a received matrix artifact against independently held operator pins, without opening the host’s state.
• chio process qualify test-evidence Check that every scenario in a verified matrix carries the test evidence its decision rests on.

chio process qualify run

Run the seven qualification scenarios: two under the cage, five with confined tools and worker containers supervised by chio process run.

chio process qualify run [OPTIONS] --cage-init <PATH> --probe <PATH> --reader <PATH> --worker-image <IMAGE> --output <DIR> --receipt-rollback-anchor-root <PATH>

• --cage-init <PATH> Static chio-cage-init helper the confined scenarios launch under. Required.
• --probe <PATH> Enforcement probe binary the cage scenarios run. Required.
• --reader <PATH> Confined repository reader tool the worker scenarios call. Required.
• --worker-image <IMAGE> Worker container image, by sha256: image id. Required.
• --output <DIR> New directory for the matrix artifact and its evidence. Required.
• --receipt-rollback-anchor-root <PATH> Private receipt rollback anchor directory on a different filesystem from the receipt database. Required.

chio process qualify verify

Verify a received matrix artifact against independently held operator pins, without opening the host’s state.

chio process qualify verify [OPTIONS] --artifact <PATH> --trusted-pins <PATH>

• --artifact <PATH> Matrix artifact to verify. Required.
• --trusted-pins <PATH> Operator pins obtained independently of the artifact: kernel key, runtime id, and launch signer. Required.

chio process qualify test-evidence

Check that every scenario in a verified matrix carries the test evidence its decision rests on.

chio process qualify test-evidence [OPTIONS] --artifact <PATH> --trusted-pins <PATH>

• --artifact <PATH> Matrix artifact to check. Required.
• --trusted-pins <PATH> Operator pins obtained independently of the artifact. Required.

chio process prepare-broker-call

Sign one provider request with the host’s retained process proof key.

chio process prepare-broker-call [OPTIONS] --state <STATE> --process <PROCESS> --operation-key <OPERATION_KEY> --capability <CAPABILITY> --request <REQUEST> --out <OUT>

• --state <STATE> Private host state directory. Required.
• --process <PROCESS> Process name from the host configuration. Required.
• --operation-key <OPERATION_KEY> Operation key that names the call. Required.
• --capability <CAPABILITY> Capability token the call is made under. Required.
• --request <REQUEST> Provider request to sign. Required.
• --out <OUT> Signed broker request. Required.

chio security

Prepare, supervise, and exercise the confined runtime on this host.

chio security [OPTIONS] <COMMAND>

• chio security selftest Run the enforcement suites that ship with this release against the installed binaries on this host, and keep the evidence.
• chio security preflight Prove the host, its bearer roles, its signed launch material, and its durable stores before the confined runtime starts.
• chio security supervise Run one service under systemd: credentials from the credentials directory, readiness on the notify socket, stop signals forwarded.
• chio security shadow-migrate Verify registry evidence and atomically write a deterministic migration report.
• chio security provision-reference-runtime Provision signed launch material for one confined tool at an enforcing migration stage.
• chio security provision-native-mcp-demo Provision a signed native MCP launch at migration stage Disabled, to review the material before enforcing it.

Example

Run every enforcement suite the host supports and keep the logs, exit statuses, and manifest together.

chio security selftest --evidence ./deployment-evidence

suite            result
cage             pass
restart          pass
caller-delivery  pass
deception        pass
temporal         pass   10 inventories, 40 tests
keyring          pass
broker           pass
7 suites passed; evidence in ./deployment-evidence

chio security selftest

Run the enforcement suites that ship with this release against the installed binaries on this host, and keep the evidence.

chio security selftest [OPTIONS] [SUITE]...

• [SUITE]... Suites to run: cage, restart, caller-delivery, deception, temporal, keyring, broker, timing. Without one, every suite the host supports. timing runs the three constant-time harnesses and reports max|t| against the 4.5 threshold, a result that holds only for the host it ran on.
• --list List the suites, their case counts, and what each needs from the host.
• --evidence <DIR> Directory for the per-suite logs, exit statuses, and a SHA-256 manifest. Must be new.
• --portable Run only the cases that need no Linux enforcement, for a developer laptop.
• --require-all Fail instead of skipping a suite the host cannot run.

chio security preflight

Prove the host, its bearer roles, its signed launch material, and its durable stores before the confined runtime starts.

chio security preflight [OPTIONS] [COMMAND]...

• [COMMAND]... The wrapped MCP server command and its arguments, exactly as the launch passes them after --.
• --require-enforcement Fail when the host cannot enforce the cage or the launch material authorizes without confining.
• --signed-manifest <PATH> Publisher-signed manifest of the wrapped server.
• --manifest-public-key <PUBLIC_KEY> Independently registered public key that signed the manifest.
• --cage-policy <PATH> Canonical signed native-launch policy for the wrapped server.
• --cage-policy-signer <PUBLIC_KEY> Independently pinned public key for the native-launch policy signer.
• --server-id <SERVER_ID> Server identifier the manifest and policy must belong to.

chio security supervise

Run one service under systemd: credentials from the credentials directory, readiness on the notify socket, stop signals forwarded.

chio security supervise [OPTIONS] <COMMAND>...

• <COMMAND>... The service command and its arguments, after --. Required.
• --credentials-dir <PATH> Directory holding the credential files; systemd sets it for every unit with LoadCredential=. Reads CREDENTIALS_DIRECTORY.
• --credential-env <VARIABLE=CREDENTIAL> Deliver the credential file CREDENTIAL to the service as VARIABLE. Repeat for every secret.
• --ready-http <URL> Report readiness once a GET of this URL succeeds.
• --ready-unix-socket <PATH> Report readiness once this Unix socket accepts a connection from the supervised service.
• --ready-timeout <SECONDS> Seconds the service may take to become ready before it is stopped. Default 60.
• --stop-grace <SECONDS> Seconds a stopped service may take to drain before SIGKILL. Default 30.
• --exec Deliver the credentials and replace this process with the service instead of supervising it.

chio security shadow-migrate

Verify registry evidence and atomically write a deterministic migration report.

chio security shadow-migrate [OPTIONS] --input <PATH> --output <PATH>

• --input <PATH> Closed JSON inventory containing registered keys, manifests, receipts, and observations. Required.
• --output <PATH> Destination for the canonical JSON report. Required.

chio security provision-reference-runtime

Provision signed launch material for one confined tool at an enforcing migration stage.

chio security provision-reference-runtime [OPTIONS] --output-dir <PATH> --cage-init <PATH> --target <PATH> --execution-uid <UID> --execution-gid <GID> --server-id <SERVER_ID>

• --output-dir <PATH> Directory to create with every artifact; an existing one is revalidated. Required.
• --runtime-security-dir <PATH> Directory the runtime reads the ledger and receipt material from, when it differs from the output directory.
• --cage-init <PATH> Static position-independent chio-cage-init the policy binds. Required.
• --max-artifact-bytes <MAX_ARTIFACT_BYTES> Signed per-artifact retention ceiling for the helper, target, and runtime files (at most 256 MiB). Default 1048576.
• --receipt-rollback-anchor-root <PATH> Private external receipt rollback anchor directory, on a different filesystem from the receipt database. Required for the Enforced stage.
• --broker-binding <PATH> Reviewed JSON socket path, authentication digest, and broker peer identity.
• --tools-fixture <PATH> Reviewed tools/list fixture of the target.
• --discover-tools Spawn the target once and review its own tools/list.
• --target <PATH> The wrapped MCP server executable. Required.
• --target-arg <VALUE> One argument of the wrapped server, in order. Repeat for each.
• --working-directory <PATH> Working directory of the wrapped server; its parent directory by default.
• --read-path <PATH> A path the wrapped server may read. Repeat for each grant.
• --write-path <PATH> A path the wrapped server may write. Repeat for each grant.
• --runtime-file <PATH> Interpreter or shared object a dynamically linked target needs; each must also be a read path.
• --syscall-profile <SYSCALL_PROFILE> Reviewed syscall set; minimal by default. Values minimal, standard.
• --execution-uid <UID> Non-root UID applied to the target before sandboxing. Required.
• --execution-gid <GID> Non-root primary GID applied to the target before sandboxing. Required.
• --execution-supplementary-gid <GID> Supplementary target GID, in ascending order. Repeat for each.
• --server-id <SERVER_ID> Server identifier the manifest and the policy bind. Required.
• --server-name <SERVER_NAME> Server name committed to the signed manifest. Default Chio reference tool.
• --server-version <SERVER_VERSION> Server version committed to the signed manifest. Default 1.
• --stage <STAGE> Stage the migration ledger is promoted to. Default enforced. Values shadow, enforced.

chio security provision-native-mcp-demo

Provision a signed native MCP launch at migration stage Disabled, to review the material before enforcing it.

chio security provision-native-mcp-demo [OPTIONS] --output-dir <PATH> --target <PATH> --execution-uid <UID> --execution-gid <GID> --server-id <SERVER_ID>

• --output-dir <PATH> New absolute output directory, or an exact prior provision for an idempotent rerun. Required.
• --runtime-security-dir <PATH> Absolute directory committed to runtime policy paths. Defaults to the output directory.
• --tools-fixture <PATH> Reviewed JSON tools/list fixture used to build the signed manifest.
• --discover-tools Spawn the target once and review its own tools/list.
• --target <PATH> Absolute canonical MCP server executable bound into the launch policy. Required.
• --target-arg <VALUE> One target argv element after the executable. Repeat for each.
• --working-directory <PATH> Absolute canonical working directory. Defaults to the target’s parent.
• --execution-uid <UID> Non-root UID applied to the target before sandboxing. Required.
• --execution-gid <GID> Non-root primary GID applied to the target before sandboxing. Required.
• --execution-supplementary-gid <GID> Supplementary target GID, in ascending order. Repeat for each.
• --server-id <SERVER_ID> Server identifier committed to the manifest, policy, and migration ledger. Required.
• --server-name <SERVER_NAME> Server name committed to the signed manifest.
• --server-version <SERVER_VERSION> Server version committed to the signed manifest. Default 1.

chio release

Verify Chio releases and check a node before it upgrades.

chio release [OPTIONS] <COMMAND>

• chio release verify Verify a Chio release: the checksum, the signing identity, and the build provenance of the installed binary or of downloaded archives.
• chio release check Check whether this node can move to a release before you stop it: store schemas, flag changes, and rollback.

Example

Verify the binary on your PATH and the formal proof report its release carries.

chio release verify --evidence formal

binary     /usr/local/bin/chio  chio 0.2.0  aarch64-apple-darwin
checksum   matches SHA256SUMS for v0.2.0
signed by  release.yml on backbay-labs/chio, issuer token.actions.githubusercontent.com
provenance SLSA v1, 5 subjects, tag v0.2.0
formal     proof report bound to v0.2.0, every gate passed
verified

chio release verify

Verify a Chio release: the checksum, the signing identity, and the build provenance of the installed binary or of downloaded archives.

chio release verify [OPTIONS] [ARCHIVE]...

• [ARCHIVE]... Release archives to verify. Without one, the running chio binary.
• --tag <TAG> Release to verify the archives against. Defaults to the version the archive or binary names.
• --evidence <KIND> Also verify one attached evidence set. Repeat for several. Values formal, threat-coverage, reproducible, qualification, all.
• --out <FILE> Write the verification report as JSON to this file.

chio release check

Check whether this node can move to a release before you stop it: store schemas, flag changes, and rollback.

chio release check [OPTIONS] <VERSION>

• <VERSION> Target release, such as 0.2.0. Required.
• --state <DIR> State directory or store the node uses. Repeat for each; defaults to ~/.chio/state.
• --unit <UNIT> systemd unit or service command line to check for renamed and removed flags. Repeat for each.

chio anchor

Anchor receipt checkpoints to public ledgers and verify inclusion proofs offline.

chio anchor [OPTIONS] <COMMAND>

• chio anchor batch Roll unanchored receipt checkpoints into a signed chio.anchor_batch.v1 and publish its root to the profile’s lanes.
• chio anchor prove Build a chio.anchor-proof-bundle.v2 for one receipt: its checkpoint inclusion proof and every lane’s anchor record.
• chio anchor verify Verify a proof bundle offline, lane by lane, failing closed on any lane the witness policy requires.

Example

Verify a receipt’s proof bundle offline against your kernel key.

chio anchor verify proof.json --trusted-kernel-pubkey 4f1c…a2e9

checkpoint  #12, inclusion verified
evm         ChioRootRegistry on Base, sequence 12, final
solana      memo confirmed
rekor       witness entry verified
verified

chio anchor batch

Roll unanchored receipt checkpoints into a signed chio.anchor_batch.v1 and publish its root to the profile’s lanes.

chio anchor batch [OPTIONS] --profile <FILE>

• --profile <FILE> Anchor profile file. Required.
• --through <CHECKPOINT_SEQ> Last checkpoint sequence to include.

chio anchor prove

Build a chio.anchor-proof-bundle.v2 for one receipt: its checkpoint inclusion proof and every lane’s anchor record.

chio anchor prove [OPTIONS] --output <FILE> <RECEIPT_ID>

• <RECEIPT_ID> Receipt to prove. Required.
• --output <FILE> Proof bundle file. Required.

chio anchor verify

Verify a proof bundle offline, lane by lane, failing closed on any lane the witness policy requires.

chio anchor verify [OPTIONS] --trusted-kernel-pubkey <HEX> <BUNDLE>

• <BUNDLE> Proof bundle file. Required.
• --trusted-kernel-pubkey <HEX> Kernel public key the checkpoints must verify under. Required.

chio spend

Watch spend as it happens: the event stream, burn-rate projections, anomaly findings, and threshold webhooks.

chio spend [OPTIONS] <COMMAND>

• chio spend stream Tail the cursor-ordered spend event stream; a gap in the cursor is reported, never skipped.
• chio spend burn-rate Fetch the signed chio.spend.burn-rate-projection.v1 for a capability: the window’s rate and the integer time to exhaustion.
• chio spend anomalies Read signed anomaly findings.
• chio spend webhook Budget-threshold webhooks, delivered at least once under operator egress policy.

Example

Project when a grant’s budget runs out at the last four hours’ rate.

chio spend burn-rate --capability cap-01a8…31f2 --window 4h

capability  cap-01a8…31f2
window      4h, USD 1.84 per hour
remaining   USD 9.20 of 20.00
exhaustion  in 5h 00m

chio spend stream

Tail the cursor-ordered spend event stream; a gap in the cursor is reported, never skipped.

chio spend stream [OPTIONS]

• --capability <ID> Only events for this capability.
• --cursor <CURSOR> Resume after this cursor.

chio spend burn-rate

Fetch the signed chio.spend.burn-rate-projection.v1 for a capability: the window’s rate and the integer time to exhaustion.

chio spend burn-rate [OPTIONS] --capability <ID> --window <DURATION>

• --capability <ID> Capability to project. Required.
• --window <DURATION> Averaging window, such as 4h. Required.
• --output <FILE> Write the signed projection here.

chio spend anomalies

Read signed anomaly findings.

chio spend anomalies [OPTIONS] <COMMAND>

chio spend anomalies export

Export signed chio.spend.anomaly-finding.v1 records since a time.

chio spend anomalies export [OPTIONS] --since <TIME> --output <FILE>

• --since <TIME> Earliest finding time (RFC 3339 or Unix seconds). Required.
• --output <FILE> Output file. Required.

chio spend webhook

Budget-threshold webhooks, delivered at least once under operator egress policy.

chio spend webhook [OPTIONS] <COMMAND>

• chio spend webhook add Register a webhook for the 50, 80, 95, and 100 percent budget crossings.
• chio spend webhook list List registered webhooks and their last delivery.

chio spend webhook add

Register a webhook for the 50, 80, 95, and 100 percent budget crossings.

chio spend webhook add [OPTIONS] --url <URL> --secret-ref <REF>

• --url <URL> Delivery URL. Required.
• --secret-ref <REF> Reference to the signing secret. Required.
• --capability <ID> Only crossings for this capability.

chio spend webhook list

List registered webhooks and their last delivery.

chio spend webhook list [OPTIONS]

chio oracle

Read price oracles exactly as the kernel does when it converts a budget.

chio oracle [OPTIONS] <COMMAND>

Example

Read USDC/USD with its age, divergence, and margin.

chio oracle read USDC/USD

chainlink   0.9998  age 41s of 600s
pyth        0.9997  divergence 1 bps of 500
sequencer   up
margin      200 bps
health      ok

chio oracle read

Read a pair through the configured oracle: the Chainlink and Pyth readings, age against the staleness limit, divergence, sequencer state, margin, and health.

chio oracle read [OPTIONS] <PAIR>

• <PAIR> Currency pair, such as USDC/USD. Required.

chio run

Spawn an agent subprocess and enforce policy via the kernel.

chio run [OPTIONS] --policy <POLICY> <COMMAND>...

• <COMMAND>... The agent command and its arguments. Required.
• --policy <POLICY> Path to the policy YAML file. Required.

Example

Run from your application directory with an existing policy, replacing your-agent with your executable and its arguments.

chio run --policy policy.yaml -- your-agent

chio check

Evaluate a single tool call against a policy (no subprocess).

chio check [OPTIONS] --policy <POLICY> --tool <TOOL>

• --policy <POLICY> Path to the policy YAML file. Required.
• --mode <MODE> Evaluation mode. Preflight checks only policies that do not need tool output. Default preflight. Values preflight, full.
• --tool <TOOL> Tool name to evaluate. Required.
• --params <PARAMS> Tool parameters as a JSON string. Default {}.
• --server <SERVER> Server ID to use for the evaluation. Default *.
• --output-fixture <JSON> JSON value returned by the fixture-backed tool server in full mode.

$ chio --receipt-db .chio/receipts.db --session-db .chio/session.db check \
  --policy ./policy.yaml --server hello --tool hello_world --params '{"name":"Chio"}'

verdict:    ALLOW
tool:       hello_world
server:     hello
receipt_id: 7fb5b33114af52bd96bf65a7c38e07437bad84580b1f203e11698acc3081374f
policy:     69e943b96e9ce64d0264bb56bf8930e77bd4e68adf68fcf1395790dae03e6b55
source:     0d35135e8b19230b7aa42b0cc5982579450f5dc4a0280822e8b339e7786d2296
mode:       preflight
fixture:    false

chio init

Scaffold a runnable Chio example project with a governed demo flow.

chio init [OPTIONS] <PATH>

• <PATH> Directory to create for the scaffolded project. Required.

Example

Choose a new directory. The scaffold supplies a governed demo that shows a grant, a refusal, and the signed record.

chio init hello-chio

chio policy

Analyze HushSpec policy rules and admission refinement.

chio policy [OPTIONS] <COMMAND>

• chio policy analyze Analyze policy rules and compare admission refinement.
• chio policy test Run a table of cases against a policy and its guards, and fail when any decision differs from the expected one.
• chio policy explain Print what a policy compiles to, or how it decides one call.

Example

Run the case table beside the pricing project’s policy. A changed decision fails the run.

chio policy test

policy   ./policy.yaml
PASS  fixer reads the pricing source   allow
PASS  fixer reads /secrets/.env        deny   outside the grant
PASS  fixer edits a test               deny   rule tests-are-evidence
3 cases: 3 passed

chio policy analyze

Analyze policy rules and compare admission refinement.

chio policy analyze [OPTIONS] <POLICY>

• <POLICY> Effective policy to analyze. Required.
• --against <AGAINST> Older policy that the analyzed policy must narrow.
• --fail-on <FAIL_ON> Lowest finding severity that produces exit code 1. Default warning. Values notice, warning, error.
• --format <FORMAT> Analysis report output format. Values human, json.
• --max-atoms <MAX_ATOMS> Maximum authored atoms accepted before analysis fails closed. Default 10000.

chio policy test

Run a table of cases against a policy and its guards, and fail when any decision differs from the expected one.

chio policy test [OPTIONS] [CASES]...

• [CASES]... Case files. Defaults to policy.test.yaml in the current directory.
• --policy <POLICY> Policy to test instead of the one the case file names.
• --case <TEXT> Run only the cases whose name contains this text. Repeat for several.
• --receipts <DIR> Write each case’s signed receipt to this directory.
• --junit <FILE> Also write the results as JUnit XML for CI.
• --mutate Weaken the policy one rule at a time (drop a pattern, widen a limit, remove a guard) and rerun every case against each weakening. Exit 1 when a weakening changes no case’s decision, naming the rule no case covers.

chio policy explain

Print what a policy compiles to, or how it decides one call.

chio policy explain [OPTIONS] <POLICY>

• <POLICY> Policy file. Required.
• --server <SERVER> Server of the call to explain.
• --tool <TOOL> Tool of the call to explain.
• --params <PARAMS> Parameters of the call, as JSON.
• --output <OUTPUT> Tool output to run the output guards against, as JSON.

chio api

Protect an HTTP API with Chio using an OpenAPI spec-backed sidecar.

chio api [OPTIONS] <COMMAND>

chio api protect

Start the Chio HTTP sidecar/reverse proxy.

chio api protect [OPTIONS] --upstream <UPSTREAM>

• --upstream <UPSTREAM> Upstream base URL to proxy to. Required.
• --spec <SPEC> Optional local OpenAPI spec path. Auto-discovered when omitted.
• --listen <LISTEN> Address to listen on. Default 127.0.0.1:9090.
• --receipt-store <RECEIPT_STORE> Optional SQLite receipt store path.
• --allow-ephemeral-receipts Permit in-memory receipts, whose audit evidence is lost on every restart. Required to boot without --receipt-store. For local development only.
• --upstream-timeout-secs <UPSTREAM_TIMEOUT_SECS> Wall-clock ceiling in seconds on a single upstream hop, including reading the full response. Raise it for upstreams with legitimately slow calls or large bounded responses. Defaults to 20 seconds.
• --trust <FILE> Trust file whose issuer pins admit presented capabilities. Defaults to ~/.chio/trust.toml. Reads CHIO_TRUST.
• --computer <COMPUTER> Attach to a Computer’s kernel state: verify the grants its kernel issued, read the policy in force, consult its revocations and budgets, and append receipts to its history. Replaces the individual store options.
• --service <SERVICE> Service name the protected operations are registered under on the Computer; receipts and grants name it.

chio mcp

Serve an MCP-compatible edge backed by the Chio kernel.

chio mcp [OPTIONS] <COMMAND>

• chio mcp wrap Wrap a stdio MCP server with verdict gating and emit IDE configs.
• chio mcp governed-sim Run a single governed MustPrepay call through an ephemeral kernel.
• chio mcp serve Wrap an MCP server subprocess and expose a secured MCP edge over stdio.
• chio mcp serve-http Wrap an MCP server subprocess and expose a secured MCP edge over Streamable HTTP.

chio mcp wrap

Wrap a stdio MCP server with verdict gating and emit IDE configs.

chio mcp wrap [OPTIONS] [COMMAND]...

• [COMMAND]... The wrapped MCP server command and its arguments. Required unless --tools-fixture is supplied (the test-only path).
• --server-id <SERVER_ID> Server ID to assign to the wrapped MCP server inside the inferred manifest scaffold. Default mcp.
• --manifest <MANIFEST> Optional path to the user’s manifest scaffold. When absent the command renders the inferred scaffold to stdout instead of running the wrap loop.
• --print-scopes Print the inferred capability-scope manifest scaffold and exit.
• --emit-config <EMIT_CONFIG> IDE target for --emit-config. When set, the command prints the paste-ready config for the requested IDE and exits without spawning the wrapped child. Values cursor, claude-desktop, continue, zed.
• --display-name <DISPLAY_NAME> Display name surfaced inside emitted IDE config blobs.
• --tools-fixture <TOOLS_FIXTURE> Render the manifest scaffold from a JSON tools/list fixture file instead of spawning the wrapped child. Used by the scope inference and emit-config tests so they stay hermetic on shared CI runners.
• --e2e-fixture <E2E_FIXTURE> Drive the wrap loop against an in-process JSON-RPC fixture (a JSON object with tools and responses arrays). Reads JSON-RPC frames from stdin and emits framed responses on stdout, gated by the manifest scaffold. Used by the e2e test so the stdio-orchestration round-trip can run without a real wrapped child.
• --self-test-attestation <SELF_TEST_ATTESTATION> Self-test mode for the attestation header. Prints the "Chio-verified" attestation block for the given tool name as JSON and exits.
• --strict-execution-nonce Execute allowed tool calls through a kernel path that mints and presents strict execution nonces before invoking the wrapped server.

chio mcp governed-sim

Run a single governed MustPrepay call through an ephemeral kernel.

chio mcp governed-sim [OPTIONS] --out <OUT>

• --payment-adapter <PAYMENT_ADAPTER> Payment adapter: sim (deterministic no-broadcast) or none (absent, deny path). Default sim.
• --governed-mustprepay Run a governed MustPrepay tool call through the kernel.
• --out <OUT> Path to write the receipt bundle JSON. Required.

chio mcp serve

Wrap an MCP server subprocess and expose a secured MCP edge over stdio.

chio mcp serve [OPTIONS] <COMMAND>...

• <COMMAND>... The wrapped MCP server command and its arguments. Required.
• --policy <POLICY> Path to the policy YAML file. Mutually exclusive with --preset.
• --preset <PRESET> Bundled policy preset to use instead of --policy. Available presets: * code-agent -- zero-config policy for coding agents (Claude Code, Cursor, MCP filesystem/git/shell servers). Allows safe file reads, denies .env / .git/** / .ssh/** writes, denies git push --force.
• --server-id <SERVER_ID> Server ID to assign to the wrapped MCP server inside Chio. Default mcp.
• --server-name <SERVER_NAME> Human-readable name for the wrapped MCP server.
• --server-version <SERVER_VERSION> Version string for the wrapped MCP server.
• --manifest-public-key <MANIFEST_PUBLIC_KEY> Override the public key embedded in the synthetic manifest.
• --page-size <PAGE_SIZE> Page size for paginated tools/list responses. Default 50.
• --tools-list-changed Whether the edge should advertise notifications/tools/list_changed.
• --signed-manifest <PATH> Publisher-signed manifest of the wrapped server, verified against --manifest-public-key.
• --cage-policy <PATH> Canonical signed native-launch policy for the wrapped server.
• --cage-policy-signer <PUBLIC_KEY> Independently pinned public key for the native-launch policy signer.

chio mcp serve-http

Wrap an MCP server subprocess and expose a secured MCP edge over Streamable HTTP.

chio mcp serve-http [OPTIONS] --policy <POLICY> --server-id <SERVER_ID> <COMMAND>...

• <COMMAND>... The wrapped MCP server command and its arguments. Required.
• --policy <POLICY> Path to the policy YAML file. Required.
• --server-id <SERVER_ID> Server ID to assign to the wrapped MCP server inside Chio. Required.
• --server-name <SERVER_NAME> Human-readable name for the wrapped MCP server.
• --server-version <SERVER_VERSION> Version string for the wrapped MCP server.
• --manifest-public-key <MANIFEST_PUBLIC_KEY> Override the public key embedded in the synthetic manifest.
• --page-size <PAGE_SIZE> Page size for paginated tools/list responses. Default 50.
• --tools-list-changed Whether the edge should advertise notifications/tools/list_changed.
• --shared-hosted-owner Use one shared wrapped MCP subprocess for all remote sessions.
• --listen <LISTEN> Socket address to bind the remote MCP edge to. Default 127.0.0.1:8931.
• --auth-token <AUTH_TOKEN> Static bearer token required for remote MCP session admission. Prefer CHIO_AUTH_TOKEN env over the argv form so the bearer does not leak via ps / /proc/<pid>/cmdline. Reads CHIO_AUTH_TOKEN.
• --auth-jwt-public-key <AUTH_JWT_PUBLIC_KEY> Public key used to verify externally issued JWT bearer tokens.
• --auth-jwt-discovery-url <AUTH_JWT_DISCOVERY_URL> OIDC discovery URL used to resolve issuer metadata and JWT JWKS keys.
• --auth-introspection-url <AUTH_INTROSPECTION_URL> OAuth2 token introspection endpoint used to validate opaque bearer tokens.
• --auth-introspection-client-id <AUTH_INTROSPECTION_CLIENT_ID> Client ID used when calling the token introspection endpoint.
• --auth-introspection-client-secret <AUTH_INTROSPECTION_CLIENT_SECRET> Client secret used when calling the token introspection endpoint. Prefer CHIO_MCP_AUTH_INTROSPECTION_CLIENT_SECRET env over the argv form so the secret does not leak via ps / /proc/<pid>/cmdline. Reads CHIO_MCP_AUTH_INTROSPECTION_CLIENT_SECRET.
• --auth-jwt-provider-profile <AUTH_JWT_PROVIDER_PROFILE> Optional provider profile used for principal mapping and default OIDC discovery behavior. Values generic, auth0, okta, azure-ad.
• --auth-server-seed-file <AUTH_SERVER_SEED_FILE> Local auth-server signing seed file. When set, serve-http can issue JWTs itself.
• --identity-federation-seed-file <IDENTITY_FEDERATION_SEED_FILE> Persistent seed file used to derive stable Chio subjects from authenticated OAuth bearer principals.
• --enterprise-providers-file <ENTERPRISE_PROVIDERS_FILE> Optional file-backed enterprise provider registry shared with trust-control.
• --auth-jwt-issuer <AUTH_JWT_ISSUER> Expected bearer-token issuer for remote MCP session admission.
• --auth-jwt-audience <AUTH_JWT_AUDIENCE> Expected bearer-token audience for remote MCP session admission.
• --admin-token <ADMIN_TOKEN> Optional static bearer token for remote admin APIs. Prefer CHIO_ADMIN_TOKEN env over the argv form so the bearer does not leak via ps / /proc/<pid>/cmdline. Reads CHIO_ADMIN_TOKEN.
• --public-base-url <PUBLIC_BASE_URL> Public base URL used when constructing protected-resource metadata URLs.
• --auth-server <AUTH_SERVERS> Authorization server URL advertised via protected-resource metadata.
• --auth-authorization-endpoint <AUTH_AUTHORIZATION_ENDPOINT> OAuth authorization endpoint advertised in colocated auth-server metadata.
• --auth-token-endpoint <AUTH_TOKEN_ENDPOINT> OAuth token endpoint advertised in colocated auth-server metadata.
• --auth-registration-endpoint <AUTH_REGISTRATION_ENDPOINT> Optional dynamic client registration endpoint advertised in auth-server metadata.
• --auth-jwks-uri <AUTH_JWKS_URI> Optional JWKS URI advertised in auth-server metadata.
• --auth-scope <AUTH_SCOPES> Scope hint advertised in protected-resource challenges and metadata.
• --auth-subject <AUTH_SUBJECT> Subject to embed in locally issued auth-server access tokens. Default operator.
• --auth-code-ttl-secs <AUTH_CODE_TTL_SECS> Authorization-code lifetime for the hosted auth server. Default 300.
• --auth-access-token-ttl-secs <AUTH_ACCESS_TOKEN_TTL_SECS> Access-token lifetime for the hosted auth server. Default 600.
• --trust <FILE> Trust file whose issuer pins admit presented capabilities. Defaults to ~/.chio/trust.toml. Reads CHIO_TRUST.
• --computer <COMPUTER> Attach to a Computer’s kernel state: verify the grants its kernel issued, read the policy in force, consult its revocations and budgets, and append receipts to its history. Replaces the individual store options.

chio trust

Manage local trust-plane state such as persisted revocations.

chio trust [OPTIONS] <COMMAND>

• chio trust serve Serve the shared trust-control plane over HTTP.
• chio trust provider Manage enterprise federation provider-admin records.
• chio trust federation-policy Manage permissionless federation admission policies.
• chio trust evidence-share Inspect shared remote evidence references used by local delegated activity.
• chio trust authorization-context Render derived external authorization context from governed receipts.
• chio trust appraisal Export a signed runtime-attestation appraisal report.
• chio trust behavioral-feed Export a signed insurer-facing behavioral feed from canonical trust data.
• chio trust exposure-ledger Export a signed exposure ledger from canonical trust and underwriting data.
• chio trust credit-scorecard Export a signed subject-scoped credit scorecard from exposure and reputation data.
• chio trust capital-book Export a signed live capital book with explicit source-of-funds attribution.
• chio trust capital-instruction Issue one custody-neutral escrow or reserve instruction artifact.
• chio trust capital-allocation Issue one simulation-first capital-allocation decision for a governed action.
• chio trust facility Evaluate, issue, and list bounded credit facilities from subject-scoped evidence.
• chio trust bond Evaluate, issue, and list reserve-lock bond artifacts from credit evidence.
• chio trust loss Evaluate, issue, and list immutable bond loss-lifecycle artifacts.
• chio trust credit-backtest Export deterministic credit backtests over historical subject-scoped evidence.
• chio trust provider-risk-package Export one signed provider-facing risk package over canonical credit truth.
• chio trust liability-provider Issue, list, and resolve curated liability-market provider registry entries.
• chio trust liability-market Issue quote, placement, and bound-coverage artifacts and list workflow state.
• chio trust underwriting-input Export a signed underwriting policy-input snapshot from canonical trust data.
• chio trust underwriting-decision Evaluate a bounded underwriting decision from canonical trust data.
• chio trust underwriting-appeal Create or resolve underwriting appeals against persisted decisions.
• chio trust trace-verify Check a signed observation log against a bounded transition model.
• chio trust revoke Persist a capability revocation into the configured revocation database.
• chio trust federated-issue Issue one local capability after verifying a challenge-bound portable presentation.
• chio trust federated-delegation-policy-create Create a signed federated delegation policy from a single default capability.
• chio trust status Query whether a capability ID is currently revoked.
• chio trust pin Pin a key for one verification role in the trust file.
• chio trust pins List the pins in the trust file: name, role, key fingerprint, and where each came from.
• chio trust unpin Remove a pin from the trust file, for every role or for one.
• chio trust roles List every verification role, the artifacts it signs, and the commands that read it.

chio trust serve

Serve the shared trust-control plane over HTTP.

chio trust serve [OPTIONS] --service-token <SERVICE_TOKEN>

• --listen <LISTEN> Socket address to bind the trust-control service to. Default 127.0.0.1:8940.
• --service-token <SERVICE_TOKEN> Bearer token required for trust-control service requests. Prefer CHIO_TRUST_SERVICE_TOKEN over --service-token so the secret is not visible to other users via ps//proc. Required. Reads CHIO_TRUST_SERVICE_TOKEN.
• --tenant-read-token <TENANT=TOKEN> Tenant-scoped read token mapping in tenant_id=token form. Repeat for multiple tenants. Requests presenting one of these tokens are confined to reading the matching tenant’s receipts; the --service-token retains administrative cross-tenant access.
• --advertise-url <ADVERTISE_URL> Public base URL this trust-control node advertises to peers and clients.
• --peer-url <PEER_URLS> Peer trust-control base URL. Repeat for multiple peers.
• --allow-local-peer-urls Allow loopback/private cluster peer URLs for local development only.
• --cluster-sync-interval-ms <CLUSTER_SYNC_INTERVAL_MS> Background cluster sync interval in milliseconds. Default 500.
• --policy <POLICY> Optional policy file whose reputation issuance extension is enforced by the service.
• --enterprise-providers-file <ENTERPRISE_PROVIDERS_FILE> Optional file-backed enterprise provider registry shared with remote MCP edges.
• --federation-policies-file <FEDERATION_POLICIES_FILE> Optional file-backed permissionless federation policy registry.
• --scim-lifecycle-file <SCIM_LIFECYCLE_FILE> Optional file-backed SCIM lifecycle registry for external IdP provisioning and deprovisioning.
• --verifier-policies-file <VERIFIER_POLICIES_FILE> Optional file-backed signed verifier policy registry for remote verifier flows.
• --verifier-challenge-db <VERIFIER_CHALLENGE_DB> Optional SQLite verifier challenge-state database for replay-safe remote verifier flows.
• --passport-statuses-file <PASSPORT_STATUSES_FILE> Optional file-backed passport lifecycle registry for publish/resolve/revoke flows.
• --passport-issuance-offers-file <PASSPORT_ISSUANCE_OFFERS_FILE> Optional file-backed passport issuance registry for OID4VCI-style pre-authorized offers.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional file-backed certification registry for publish/resolve/revoke flows.
• --certification-discovery-file <CERTIFICATION_DISCOVERY_FILE> Optional multi-operator certification discovery network file.
• --fiscal-genesis-policy <FISCAL_GENESIS_POLICY> Pinned fiscal genesis policy JSON loaded before the service binds.
• --fiscal-anchor-url <FISCAL_ANCHOR_URL> Independent HTTPS fiscal continuity anchor base URL.
• --fiscal-anchor-token <FISCAL_ANCHOR_TOKEN> Bearer token for the independent fiscal continuity anchor. Reads CHIO_FISCAL_ANCHOR_TOKEN.
• --fiscal-admission-authority-id <FISCAL_ADMISSION_AUTHORITY_ID> Stable identifier for the local durable fiscal admission authority. Default fiscal-admission.
• --fiscal-admission-signer-key-epoch <FISCAL_ADMISSION_SIGNER_KEY_EPOCH> Monotonic key epoch for the fiscal admission signing key. Default 1.
• --fiscal-admission-signing-seed <FISCAL_ADMISSION_SIGNING_SEED> Existing private seed file used to sign durable fiscal admissions.
• --fiscal-anchor-timeout-seconds <FISCAL_ANCHOR_TIMEOUT_SECONDS> Fiscal continuity anchor request timeout in seconds. Default 5.
• --certification-public-metadata-ttl-seconds <CERTIFICATION_PUBLIC_METADATA_TTL_SECONDS> Public certification metadata TTL in seconds. Default 3600.
• --roster-policy-file <ROSTER_POLICY_FILE> JSON file containing the operator roster policy (roster, allowed decision rules, roster anchor) for liability adjudication enforcement.
• --trust <FILE> Trust file whose issuer and receipt-kernel pins the service accepts. Defaults to ~/.chio/trust.toml. Reads CHIO_TRUST.

chio trust provider

Manage enterprise federation provider-admin records.

chio trust provider [OPTIONS] <COMMAND>

• chio trust provider list List enterprise provider records from the shared registry.
• chio trust provider get Read one enterprise provider record.
• chio trust provider upsert Create or update one enterprise provider record from JSON.
• chio trust provider delete Delete one enterprise provider record.

chio trust provider list

List enterprise provider records from the shared registry.

chio trust provider list [OPTIONS]

• --enterprise-providers-file <ENTERPRISE_PROVIDERS_FILE> Local registry file to inspect when not using --control-url.

chio trust provider get

Read one enterprise provider record.

chio trust provider get [OPTIONS] --provider-id <PROVIDER_ID>

• --provider-id <PROVIDER_ID> Provider ID to fetch. Required.
• --enterprise-providers-file <ENTERPRISE_PROVIDERS_FILE> Local registry file to inspect when not using --control-url.

chio trust provider upsert

Create or update one enterprise provider record from JSON.

chio trust provider upsert [OPTIONS] --input <INPUT>

• --input <INPUT> Input JSON file containing an EnterpriseProviderRecord. Required.
• --enterprise-providers-file <ENTERPRISE_PROVIDERS_FILE> Local registry file to update when not using --control-url.

chio trust provider delete

Delete one enterprise provider record.

chio trust provider delete [OPTIONS] --provider-id <PROVIDER_ID>

• --provider-id <PROVIDER_ID> Provider ID to delete. Required.
• --enterprise-providers-file <ENTERPRISE_PROVIDERS_FILE> Local registry file to update when not using --control-url.

chio trust federation-policy

Manage permissionless federation admission policies.

chio trust federation-policy [OPTIONS] <COMMAND>

• chio trust federation-policy list List published permissionless federation policies.
• chio trust federation-policy get Read one published permissionless federation policy.
• chio trust federation-policy upsert Create or update one permissionless federation policy record from JSON.
• chio trust federation-policy delete Delete one permissionless federation policy record.
• chio trust federation-policy evaluate Evaluate admission for one peer under a published federation policy.

chio trust federation-policy list

List published permissionless federation policies.

chio trust federation-policy list [OPTIONS]

• --federation-policies-file <FEDERATION_POLICIES_FILE> Local registry file to inspect when not using --control-url.

chio trust federation-policy get

Read one published permissionless federation policy.

chio trust federation-policy get [OPTIONS] --policy-id <POLICY_ID>

• --policy-id <POLICY_ID> Policy ID to fetch. Required.
• --federation-policies-file <FEDERATION_POLICIES_FILE> Local registry file to inspect when not using --control-url.

chio trust federation-policy upsert

Create or update one permissionless federation policy record from JSON.

chio trust federation-policy upsert [OPTIONS] --input <INPUT>

• --input <INPUT> Input JSON file containing a FederationAdmissionPolicyRecord. Required.
• --federation-policies-file <FEDERATION_POLICIES_FILE> Local registry file to update when not using --control-url.

chio trust federation-policy delete

Delete one permissionless federation policy record.

chio trust federation-policy delete [OPTIONS] --policy-id <POLICY_ID>

• --policy-id <POLICY_ID> Policy ID to delete. Required.
• --federation-policies-file <FEDERATION_POLICIES_FILE> Local registry file to update when not using --control-url.

chio trust federation-policy evaluate

Evaluate admission for one peer under a published federation policy.

chio trust federation-policy evaluate [OPTIONS] --input <INPUT>

• --input <INPUT> Input JSON file containing a FederationAdmissionEvaluationRequest. Required.

chio trust evidence-share

Inspect shared remote evidence references used by local delegated activity.

chio trust evidence-share [OPTIONS] <COMMAND>

chio trust evidence-share list

List shared-evidence references visible from local activity or the remote trust service.

chio trust evidence-share list [OPTIONS]

• --capability <CAPABILITY> Filter by local capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by local agent subject public key.
• --tool-server <TOOL_SERVER> Filter by local tool server.
• --tool-name <TOOL_NAME> Filter by local tool name.
• --since <SINCE> Filter: receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Filter: receipts with timestamp <= this Unix seconds value.
• --issuer <ISSUER> Filter by remote share issuer.
• --partner <PARTNER> Filter by remote share partner.
• --limit <LIMIT> Maximum number of shared-evidence references to return. Default 50.

chio trust authorization-context

Render derived external authorization context from governed receipts.

chio trust authorization-context [OPTIONS] <COMMAND>

• chio trust authorization-context metadata Export machine-readable Chio authorization-profile metadata for enterprise IAM review.
• chio trust authorization-context list List derived authorization-context mappings from local state or trust-control.
• chio trust authorization-context review-pack Export an enterprise reviewer pack tying authorization context back to governed receipt truth.

chio trust authorization-context metadata

Export machine-readable Chio authorization-profile metadata for enterprise IAM review.

chio trust authorization-context metadata [OPTIONS]

chio trust authorization-context list

List derived authorization-context mappings from local state or trust-control.

chio trust authorization-context list [OPTIONS]

• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --limit <LIMIT> Maximum number of derived authorization-context rows to embed. Default 50.

chio trust authorization-context review-pack

Export an enterprise reviewer pack tying authorization context back to governed receipt truth.

chio trust authorization-context review-pack [OPTIONS]

• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --limit <LIMIT> Maximum number of derived authorization-context rows to embed. Default 50.

chio trust appraisal

Export a signed runtime-attestation appraisal report.

chio trust appraisal [OPTIONS] <COMMAND>

• chio trust appraisal export Export a signed runtime-attestation appraisal report from local input or trust-control.
• chio trust appraisal export-result Export a signed portable runtime-attestation appraisal result artifact.
• chio trust appraisal import Evaluate a signed external runtime-attestation appraisal result against local import policy.

chio trust appraisal export

Export a signed runtime-attestation appraisal report from local input or trust-control.

chio trust appraisal export [OPTIONS] --input <INPUT>

• --input <INPUT> Input JSON or YAML file containing a RuntimeAttestationEvidence payload. Required.
• --policy-file <POLICY_FILE> Optional HushSpec policy used to evaluate policy-visible outcomes locally.

chio trust appraisal export-result

Export a signed portable runtime-attestation appraisal result artifact.

chio trust appraisal export-result [OPTIONS] --issuer <ISSUER> --input <INPUT>

• --issuer <ISSUER> Issuer identifier recorded in the exported result. Required.
• --input <INPUT> Input JSON or YAML file containing a RuntimeAttestationEvidence payload. Required.
• --policy-file <POLICY_FILE> Optional HushSpec policy used to evaluate exporter-visible outcomes locally.

chio trust appraisal import

Evaluate a signed external runtime-attestation appraisal result against local import policy.

chio trust appraisal import [OPTIONS] --input <INPUT> --policy-file <POLICY_FILE>

• --input <INPUT> Input JSON or YAML file containing a signed appraisal result envelope. Required.
• --policy-file <POLICY_FILE> JSON or YAML file containing a RuntimeAttestationImportedAppraisalPolicy payload. Required.

chio trust behavioral-feed

Export a signed insurer-facing behavioral feed from canonical trust data.

chio trust behavioral-feed [OPTIONS] <COMMAND>

chio trust behavioral-feed export

Export a signed behavioral feed from local state or trust-control.

chio trust behavioral-feed export [OPTIONS]

• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt detail rows to embed. Default 100.

chio trust exposure-ledger

Export a signed exposure ledger from canonical trust and underwriting data.

chio trust exposure-ledger [OPTIONS] <COMMAND>

chio trust exposure-ledger export

Export a signed exposure ledger from local state or trust-control.

chio trust exposure-ledger export [OPTIONS]

• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to embed. Default 100.
• --decision-limit <DECISION_LIMIT> Maximum number of underwriting decision rows to embed. Default 50.

chio trust credit-scorecard

Export a signed subject-scoped credit scorecard from exposure and reputation data.

chio trust credit-scorecard [OPTIONS] <COMMAND>

chio trust credit-scorecard export

Export a signed credit scorecard from local state or trust-control.

chio trust credit-scorecard export [OPTIONS]

• --agent-subject <AGENT_SUBJECT> Subject public key to score.
• --capability <CAPABILITY> Optional filter by capability ID.
• --tool-server <TOOL_SERVER> Optional filter by tool server.
• --tool-name <TOOL_NAME> Optional filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to evaluate. Default 100.
• --decision-limit <DECISION_LIMIT> Maximum number of underwriting decision rows to evaluate. Default 50.
• --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 trust capital-book

Export a signed live capital book with explicit source-of-funds attribution.

chio trust capital-book [OPTIONS] <COMMAND>

chio trust capital-book export

Export a signed live capital book from canonical facility, bond, and loss posture.

chio trust capital-book export [OPTIONS] --agent-subject <AGENT_SUBJECT>

• --agent-subject <AGENT_SUBJECT> Subject public key to evaluate. Required.
• --capability <CAPABILITY> Optional filter by capability ID.
• --tool-server <TOOL_SERVER> Optional filter by tool server.
• --tool-name <TOOL_NAME> Optional filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to inspect for disbursement provenance. Default 100.
• --facility-limit <FACILITY_LIMIT> Maximum number of facility rows to inspect. Default 10.
• --bond-limit <BOND_LIMIT> Maximum number of bond rows to inspect. Default 10.
• --loss-event-limit <LOSS_EVENT_LIMIT> Maximum number of loss-lifecycle rows to inspect. Default 25.

chio trust capital-instruction

Issue one custody-neutral escrow or reserve instruction artifact.

chio trust capital-instruction [OPTIONS] <COMMAND>

chio trust capital-instruction issue

Issue one custody-neutral escrow or reserve instruction artifact from JSON or YAML input.

chio trust capital-instruction issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML capital-instruction input file. Required.

chio trust capital-allocation

Issue one simulation-first capital-allocation decision for a governed action.

chio trust capital-allocation [OPTIONS] <COMMAND>

chio trust capital-allocation issue

Issue one live capital-allocation decision artifact from JSON or YAML input.

chio trust capital-allocation issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML capital-allocation input file. Required.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust facility

Evaluate, issue, and list bounded credit facilities from subject-scoped evidence.

chio trust facility [OPTIONS] <COMMAND>

• chio trust facility evaluate Evaluate a deterministic facility-policy report without persisting an artifact.
• chio trust facility issue Issue and persist a signed facility artifact from deterministic facility policy.
• chio trust facility list List persisted credit facility artifacts.

chio trust facility evaluate

Evaluate a deterministic facility-policy report without persisting an artifact.

chio trust facility evaluate [OPTIONS] --agent-subject <AGENT_SUBJECT>

• --agent-subject <AGENT_SUBJECT> Subject public key to evaluate. Required.
• --capability <CAPABILITY> Optional filter by capability ID.
• --tool-server <TOOL_SERVER> Optional filter by tool server.
• --tool-name <TOOL_NAME> Optional filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to evaluate. Default 100.
• --decision-limit <DECISION_LIMIT> Maximum number of underwriting decision rows to evaluate. Default 50.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust facility issue

Issue and persist a signed facility artifact from deterministic facility policy.

chio trust facility issue [OPTIONS] --agent-subject <AGENT_SUBJECT>

• --agent-subject <AGENT_SUBJECT> Subject public key to evaluate. Required.
• --capability <CAPABILITY> Optional filter by capability ID.
• --tool-server <TOOL_SERVER> Optional filter by tool server.
• --tool-name <TOOL_NAME> Optional filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to evaluate. Default 100.
• --decision-limit <DECISION_LIMIT> Maximum number of underwriting decision rows to evaluate. Default 50.
• --supersedes-facility-id <SUPERSEDES_FACILITY_ID> Optional previously active facility to supersede.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust facility list

List persisted credit facility artifacts.

chio trust facility list [OPTIONS]

• --facility-id <FACILITY_ID> Filter by facility ID.
• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --disposition <DISPOSITION> Filter by disposition (grant, manual_review, deny).
• --lifecycle-state <LIFECYCLE_STATE> Filter by lifecycle state (active, superseded, denied, expired).
• --limit <LIMIT> Maximum number of facility rows to embed. Default 50.

chio trust bond

Evaluate, issue, and list reserve-lock bond artifacts from credit evidence.

chio trust bond [OPTIONS] <COMMAND>

• chio trust bond evaluate Evaluate a deterministic bond-policy report without persisting an artifact.
• chio trust bond issue Issue and persist a signed bond artifact from deterministic bond policy.
• chio trust bond simulate Simulate bonded execution under an operator control policy without mutating state.
• chio trust bond list List persisted credit bond artifacts.

chio trust bond evaluate

Evaluate a deterministic bond-policy report without persisting an artifact.

chio trust bond evaluate [OPTIONS] --agent-subject <AGENT_SUBJECT>

• --agent-subject <AGENT_SUBJECT> Subject public key to evaluate. Required.
• --capability <CAPABILITY> Optional filter by capability ID.
• --tool-server <TOOL_SERVER> Optional filter by tool server.
• --tool-name <TOOL_NAME> Optional filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to evaluate. Default 100.
• --decision-limit <DECISION_LIMIT> Maximum number of underwriting decision rows to evaluate. Default 50.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust bond issue

Issue and persist a signed bond artifact from deterministic bond policy.

chio trust bond issue [OPTIONS] --agent-subject <AGENT_SUBJECT>

• --agent-subject <AGENT_SUBJECT> Subject public key to evaluate. Required.
• --capability <CAPABILITY> Optional filter by capability ID.
• --tool-server <TOOL_SERVER> Optional filter by tool server.
• --tool-name <TOOL_NAME> Optional filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to evaluate. Default 100.
• --decision-limit <DECISION_LIMIT> Maximum number of underwriting decision rows to evaluate. Default 50.
• --supersedes-bond-id <SUPERSEDES_BOND_ID> Optional previously active bond to supersede.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust bond simulate

Simulate bonded execution under an operator control policy without mutating state.

chio trust bond simulate [OPTIONS] --bond-id <BOND_ID> --autonomy-tier <AUTONOMY_TIER> --runtime-assurance-tier <RUNTIME_ASSURANCE_TIER> --policy-file <POLICY_FILE>

• --bond-id <BOND_ID> Bond artifact ID to evaluate. Required.
• --autonomy-tier <AUTONOMY_TIER> Requested autonomy tier (direct, delegated, autonomous). Required.
• --runtime-assurance-tier <RUNTIME_ASSURANCE_TIER> Runtime assurance tier attached to the simulated request. Required.
• --call-chain-present Whether delegated call-chain context is present.
• --policy-file <POLICY_FILE> YAML or JSON operator control policy file. Required.

chio trust bond list

List persisted credit bond artifacts.

chio trust bond list [OPTIONS]

• --bond-id <BOND_ID> Filter by bond ID.
• --facility-id <FACILITY_ID> Filter by facility ID.
• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --disposition <DISPOSITION> Filter by disposition (lock, hold, release, impair).
• --lifecycle-state <LIFECYCLE_STATE> Filter by lifecycle state (active, superseded, released, impaired, expired).
• --limit <LIMIT> Maximum number of bond rows to embed. Default 50.

chio trust loss

Evaluate, issue, and list immutable bond loss-lifecycle artifacts.

chio trust loss [OPTIONS] <COMMAND>

• chio trust loss evaluate Evaluate a deterministic bond loss-lifecycle transition without persisting an artifact.
• chio trust loss issue Issue and persist a signed bond loss-lifecycle artifact.
• chio trust loss list List persisted bond loss-lifecycle artifacts.

chio trust loss evaluate

Evaluate a deterministic bond loss-lifecycle transition without persisting an artifact.

chio trust loss evaluate [OPTIONS] --bond-id <BOND_ID> --event-kind <EVENT_KIND>

• --bond-id <BOND_ID> Bond ID to evaluate against. Required.
• --event-kind <EVENT_KIND> Event kind (delinquency, recovery, reserve_release, reserve_slash, write_off). Required.
• --amount-units <AMOUNT_UNITS> Optional explicit amount in minor units.
• --amount-currency <AMOUNT_CURRENCY> Optional explicit amount currency.

chio trust loss issue

Issue and persist a signed bond loss-lifecycle artifact.

chio trust loss issue [OPTIONS] --bond-id <BOND_ID> --event-kind <EVENT_KIND>

• --bond-id <BOND_ID> Bond ID to evaluate against. Required.
• --event-kind <EVENT_KIND> Event kind (delinquency, recovery, reserve_release, reserve_slash, write_off). Required.
• --amount-units <AMOUNT_UNITS> Optional explicit amount in minor units.
• --amount-currency <AMOUNT_CURRENCY> Optional explicit amount currency.
• --authority-chain-file <AUTHORITY_CHAIN_FILE> Optional JSON/YAML file containing Vec<CapitalExecutionAuthorityStep>.
• --execution-window-file <EXECUTION_WINDOW_FILE> Optional JSON/YAML file containing CapitalExecutionWindow.
• --rail-file <RAIL_FILE> Optional JSON/YAML file containing CapitalExecutionRail.
• --observed-execution-file <OBSERVED_EXECUTION_FILE> Optional JSON/YAML file containing CapitalExecutionObservation.
• --appeal-window-ends-at <APPEAL_WINDOW_ENDS_AT> Optional reserve-control appeal window close timestamp.
• --description <DESCRIPTION> Optional reserve-control description recorded on the lifecycle artifact.

chio trust loss list

List persisted bond loss-lifecycle artifacts.

chio trust loss list [OPTIONS]

• --event-id <EVENT_ID> Filter by event ID.
• --bond-id <BOND_ID> Filter by bond ID.
• --facility-id <FACILITY_ID> Filter by facility ID.
• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --event-kind <EVENT_KIND> Filter by event kind (delinquency, recovery, reserve_release, reserve_slash, write_off).
• --limit <LIMIT> Maximum number of event rows to embed. Default 50.

chio trust credit-backtest

Export deterministic credit backtests over historical subject-scoped evidence.

chio trust credit-backtest [OPTIONS] <COMMAND>

chio trust credit-backtest export

Export one deterministic credit backtest report over historical evidence windows.

chio trust credit-backtest export [OPTIONS] --agent-subject <AGENT_SUBJECT>

• --agent-subject <AGENT_SUBJECT> Subject public key to evaluate. Required.
• --capability <CAPABILITY> Optional filter by capability ID.
• --tool-server <TOOL_SERVER> Optional filter by tool server.
• --tool-name <TOOL_NAME> Optional filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to evaluate per window. Default 100.
• --decision-limit <DECISION_LIMIT> Maximum number of underwriting decision rows to evaluate per window. Default 50.
• --window-seconds <WINDOW_SECONDS> Width of each replay window in seconds. Default 604800.
• --window-count <WINDOW_COUNT> Number of windows to replay. Default 4.
• --stale-after-seconds <STALE_AFTER_SECONDS> Evidence older than this threshold is flagged stale. Default 2592000.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust provider-risk-package

Export one signed provider-facing risk package over canonical credit truth.

chio trust provider-risk-package [OPTIONS] <COMMAND>

chio trust provider-risk-package export

Export one signed provider-facing risk package over canonical subject-scoped evidence.

chio trust provider-risk-package export [OPTIONS] --agent-subject <AGENT_SUBJECT>

• --agent-subject <AGENT_SUBJECT> Subject public key to evaluate. Required.
• --capability <CAPABILITY> Optional filter by capability ID.
• --tool-server <TOOL_SERVER> Optional filter by tool server.
• --tool-name <TOOL_NAME> Optional filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt rows to evaluate. Default 100.
• --decision-limit <DECISION_LIMIT> Maximum number of underwriting decision rows to evaluate. Default 50.
• --recent-loss-limit <RECENT_LOSS_LIMIT> Maximum number of recent loss events to include. Default 10.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust liability-provider

Issue, list, and resolve curated liability-market provider registry entries.

chio trust liability-provider [OPTIONS] <COMMAND>

• chio trust liability-provider issue Issue and persist a signed curated liability-provider artifact from JSON or YAML input.
• chio trust liability-provider list List persisted liability-provider artifacts.
• chio trust liability-provider resolve Resolve one provider + jurisdiction + coverage + currency combination fail closed.

chio trust liability-provider issue

Issue and persist a signed curated liability-provider artifact from JSON or YAML input.

chio trust liability-provider issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML provider report input file. Required.
• --supersedes-provider-record-id <SUPERSEDES_PROVIDER_RECORD_ID> Optional previously active provider record to supersede.

chio trust liability-provider list

List persisted liability-provider artifacts.

chio trust liability-provider list [OPTIONS]

• --provider-id <PROVIDER_ID> Filter by provider ID.
• --jurisdiction <JURISDICTION> Filter by jurisdiction.
• --coverage-class <COVERAGE_CLASS> Filter by coverage class (tool_execution, data_breach, financial_loss, professional_liability, regulatory_response).
• --currency <CURRENCY> Filter by currency.
• --lifecycle-state <LIFECYCLE_STATE> Filter by lifecycle state (active, suspended, superseded, retired).
• --limit <LIMIT> Maximum number of provider rows to embed. Default 50.

chio trust liability-provider resolve

Resolve one provider + jurisdiction + coverage + currency combination fail closed.

chio trust liability-provider resolve [OPTIONS] --provider-id <PROVIDER_ID> --jurisdiction <JURISDICTION> --coverage-class <COVERAGE_CLASS> --currency <CURRENCY>

• --provider-id <PROVIDER_ID> Provider ID to resolve. Required.
• --jurisdiction <JURISDICTION> Jurisdiction to resolve. Required.
• --coverage-class <COVERAGE_CLASS> Coverage class to resolve. Required.
• --currency <CURRENCY> Currency to resolve. Required.

chio trust liability-market

Issue quote, placement, and bound-coverage artifacts and list workflow state.

chio trust liability-market [OPTIONS] <COMMAND>

• chio trust liability-market quote-request-issue Issue and persist a signed liability quote request from JSON or YAML input.
• chio trust liability-market quote-response-issue Issue and persist a signed liability quote response from JSON or YAML input.
• chio trust liability-market pricing-authority-issue Issue and persist a signed delegated pricing-authority artifact.
• chio trust liability-market placement-issue Issue and persist a signed liability placement from JSON or YAML input.
• chio trust liability-market bound-coverage-issue Issue and persist a signed bound-coverage artifact from JSON or YAML input.
• chio trust liability-market auto-bind-issue Evaluate and persist one automatic bind decision plus issued placement/bound coverage.
• chio trust liability-market claim-issue Issue and persist a signed liability claim package from JSON or YAML input.
• chio trust liability-market claim-response-issue Issue and persist a signed liability claim response from JSON or YAML input.
• chio trust liability-market dispute-issue Issue and persist a signed liability claim dispute from JSON or YAML input.
• chio trust liability-market adjudication-issue Issue and persist a signed liability claim adjudication from JSON or YAML input.
• chio trust liability-market claim-payout-instruction-issue Issue and persist a signed liability claim payout instruction from JSON or YAML input.
• chio trust liability-market claim-payout-receipt-issue Issue and persist a signed liability claim payout receipt from JSON or YAML input.
• chio trust liability-market claim-settlement-instruction-issue Issue and persist a signed liability claim settlement instruction from JSON or YAML input.
• chio trust liability-market claim-settlement-receipt-issue Issue and persist a signed liability claim settlement receipt from JSON or YAML input.
• chio trust liability-market list List quote-request to bound-coverage workflow rows.
• chio trust liability-market claims-list List claim-package to adjudication workflow rows.

chio trust liability-market quote-request-issue

Issue and persist a signed liability quote request from JSON or YAML input.

chio trust liability-market quote-request-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML quote-request input file. Required.

chio trust liability-market quote-response-issue

Issue and persist a signed liability quote response from JSON or YAML input.

chio trust liability-market quote-response-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML quote-response input file. Required.

chio trust liability-market pricing-authority-issue

Issue and persist a signed delegated pricing-authority artifact.

chio trust liability-market pricing-authority-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML pricing-authority input file. Required.

chio trust liability-market placement-issue

Issue and persist a signed liability placement from JSON or YAML input.

chio trust liability-market placement-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML placement input file. Required.

chio trust liability-market bound-coverage-issue

Issue and persist a signed bound-coverage artifact from JSON or YAML input.

chio trust liability-market bound-coverage-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML bound-coverage input file. Required.

chio trust liability-market auto-bind-issue

Evaluate and persist one automatic bind decision plus issued placement/bound coverage.

chio trust liability-market auto-bind-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML auto-bind input file. Required.

chio trust liability-market claim-issue

Issue and persist a signed liability claim package from JSON or YAML input.

chio trust liability-market claim-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML claim input file. Required.

chio trust liability-market claim-response-issue

Issue and persist a signed liability claim response from JSON or YAML input.

chio trust liability-market claim-response-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML claim-response input file. Required.

chio trust liability-market dispute-issue

Issue and persist a signed liability claim dispute from JSON or YAML input.

chio trust liability-market dispute-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML dispute input file. Required.

chio trust liability-market adjudication-issue

Issue and persist a signed liability claim adjudication from JSON or YAML input.

chio trust liability-market adjudication-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML adjudication input file. Required.
• --roster-policy-file <ROSTER_POLICY_FILE> JSON file containing the operator roster policy (roster, allowed decision rules, roster anchor). Required when --control-url is not set.

chio trust liability-market claim-payout-instruction-issue

Issue and persist a signed liability claim payout instruction from JSON or YAML input.

chio trust liability-market claim-payout-instruction-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML claim payout instruction input file. Required.
• --roster-policy-file <ROSTER_POLICY_FILE> JSON file containing the operator roster policy. Required when --control-url is not set.

chio trust liability-market claim-payout-receipt-issue

Issue and persist a signed liability claim payout receipt from JSON or YAML input.

chio trust liability-market claim-payout-receipt-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML claim payout receipt input file. Required.

chio trust liability-market claim-settlement-instruction-issue

Issue and persist a signed liability claim settlement instruction from JSON or YAML input.

chio trust liability-market claim-settlement-instruction-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML claim settlement instruction input file. Required.
• --roster-policy-file <ROSTER_POLICY_FILE> JSON file containing the operator roster policy. Required when --control-url is not set.

chio trust liability-market claim-settlement-receipt-issue

Issue and persist a signed liability claim settlement receipt from JSON or YAML input.

chio trust liability-market claim-settlement-receipt-issue [OPTIONS] --input-file <INPUT_FILE>

• --input-file <INPUT_FILE> JSON or YAML claim settlement receipt input file. Required.

chio trust liability-market list

List quote-request to bound-coverage workflow rows.

chio trust liability-market list [OPTIONS]

• --quote-request-id <QUOTE_REQUEST_ID> Filter by quote request ID.
• --provider-id <PROVIDER_ID> Filter by provider ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --jurisdiction <JURISDICTION> Filter by jurisdiction.
• --coverage-class <COVERAGE_CLASS> Filter by coverage class (tool_execution, data_breach, financial_loss, professional_liability, regulatory_response).
• --currency <CURRENCY> Filter by currency.
• --limit <LIMIT> Maximum number of workflow rows to embed. Default 50.

chio trust liability-market claims-list

List claim-package to adjudication workflow rows.

chio trust liability-market claims-list [OPTIONS]

• --claim-id <CLAIM_ID> Filter by claim ID.
• --provider-id <PROVIDER_ID> Filter by provider ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --jurisdiction <JURISDICTION> Filter by jurisdiction.
• --policy-number <POLICY_NUMBER> Filter by policy number.
• --limit <LIMIT> Maximum number of claim rows to embed. Default 50.

chio trust underwriting-input

Export a signed underwriting policy-input snapshot from canonical trust data.

chio trust underwriting-input [OPTIONS] <COMMAND>

chio trust underwriting-input export

Export a signed underwriting policy-input snapshot from local state or trust-control.

chio trust underwriting-input export [OPTIONS]

• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt references to embed. Default 100.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust underwriting-decision

Evaluate a bounded underwriting decision from canonical trust data.

chio trust underwriting-decision [OPTIONS] <COMMAND>

• chio trust underwriting-decision evaluate Evaluate a bounded underwriting decision from local state or trust-control.
• chio trust underwriting-decision simulate Simulate an alternative underwriting policy against canonical evidence without persisting a decision.
• chio trust underwriting-decision issue Issue and persist a signed underwriting decision artifact.
• chio trust underwriting-decision list List persisted underwriting decision artifacts and appeal status.

chio trust underwriting-decision evaluate

Evaluate a bounded underwriting decision from local state or trust-control.

chio trust underwriting-decision evaluate [OPTIONS]

• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt references to inspect. Default 100.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust underwriting-decision simulate

Simulate an alternative underwriting policy against canonical evidence without persisting a decision.

chio trust underwriting-decision simulate [OPTIONS] --policy-file <POLICY_FILE>

• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt references to inspect. Default 100.
• --policy-file <POLICY_FILE> YAML or JSON underwriting decision policy file. Required.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.

chio trust underwriting-decision issue

Issue and persist a signed underwriting decision artifact.

chio trust underwriting-decision issue [OPTIONS]

• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --since <SINCE> Include receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Include receipts with timestamp <= this Unix seconds value.
• --receipt-limit <RECEIPT_LIMIT> Maximum number of receipt references to inspect. Default 100.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Optional local certification registry file used when not using --control-url.
• --supersedes-decision-id <SUPERSEDES_DECISION_ID> Optional prior decision ID this new artifact supersedes.

chio trust underwriting-decision list

List persisted underwriting decision artifacts and appeal status.

chio trust underwriting-decision list [OPTIONS]

• --decision-id <DECISION_ID> Filter by decision ID.
• --capability <CAPABILITY> Filter by capability ID.
• --agent-subject <AGENT_SUBJECT> Filter by agent subject public key.
• --tool-server <TOOL_SERVER> Filter by tool server.
• --tool-name <TOOL_NAME> Filter by tool name.
• --outcome <OUTCOME> Filter by outcome (approve, reduce_ceiling, step_up, deny).
• --lifecycle-state <LIFECYCLE_STATE> Filter by lifecycle state (active, superseded).
• --appeal-status <APPEAL_STATUS> Filter by latest appeal status (open, accepted, rejected).
• --limit <LIMIT> Maximum number of persisted decision rows to return. Default 50.

chio trust underwriting-appeal

Create or resolve underwriting appeals against persisted decisions.

chio trust underwriting-appeal [OPTIONS] <COMMAND>

• chio trust underwriting-appeal create Create an underwriting appeal record for one persisted decision.
• chio trust underwriting-appeal resolve Resolve one open underwriting appeal.

chio trust underwriting-appeal create

Create an underwriting appeal record for one persisted decision.

chio trust underwriting-appeal create [OPTIONS] --decision-id <DECISION_ID> --requested-by <REQUESTED_BY> --reason <REASON>

• --decision-id <DECISION_ID> Decision ID to appeal. Required.
• --requested-by <REQUESTED_BY> Operator or system subject opening the appeal. Required.
• --reason <REASON> Short appeal reason. Required.
• --note <NOTE> Optional freeform note.

chio trust underwriting-appeal resolve

Resolve one open underwriting appeal.

chio trust underwriting-appeal resolve [OPTIONS] --appeal-id <APPEAL_ID> --resolution <RESOLUTION> --resolved-by <RESOLVED_BY>

• --appeal-id <APPEAL_ID> Appeal ID to resolve. Required.
• --resolution <RESOLUTION> Resolution outcome (accepted or rejected). Required.
• --resolved-by <RESOLVED_BY> Operator or system subject resolving the appeal. Required.
• --note <NOTE> Optional freeform note.
• --replacement-decision-id <REPLACEMENT_DECISION_ID> Optional replacement decision ID when an appeal resolution references a superseding artifact.

chio trust trace-verify

Check a signed observation log against a bounded transition model.

chio trust trace-verify [OPTIONS] --log <LOG> --trusted-key <TRUSTED_KEYS>

• --log <LOG> Canonical NDJSON observation log. Required.
• --trusted-key <TRUSTED_KEYS> Trusted observer public key. Repeat to trust multiple observers. Required.
• --spec <SPEC> Transition model used for projection and reachability. Default revocation-propagation. Values revocation-propagation.
• --apalache-bin <APALACHE_BIN> Apalache executable. Default apalache-mc.
• --timeout-secs <TIMEOUT_SECS> Maximum seconds for each bounded reachability query. Default 300.
• --itf-output <ITF_OUTPUT> Optional path for the deterministic ITF projection.
• --report-output <REPORT_OUTPUT> Optional path for the validation report.

chio trust revoke

Persist a capability revocation into the configured revocation database.

chio trust revoke [OPTIONS] --capability-id <CAPABILITY_ID>

• --capability-id <CAPABILITY_ID> Capability ID to revoke. Required.

chio trust federated-issue

Issue one local capability after verifying a challenge-bound portable presentation.

chio trust federated-issue [OPTIONS] --presentation-response <PRESENTATION_RESPONSE> --challenge <CHALLENGE> --capability-policy <CAPABILITY_POLICY>

• --presentation-response <PRESENTATION_RESPONSE> Signed passport presentation response from the external agent. Required.
• --challenge <CHALLENGE> Exact expected challenge JSON used to bind the presentation to this verifier. Required.
• --capability-policy <CAPABILITY_POLICY> Policy file whose default capability definition is the single capability to issue. Required.
• --enterprise-identity <ENTERPRISE_IDENTITY> Optional enterprise identity context JSON used for provider-admin-gated admission.
• --delegation-policy <DELEGATION_POLICY> Optional signed federated delegation policy that sets the parent scope/TTL ceiling.
• --upstream-capability-id <UPSTREAM_CAPABILITY_ID> Optional imported upstream capability ID used as the parent for multi-hop federated delegation.

chio trust federated-delegation-policy-create

Create a signed federated delegation policy from a single default capability.

chio trust federated-delegation-policy-create [OPTIONS] --output <OUTPUT> --signing-seed-file <SIGNING_SEED_FILE> --issuer <ISSUER> --partner <PARTNER> --verifier <VERIFIER> --capability-policy <CAPABILITY_POLICY> --expires-at <EXPIRES_AT>

• --output <OUTPUT> Output path for the signed policy JSON. Required.
• --signing-seed-file <SIGNING_SEED_FILE> Persistent seed file used to sign the federated delegation policy. Required.
• --issuer <ISSUER> Local issuer name or organization identifier. Required.
• --partner <PARTNER> External partner name or organization identifier. Required.
• --verifier <VERIFIER> Trust-control verifier URL this policy is bound to. Required.
• --capability-policy <CAPABILITY_POLICY> Capability policy whose single default capability becomes the delegation ceiling. Required.
• --expires-at <EXPIRES_AT> Policy expiration as Unix seconds. Required.
• --purpose <PURPOSE> Optional reason or purpose string embedded in the policy document.
• --parent-capability-id <PARENT_CAPABILITY_ID> Optional upstream capability ID that this delegation policy is allowed to continue from.

chio trust status

Query whether a capability ID is currently revoked.

chio trust status [OPTIONS] --capability-id <CAPABILITY_ID>

• --capability-id <CAPABILITY_ID> Capability ID to check. Required.

chio trust pin

Pin a key for one verification role in the trust file.

chio trust pin [OPTIONS] <ROLE> <KEY>

• <ROLE> Verification role, such as receipt-kernel, swarm.witness, or issuer. chio trust roles lists them. Required.
• <KEY> Key, DID, key file, or partner card. Required.
• --name <NAME> Name for the pin, used by chio trust unpin and shown by verifiers. Defaults to the card’s organization or the key fingerprint.
• --trust <FILE> Trust file to change instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). Reads CHIO_TRUST.

chio trust pins

List the pins in the trust file: name, role, key fingerprint, and where each came from.

chio trust pins [OPTIONS]

• --role <ROLE> Show only the pins for this role.
• --trust <FILE> Trust file to change instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). Reads CHIO_TRUST.

chio trust unpin

Remove a pin from the trust file, for every role or for one.

chio trust unpin [OPTIONS] <NAME>

• <NAME> Pin name from chio trust pins. Required.
• --role <ROLE> Remove the pin from this role only.
• --trust <FILE> Trust file to change instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). Reads CHIO_TRUST.

chio trust roles

List every verification role, the artifacts it signs, and the commands that read it.

chio trust roles [OPTIONS]

chio receipt

Query and list receipts from the receipt store.

chio receipt [OPTIONS] <COMMAND>

• chio receipt list List receipts with optional filters. Output: one JSON receipt per line (JSON Lines).
• chio receipt health Report receipt-store write health and durability status.
• chio receipt flush Flush pending receipt writes to durable storage, bounded by a timeout.
• chio receipt audit Run the full receipt-log audit: claim-log projection validation plus a complete checkpoint-chain verification (the deep check).
• chio receipt retention Inspect or repair the receipt-store retention state.
• chio receipt checkpoint Inspect or advance the receipt-checkpoint chain.
• chio receipt explain Explain why a receipt was allowed or denied.
• chio receipt verify Verify receipt signatures, the signer pin, and action hashes offline, one JSON receipt per line.
• chio receipt verify-process-response Bind a process response to a frozen request and an independently selected context; verifies the receipt, the result content, and the decision.
• chio receipt verify-native-start Verify a released native launch against its signed policy and external pins; does not establish target death, call completion, or a terminal outcome.

chio receipt list

List receipts with optional filters. Output: one JSON receipt per line (JSON Lines).

chio receipt list [OPTIONS]

• --capability <CAPABILITY> Filter by capability ID.
• --tool-server <TOOL_SERVER> Filter by tool server ID.
• --tool-name <TOOL_NAME> Filter by tool name.
• --outcome <OUTCOME> Filter by decision outcome (allow, deny, cancelled, incomplete).
• --since <SINCE> Filter: receipts with timestamp >= this Unix seconds value.
• --until <UNTIL> Filter: receipts with timestamp <= this Unix seconds value.
• --min-cost <MIN_COST> Filter: minimum cost in minor currency units (only financial receipts).
• --max-cost <MAX_COST> Filter: maximum cost in minor currency units (only financial receipts).
• --cost-currency <COST_CURRENCY> Currency for cost filters as a three-letter uppercase code.
• --limit <LIMIT> Maximum number of receipts per page. Default 50.
• --cursor <CURSOR> Cursor for pagination (seq value to start after).
• --tenant <TENANT> Tenant read boundary for the listing. The reading path fails closed when neither --tenant nor --admin-all is supplied.
• --admin-all Explicitly read across all tenants as an administrative operation.
• --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.
• --order <ORDER> Order of the listing. Default oldest. Values oldest, newest.

chio receipt health

Report receipt-store write health and durability status.

chio receipt health [OPTIONS]

chio receipt flush

Flush pending receipt writes to durable storage, bounded by a timeout.

chio receipt flush [OPTIONS]

• --timeout-ms <TIMEOUT_MS> Maximum time to wait for the flush to complete, in milliseconds. Default 5000.

chio receipt audit

Run the full receipt-log audit: claim-log projection validation plus a complete checkpoint-chain verification (the deep check).

chio receipt audit [OPTIONS]

• --repair OFFLINE on-disk repair: revalidate the on-disk receipt chain on a local connection before reporting. Run this with the kernel STOPPED. A running kernel keeps its verified head in-memory in a separate process that the CLI cannot reach, so this does NOT clear a live poisoned writer; restart the kernel to reseed a clean head from the validated on-disk state.

chio receipt retention

Inspect or repair the receipt-store retention state.

chio receipt retention [OPTIONS] <COMMAND>

chio receipt retention repair

Repair a receipt store bricked by a retention rotation that left orphaned claim-log rows: remove the rows whose source receipts were archived and deleted, restoring a writable, reopenable store. Fail-closed.

chio receipt retention repair [OPTIONS] --archive <ARCHIVE>

• --archive <ARCHIVE> Archive file that holds the co-archived claim-log rows to validate the removal against. Required.

chio receipt checkpoint

Inspect or advance the receipt-checkpoint chain.

chio receipt checkpoint [OPTIONS] <COMMAND>

• chio receipt checkpoint status Report the current receipt-checkpoint chain status.
• chio receipt checkpoint create Create the next receipt checkpoint, signed by the kernel keypair.
• chio receipt checkpoint verify Verify the integrity of the receipt-checkpoint chain.

chio receipt checkpoint status

Report the current receipt-checkpoint chain status.

chio receipt checkpoint status [OPTIONS]

• --max-batch <MAX_BATCH> Maximum number of receipts to consider per checkpoint batch. Default 1024.

chio receipt checkpoint create

Create the next receipt checkpoint, signed by the kernel keypair.

chio receipt checkpoint create [OPTIONS]

• --kernel-seed-file <KERNEL_SEED_FILE> Kernel checkpoint signing-seed file.
• --max-batch <MAX_BATCH> Maximum number of receipts to include in the checkpoint batch. Default 1024.

chio receipt checkpoint verify

Verify the integrity of the receipt-checkpoint chain.

chio receipt checkpoint verify [OPTIONS]

chio receipt explain

Explain why a receipt was allowed or denied.

chio receipt explain [OPTIONS] <RECEIPT_ID>

• <RECEIPT_ID> Receipt ID. Use a sentinel (e.g. bilateral) when reading a bilateral artifact via --input-file; the receipt_id is informational for that path. Required.
• --input-file <INPUT_FILE> Optional JSON file containing one receipt, or a BilateralCoSignArtifacts document.
• --depth <DEPTH> Maximum parent depth to render. Default 8.
• --fanout-limit <FANOUT_LIMIT> Maximum fanout siblings to render per level. Default 32.
• --inspect-bilateral Emit a structural inspection trace of the bilateral envelope. Note: this trace does NOT perform Ed25519 signature verification. For real verification, use the kernel-resident chio_federation::bilateral_dsse::verify_dsse_envelope against pinned passport keys.
• --tenant <TENANT> Tenant read boundary for the explanation. The reading path fails closed when neither --tenant nor --admin-all is supplied.
• --admin-all Explicitly read across all tenants as an administrative operation.

$ RECEIPT=$(chio --receipt-db .chio/receipts.db receipt list --admin-all \
    | jq -r 'select(.decision.verdict == "allow") | .id')
$ chio --receipt-db .chio/receipts.db receipt explain "$RECEIPT" --admin-all

receipt: 5f61461c24462125fb4c6220847b787c2917c0898cfe6c2a043d4a0eba2dd1de
schema: chio.receipt.v1
identity: 5f61461c24462125fb4c6220847b787c2917c0898cfe6c2a043d4a0eba2dd1de
decision: allow
policy_hash: 69e943b96e9ce64d0264bb56bf8930e77bd4e68adf68fcf1395790dae03e6b55
scope_diff: requested scope vs granted scope is not embedded in this receipt
parents: 0

chio receipt verify

Verify receipt signatures, the signer pin, and action hashes offline, one JSON receipt per line.

chio receipt verify [OPTIONS] --input <INPUT> --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY>

• --input <INPUT> One original JSON receipt per line. Blank lines are ignored. Required.
• --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY> Independently trusted kernel public key (raw bytes or algorithm-aware hex). Required.

chio receipt verify-process-response

Bind a process response to a frozen request and an independently selected context; verifies the receipt, the result content, and the decision.

chio receipt verify-process-response [OPTIONS] --response <RESPONSE> --request <REQUEST> --context <CONTEXT> --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY>

• --response <RESPONSE> Process response to verify. Required.
• --request <REQUEST> The frozen request the response must answer. Required.
• --context <CONTEXT> JSON object with runtime_id, process_id, and capability_id from the host. Required.
• --trusted-kernel-pubkey <TRUSTED_KERNEL_PUBKEY> Independently trusted kernel public key. Required.

chio receipt verify-native-start

Verify a released native launch against its signed policy and external pins; does not establish target death, call completion, or a terminal outcome.

chio receipt verify-native-start [OPTIONS] --signed-policy <SIGNED_POLICY> --enforcement <ENFORCEMENT> --server-id <SERVER_ID> --trusted-policy-signer <TRUSTED_POLICY_SIGNER> --expected-receipt-id <EXPECTED_RECEIPT_ID> --expected-target-sha256 <EXPECTED_TARGET_SHA256>

• --signed-policy <SIGNED_POLICY> Signed native-launch policy. Required.
• --enforcement <ENFORCEMENT> One original enforcement receipt, in JSON. Required.
• --server-id <SERVER_ID> Server the launch belongs to. Required.
• --trusted-policy-signer <TRUSTED_POLICY_SIGNER> Independently trusted policy signer, as algorithm-aware public-key hex. Required.
• --expected-receipt-id <EXPECTED_RECEIPT_ID> Receipt id the enforcement receipt must carry. Required.
• --expected-target-sha256 <EXPECTED_TARGET_SHA256> SHA-256 of the target executable the launch must have run. Required.

chio evidence

Export an offline evidence package from the local receipt database.

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.

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.

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.

$ 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

chio evidence import

Import a verified bilateral evidence package for later federated delegation.

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.

chio evidence federation-policy [OPTIONS] <COMMAND>

chio evidence federation-policy create

Create a signed bilateral federation policy for receipt sharing.

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.

chio certify

Evaluate a conformance corpus and emit a signed certification artifact.

chio certify [OPTIONS] <COMMAND>

• chio certify check Evaluate conformance evidence and emit a signed pass/fail certification artifact.
• chio certify verify Verify a signed certification artifact.
• chio certify registry Publish, resolve, and revoke certification artifacts in a registry.

chio certify check

Evaluate conformance evidence and emit a signed pass/fail certification artifact.

chio certify check [OPTIONS] --scenarios-dir <SCENARIOS_DIR> --results-dir <RESULTS_DIR> --output <OUTPUT> --tool-server-id <TOOL_SERVER_ID> --signing-seed-file <SIGNING_SEED_FILE>

• --scenarios-dir <SCENARIOS_DIR> Directory containing conformance scenario descriptor JSON files. Required.
• --results-dir <RESULTS_DIR> Directory containing conformance result JSON files. Required.
• --output <OUTPUT> Output path for the signed certification artifact JSON. Required.
• --tool-server-id <TOOL_SERVER_ID> Stable identifier for the tool server being checked. Required.
• --tool-server-name <TOOL_SERVER_NAME> Optional human-readable name for the tool server being checked.
• --report-output <REPORT_OUTPUT> Optional path to write a generated markdown report for the evaluated corpus.
• --criteria-profile <CRITERIA_PROFILE> Certification criteria profile to apply. Default conformance-all-pass-v1.
• --signing-seed-file <SIGNING_SEED_FILE> Persistent seed file used to sign certification artifacts. Required.

chio certify verify

Verify a signed certification artifact.

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

• --input <INPUT> Input path for the signed certification artifact JSON. Required.

chio certify registry

Publish, resolve, and revoke certification artifacts in a registry.

chio certify registry [OPTIONS] <COMMAND>

• chio certify registry publish Publish one signed certification artifact into a local or remote registry.
• chio certify registry publish-network Publish one certification artifact across configured discovery-network operators.
• chio certify registry list List certification artifacts from a local or remote registry.
• chio certify registry get Read one certification artifact from a local or remote registry.
• chio certify registry resolve Resolve the current certification status for one tool server.
• chio certify registry discover Discover certification status across multiple configured operators.
• chio certify registry search Search public certification listings across configured operators.
• chio certify registry transparency Render the public certification transparency feed across configured operators.
• chio certify registry consume Evaluate public certification listings against a local import policy.
• chio certify registry revoke Revoke one certification artifact in a local or remote registry.
• chio certify registry dispute Open or resolve a public certification dispute record.

chio certify registry publish

Publish one signed certification artifact into a local or remote registry.

chio certify registry publish [OPTIONS] --input <INPUT>

• --input <INPUT> Input path for the signed certification artifact JSON. Required.
• --certification-registry-file <CERTIFICATION_REGISTRY_FILE> Local registry file to update when not using --control-url.