Error Lookup

Find a returned error by URN, string code, or number, read its remediation, and decide whether the operation may run again.

On this page

A Chio error is named by a URN and a CHIO-* string code; a wire-level condition also carries a numeric code with its retry strategy.

Search the URN or the string code below, then open the entry for its remediation, stability, and the crates that consume it. Keep the original response and its receipt ID while you investigate.

URN error codes

urn:chio:error:adversarial:escape-detectedfatalAdversarial suite detected an escape from the intended guard boundary.

string code: CHIO-ADVERSARIAL-ESCAPE-DETECTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-conformance, chio-guards

Fail the run, preserve artifacts, and tighten the guard or sandbox before rerunning.

urn:chio:error:arena:replay-divergenceerrorArena replay produced a verdict divergence.

string code: CHIO-ARENA-REPLAY-DIVERGENCE
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-replay-corpus, chio-conformance

Compare the replay receipt, policy, guard bundle, and provider fixture before accepting the run.

urn:chio:error:attest:provenance-missingerrorRequired provenance evidence was missing from the receipt context.

string code: CHIO-ATTEST-PROVENANCE-MISSING
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-attest-verify, chio-otel-receipt-exporter

Regenerate the evidence bundle and include provenance before submitting the operation.

urn:chio:error:attest:quote-verification-failedfatalTEE quote verification failed.

string code: CHIO-ATTEST-QUOTE-VERIFICATION-FAILED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-attest-verify, chio-tee

Reject the attestation and refresh the quote or verifier trust roots before retrying.

urn:chio:error:attest:receipt-signing-failedfatalKernel could not sign the receipt for a decision or tool call.

string code: CHIO-KERNEL-RECEIPT-SIGNING-FAILED
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-attest-verify

Treat the operation as failed and repair the signing key, key store, or canonical payload.

urn:chio:error:attest:receipt-verification-failederrorReceipt evidence failed its integrity, signature or session binding checks.

string code: CHIO-ATTEST-RECEIPT-VERIFICATION-FAILED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-acp-proxy, chio-control-plane, chio-cli

Reject the evidence and restore the authentic receipt history and trusted signer before retrying.

urn:chio:error:capability:expirederrorCapability token expired before the kernel evaluated the request.

string code: CHIO-KERNEL-CAPABILITY-EXPIRED
json-rpc: 2101
stability: stable since 0.1.0
consumed by: chio-kernel, chio-cli, chio-control-plane

Obtain or issue a fresh time-bounded capability before retrying the operation.

urn:chio:error:capability:not-yet-validerrorCapability token is not valid at the current evaluation time.

string code: CHIO-KERNEL-CAPABILITY-NOT-YET-VALID
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-cli

Retry after the not-before timestamp or issue a capability with the intended validity window.

urn:chio:error:capability:revokederrorCapability token was revoked and must not be retried.

string code: CHIO-KERNEL-CAPABILITY-REVOKED
json-rpc: 2102
stability: stable since 0.1.0
consumed by: chio-kernel, chio-cli, chio-control-plane

Resolve the revocation reason and request a newly issued capability.

urn:chio:error:capability:scope-exceedederrorCapability scope does not allow the requested tool, resource, or prompt.

string code: CHIO-KERNEL-OUT-OF-SCOPE-TOOL
json-rpc: 2100
stability: stable since 0.1.0
consumed by: chio-kernel, chio-cli, chio-control-plane

Issue a capability that explicitly grants the requested scope, or change the request to fit the granted scope.

urn:chio:error:capability:signature-invalidfatalCapability signature verification failed.

string code: CHIO-KERNEL-INVALID-SIGNATURE
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-credentials

Reject the capability, verify issuer trust, and reissue the token with canonical JSON signing.

urn:chio:error:capability:subject-mismatcherrorCapability subject does not match the requesting actor.

string code: CHIO-KERNEL-SUBJECT-MISMATCH
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-credentials

Bind the capability to the correct subject DID or use credentials for the subject named by the token.

urn:chio:error:cli:active-defense-requirederrorA flow-required manifest was given to a host that installs no flow runtime.

string code: CHIO-CLI-ACTIVE-DEFENSE-REQUIRED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Run the server on an active-defense host that installs the flow runtime; dropping the manifest requirement is not a fix.

urn:chio:error:cli:admission-store-requirederrorDurable admission has no session database to record operations and tool outcomes in.

string code: CHIO-CLI-ADMISSION-STORE-REQUIRED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass --session-db <path> so operations and tool outcomes survive a restart.

urn:chio:error:cli:anchor-requirederrorA ledger query has no anchor to scope it.

string code: CHIO-CLI-ANCHOR-REQUIRED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass at least one of --capability, --agent-subject, or --tool-server.

urn:chio:error:cli:auth-requirederrorA remote MCP edge was started with no authentication mode.

string code: CHIO-CLI-AUTH-REQUIRED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass one of --auth-token, --auth-jwt-public-key, --auth-jwt-discovery-url, --auth-introspection-url, or --auth-server-seed-file.

urn:chio:error:cli:doctor-chio-yaml-invaliderrorchio doctor schema probe found chio.yaml validation errors.

string code: CHIO-CLI-DOCTOR-CHIO-YAML-INVALID
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-cli

Repair the document at the reported line and column and rerun chio doctor.

urn:chio:error:cli:doctor-cosign-stalewarningchio doctor cosign freshness probe found a stale or unverifiable guard-bundle signature.

string code: CHIO-CLI-DOCTOR-COSIGN-STALE
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-cli, chio-attest-verify

Re-pull the guard bundle and verify its sigstore signature against the trusted identity set.

urn:chio:error:cli:doctor-oci-unreachablewarningchio doctor OCI registry reachability probe could not reach the configured registry.

string code: CHIO-CLI-DOCTOR-OCI-UNREACHABLE
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-cli, chio-guard-registry

Verify the registry URL, network egress, and credentials, or run with CHIO_DOCTOR_SKIP_NETWORK=1 to bypass.

urn:chio:error:cli:doctor-otel-unresolvedwarningchio doctor OTEL probe could not resolve the OTLP endpoint or kernel runtime metrics.

string code: CHIO-CLI-DOCTOR-OTEL-UNRESOLVED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-cli

Set OTEL_EXPORTER_OTLP_ENDPOINT and ensure the chio-tower /metrics endpoint exposes chio_kernel_dispatch_inflight.

urn:chio:error:cli:doctor-probe-failederrorchio doctor reported one or more failing probes.

string code: CHIO-CLI-DOCTOR-PROBE-FAILED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-cli

Inspect the per-probe diagnostics, fix the reported issues, and rerun chio doctor.

urn:chio:error:cli:doctor-toolchain-mismatcherrorchio doctor toolchain probe found a Rust toolchain mismatch.

string code: CHIO-CLI-DOCTOR-TOOLCHAIN-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-cli

Install the workspace MSRV (or the version pinned in rust-toolchain.toml) and rerun chio doctor.

urn:chio:error:cli:flag-conflicterrorTwo flags were given that cannot apply to the same read or run.

string code: CHIO-CLI-FLAG-CONFLICT
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Drop the flag the message names, or run the command in the mode that flag belongs to.

urn:chio:error:cli:flag-out-of-rangeerrorA flag value is outside the range the command accepts.

string code: CHIO-CLI-FLAG-OUT-OF-RANGE
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass a value inside the range the message names.

urn:chio:error:cli:input-not-founderrorAn input file the command reads does not exist.

string code: CHIO-CLI-INPUT-NOT-FOUND
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Check the path the message names and pass an existing file.

urn:chio:error:cli:ioerrorCLI failed while reading or writing local data.

string code: CHIO-CLI-IO
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-cli, chio-control-plane

Check the path, permissions, and filesystem state before retrying.

urn:chio:error:cli:jsonerrorCLI failed to parse or render JSON.

string code: CHIO-CLI-JSON
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-cli, chio-control-plane

Fix the JSON payload or output template and rerun the command.

urn:chio:error:cli:othererrorRetired. Every CLI failure carries a specific registry code.

string code: CHIO-CLI-OTHER
json-rpc: none
stability: retired since 0.1.0
consumed by: chio-cli, chio-control-plane

No command returns this code. Look up the code the command printed instead.

urn:chio:error:cli:output-dir-not-emptyerrorThe output directory already holds files, and the command writes a complete package or nothing.

string code: CHIO-CLI-OUTPUT-DIR-NOT-EMPTY
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass a new or empty directory to --output, or remove the existing one first.

urn:chio:error:cli:plan-invaliderrorA process plan fails validation before any worker starts.

string code: CHIO-CLI-PLAN-INVALID
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Fix the field the message names in the plan; a worker resources block must set at least one ceiling.

urn:chio:error:cli:preflight-needs-outputerrorPreflight cannot evaluate guards that read a tool's output, because preflight never runs the tool.

string code: CHIO-CLI-PREFLIGHT-NEEDS-OUTPUT
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Run the check with --mode full --output-fixture <JSON> so output-sensitive guards see explicit fixture output.

urn:chio:error:cli:profile-mismatcherrorAn existing operator profile disagrees with the settings this initialization asked for.

string code: CHIO-CLI-PROFILE-MISMATCH
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Initialize with the settings of the existing profile, or choose a new --directory.

urn:chio:error:cli:receipt-storeerrorA receipt database path does not hold an initialized Chio receipt store.

string code: CHIO-CLI-RECEIPT-STORE
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass --receipt-db the path of the receipt store; check its permissions and schema health.

urn:chio:error:cli:receipt-store-requirederrorThe command needs a durable receipt store and none was given.

string code: CHIO-CLI-RECEIPT-STORE-REQUIRED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass --receipt-store <path> to chio api protect, or --receipt-db <path> to commands that read receipts. chio api protect also accepts --allow-ephemeral-receipts for a run whose receipts may be lost.

urn:chio:error:cli:revocation-storeerrorA revocation database path does not hold an initialized Chio revocation store.

string code: CHIO-CLI-REVOCATION-STORE
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass --revocation-db the path of the revocation store the host reads; check its permissions and schema health.

urn:chio:error:cli:session-emptyerrorThe session holds no receipts to certify.

string code: CHIO-CLI-SESSION-EMPTY
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass the --session-id of a session that has receipts in the store.

urn:chio:error:cli:signing-key-requirederrorThe command signs what it exports and has no signing key.

string code: CHIO-CLI-SIGNING-KEY-REQUIRED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass --authority-seed-file <path> or --authority-db <path>.

urn:chio:error:cli:sqliteerrorCLI SQLite store operation failed.

string code: CHIO-CLI-SQLITE
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-cli, chio-store-sqlite

Check the database path, schema version, and write permissions before retrying.

urn:chio:error:cli:state-abi-mismatcherrorHost state was recorded under a different process ABI than this build speaks.

string code: CHIO-CLI-STATE-ABI-MISMATCH
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Run the release that recorded the state, or start from a new --state directory.

urn:chio:error:cli:store-lockederrorAnother running process holds the store open for writing.

string code: CHIO-CLI-STORE-LOCKED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Stop the process that holds the store, or point this one at its own store.

urn:chio:error:cli:yamlerrorCLI failed to parse or render YAML.

string code: CHIO-CLI-YAML
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-cli, chio-control-plane

Fix the YAML document and rerun the command.

urn:chio:error:custody:app-attest-app-mismatcherrorApple App Attest app-identifier hash did not match the expected application identity.

string code: CHIO-CUSTODY-APP-ATTEST-APP-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; the statement was minted for a different app identifier than the verifier expects.

urn:chio:error:custody:app-attest-cert-chain-invaliderrorApple App Attest certificate chain failed signature or structural verification.

string code: CHIO-CUSTODY-APP-ATTEST-CERT-CHAIN-INVALID
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; the certificate chain did not verify against the pinned Apple roots.

urn:chio:error:custody:app-attest-challenge-mismatcherrorApple App Attest challenge hash did not match the issued challenge.

string code: CHIO-CUSTODY-APP-ATTEST-CHALLENGE-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation and reissue a fresh challenge; replayed or mismatched challenges are denied fail-closed.

urn:chio:error:custody:app-attest-counter-rollbackerrorApple App Attest assertion counter went backwards relative to the last accepted value.

string code: CHIO-CUSTODY-APP-ATTEST-COUNTER-ROLLBACK
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the assertion; a counter rollback indicates replay or a cloned key and is denied fail-closed.

urn:chio:error:custody:app-attest-credential-key-mismatcherrorApple App Attest leaf certificate public key did not match the credential public key in authenticator data (WebAuthn registration step 6).

string code: CHIO-CUSTODY-APP-ATTEST-CREDENTIAL-KEY-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; the attested hardware key is not bound to the enrolled credential public key and is denied fail-closed.

urn:chio:error:custody:app-attest-invalid-cborerrorApple App Attest statement failed to decode as valid CBOR or was missing a required field.

string code: CHIO-CUSTODY-APP-ATTEST-INVALID-CBOR
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; do not retry without a freshly generated App Attest statement from the device.

urn:chio:error:custody:app-attest-invalid-rooterrorApple App Attest certificate chain did not anchor to the pinned Apple App Attestation root.

string code: CHIO-CUSTODY-APP-ATTEST-INVALID-ROOT
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; verify the device produced a genuine Apple App Attest statement and that the pinned root is current.

urn:chio:error:custody:app-attest-key-mismatcherrorApple App Attest key identifier did not match the credential bound to this capability.

string code: CHIO-CUSTODY-APP-ATTEST-KEY-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; the statement was produced by a different hardware key than the one enrolled.

urn:chio:error:custody:assertion-rejectederrorWebAuthn assertion failed structural or signature verification.

string code: CHIO-CUSTODY-ASSERTION-REJECTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-control-plane

Treat the assertion as untrusted; do not retry without a fresh challenge from the issuer.

urn:chio:error:custody:audience-mismatcherrorCapability presented to a different audience than it was minted for.

string code: CHIO-CUSTODY-AUDIENCE-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel

Issue or request a capability whose audience pin matches the verifier identity.

urn:chio:error:custody:capability-expirederrorPasskey capability expired before the verifier evaluated the request.

string code: CHIO-CUSTODY-CAPABILITY-EXPIRED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel

Mint a fresh capability; passkey capabilities are pinned to a five-minute lifetime.

urn:chio:error:custody:credential-revokederrorWebAuthn credential bound to this capability has been revoked.

string code: CHIO-CUSTODY-CREDENTIAL-REVOKED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel, chio-revocation-oracle

Re-enroll the user's authenticator and request a freshly-issued capability.

urn:chio:error:custody:hardware-key-unavailablefatalRequired hardware custody key was unavailable.

string code: CHIO-CUSTODY-HARDWARE-KEY-UNAVAILABLE
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-tee, chio-attest-verify

Do not fall back to a software key; restore the custody key path and retry.

urn:chio:error:custody:internal-encodingfatalCustody surface failed to canonicalize, encode, or decode an envelope.

string code: CHIO-CUSTODY-INTERNAL-ENCODING
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw

Treat as an internal error; do not retry until the encoding bug is resolved. No fresh challenge will help.

urn:chio:error:custody:play-integrity-app-rejectederrorGoogle Play Integrity verdict rejected the application (unrecognized or tampered package).

string code: CHIO-CUSTODY-PLAY-INTEGRITY-APP-REJECTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; the Play Integrity verdict did not recognize the app as a genuine, unmodified install.

urn:chio:error:custody:play-integrity-device-rejectederrorGoogle Play Integrity verdict rejected the device integrity signal.

string code: CHIO-CUSTODY-PLAY-INTEGRITY-DEVICE-REJECTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; the Play Integrity verdict did not attest a trustworthy device.

urn:chio:error:custody:play-integrity-invalid-tokenerrorGoogle Play Integrity token failed to decode or verify.

string code: CHIO-CUSTODY-PLAY-INTEGRITY-INVALID-TOKEN
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation; do not retry without a freshly minted Play Integrity token from the device.

urn:chio:error:custody:play-integrity-nonce-mismatcherrorGoogle Play Integrity token nonce did not match the issued challenge.

string code: CHIO-CUSTODY-PLAY-INTEGRITY-NONCE-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-kernel-mobile

Reject the attestation and reissue a fresh nonce; replayed or mismatched nonces are denied fail-closed.

urn:chio:error:custody:rate-limitederrorCapability issuance was denied because the subject exceeded its rate budget.

string code: CHIO-CUSTODY-RATE-LIMITED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw

Retry after the rate window elapses; the mint is denied fail-closed before the revocation oracle, nonce store, or signing backend are consulted.

urn:chio:error:custody:replay-detectederrorWebAuthn challenge nonce was previously redeemed for this credential.

string code: CHIO-CUSTODY-REPLAY-DETECTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-control-plane

Obtain a fresh challenge from the issuer; replayed assertions are denied fail-closed.

urn:chio:error:custody:user-verification-requirederrorWebAuthn assertion verified cryptographically but did not report user verification.

string code: CHIO-CUSTODY-USER-VERIFICATION-REQUIRED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-custody-hw, chio-control-plane

Re-attempt the ceremony with a user-verifying gesture (PIN, biometric); custody issuance requires UV.

urn:chio:error:delegation:chain-revokederrorDelegation chain includes a revoked link.

string code: CHIO-KERNEL-DELEGATION-CHAIN-REVOKED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel, chio-federation

Rebuild the chain from non-revoked grants before retrying delegated execution.

urn:chio:error:delegation:policy-window-invaliderrorA federated delegation policy expires before it is created.

string code: CHIO-DELEGATION-POLICY-WINDOW-INVALID
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass an --expires-at later than the current time, in Unix seconds.

urn:chio:error:delegation:revocation-epoch-not-monotonicerrorA revocation checkpoint carries an epoch at or below the last published epoch.

string code: CHIO-DELEGATION-REVOCATION-EPOCH-NOT-MONOTONIC
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli, chio-federation

Publish a checkpoint whose epoch is greater than the last published one.

urn:chio:error:economy:candidate-staging-exceedederrorA candidate repository did not fit inside the operator's repository staging limits.

string code: CHIO-ECONOMY-CANDIDATE-STAGING-EXCEEDED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Submit a smaller candidate, or raise the operator's repository staging limits.

urn:chio:error:economy:metering-unavailableerrorMetering or balance state was unavailable for an economic decision.

string code: CHIO-ECONOMY-METERING-UNAVAILABLE
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-metering, chio-settle, chio-credit

Retry after the metering backend or settlement ledger is reachable and current.

urn:chio:error:economy:prepayment-requirederrorA governed intent requires prepayment and no payment adapter is configured to take it.

string code: CHIO-ECONOMY-PREPAYMENT-REQUIRED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass --payment-adapter sim for a local run, or --payment-adapter http-x402 with a facilitator URL.

urn:chio:error:economy:scorecard-emptyerrorNo governed receipt matches the scorecard selection.

string code: CHIO-ECONOMY-SCORECARD-EMPTY
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Select an agent that has governed receipts in this store, or run governed calls first.

urn:chio:error:economy:status-feed-mismatcherrorA finding-market status request named a feed this operator does not publish.

string code: CHIO-ECONOMY-STATUS-FEED-MISMATCH
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Request the status feed named in the operator profile.

urn:chio:error:guard:deniederrorGuard pipeline denied the request or response.

string code: CHIO-KERNEL-GUARD-DENIED
json-rpc: 3100
stability: stable since 0.1.0
consumed by: chio-kernel, chio-guards, chio-cli

Inspect the guard verdict and adjust the prompt, tool input, policy, or output before retrying.

urn:chio:error:guard:input-redactedwarningGuard redacted sensitive input before it crossed a trust boundary.

string code: CHIO-GUARD-INPUT-REDACTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-data-guards, chio-guards

Review the redaction receipt and provide lower-risk input if the tool requires the removed field.

urn:chio:error:guard:output-redactedwarningGuard redacted sensitive output before it crossed a trust boundary.

string code: CHIO-GUARD-OUTPUT-REDACTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-data-guards, chio-guards

Review the guard receipt and update the downstream consumer to handle redacted fields.

urn:chio:error:guard:wasm-trapfatalWASM guard trapped during evaluation.

string code: CHIO-GUARD-WASM-TRAP
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-wasm-guards, chio-guard-sdk

Fail closed, inspect the guard bundle, and republish a guard that completes deterministically.

urn:chio:error:kernel:budget-authorize-replayerrorKernel rejected a replayed budget authorization event.

string code: CHIO-KERNEL-BUDGET-AUTHORIZE-REPLAY
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-metering, chio-control-plane

Retry only with a fresh request identity that produces a unique budget authorization event.

urn:chio:error:kernel:budget-exhaustederrorKernel budget for the requested operation was exhausted.

string code: CHIO-KERNEL-BUDGET-EXHAUSTED
json-rpc: 4100
stability: stable since 0.1.0
consumed by: chio-kernel, chio-metering, chio-cli

Retry only after replenishing the budget, widening the grant, or reconciling billing state.

urn:chio:error:kernel:delivery-contract-digest-mismatcherrorDelivered output did not hash to the frozen expected digest of the delivery contract.

string code: CHIO-KERNEL-DELIVERY-CONTRACT-DIGEST-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel, chio-conformance

The delivery is rejected and no money moves. Re-run the tool so the output matches the expected digest before retrying.

urn:chio:error:kernel:delivery-contract-unsupported-carriererrorRequest carried an output-digest delivery contract the evaluator cannot enforce.

string code: CHIO-KERNEL-DELIVERY-CONTRACT-UNSUPPORTED-CARRIER
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel, chio-conformance

Route the request to an output-aware durable terminal, or drop the output_digest_sha256 constraint before retrying.

urn:chio:error:kernel:finding-delivery-media-type-mismatcherrorRevealed finding payload did not carry the media type the signed finding advertises.

string code: CHIO-KERNEL-FINDING-DELIVERY-MEDIA-TYPE-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel, chio-conformance

The reveal is rejected and the hold is released. Re-run the reveal so the delivered envelope carries the advertised media type.

urn:chio:error:kernel:finding-purchase-context-invaliderrorFinding-purchase marker or its signed purchase context failed verification.

string code: CHIO-KERNEL-FINDING-PURCHASE-CONTEXT-INVALID
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel, chio-conformance

Present a well-formed local reversible-hold marker with the matching signed purchase context, the exact offered token, and a finding_id argument equal to the marked sale.

urn:chio:error:kernel:finding-purchase-unsupported-admissionerrorGrant carried a finding-purchase marker the evaluator cannot admit.

string code: CHIO-KERNEL-FINDING-PURCHASE-UNSUPPORTED-ADMISSION
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel, chio-conformance

Route the reveal to a deployment with purchase-aware admission, or drop the require_finding_purchase marker before retrying.

urn:chio:error:kernel:internal-errorfatalKernel hit an internal error while evaluating the request.

string code: CHIO-KERNEL-INTERNAL
json-rpc: 6100
stability: stable since 0.1.0
consumed by: chio-kernel, chio-cli

Retry with bounded backoff only after preserving the receipt and diagnostic context.

urn:chio:error:kernel:receipt-read-context-missingerrorReceipt read has no authenticated or local operator context.

string code: CHIO-KERNEL-RECEIPT-READ-CONTEXT-MISSING
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-kernel, chio-store-sqlite

Reject the input and check the original signed bytes and authenticated read context.

urn:chio:error:kernel:request-cancelledwarningKernel request was cancelled before completion.

string code: CHIO-KERNEL-REQUEST-CANCELLED
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-tool-call-fabric

Treat any partial tool output as invalid and retry with a new request if work is still required.

urn:chio:error:kernel:request-incompleteerrorKernel request is missing required fields.

string code: CHIO-KERNEL-REQUEST-INCOMPLETE
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-core-types

Provide every required request field before dispatching the operation.

urn:chio:error:kernel:runtime-admission-readiness-timeouterrorRuntime admission readiness did not resolve before the dispatch deadline.

string code: CHIO-KERNEL-RUNTIME-ADMISSION-READINESS-TIMEOUT
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel

Restore the runtime admission dependency or increase the bounded readiness timeout before retrying.

urn:chio:error:kernel:session-already-existserrorSession creation attempted to reuse an existing session identifier.

string code: CHIO-KERNEL-SESSION-ALREADY-EXISTS
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-http-session

Choose a new session identifier or attach to the existing session.

urn:chio:error:kernel:session-not-initializederrorRequest arrived before the session was initialized.

string code: CHIO-KERNEL-UNKNOWN-SESSION
json-rpc: 1001
stability: stable since 0.1.0
consumed by: chio-kernel, chio-http-session

Open a new session and complete initialization before retrying the operation.

urn:chio:error:lineage:ancestor-missingerrorLineage graph references an ancestor that cannot be resolved.

string code: CHIO-LINEAGE-ANCESTOR-MISSING
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-anchor, chio-otel-receipt-exporter

Repair the lineage edge or import the missing receipt before accepting the graph.

urn:chio:error:manifest:resource-root-deniederrorRequested resource root is not allowed by the manifest.

string code: CHIO-KERNEL-RESOURCE-ROOT-DENIED
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-manifest, chio-kernel

Grant the resource root in the manifest or request a resource under an allowed root.

urn:chio:error:manifest:schema-invaliderrorManifest did not validate against the expected schema.

string code: CHIO-CLI-YAML
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-manifest, chio-cli, chio-spec-validate

Fix the manifest shape and rerun schema validation before loading it.

urn:chio:error:manifest:signature-invalidfatalManifest signature verification failed.

string code: CHIO-MANIFEST-SIGNATURE-INVALID
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-manifest, chio-guard-registry

Reject the manifest and republish it with the expected signing key and canonical payload.

urn:chio:error:manifest:tool-not-registerederrorRequested tool is not registered in the active manifest.

string code: CHIO-KERNEL-TOOL-NOT-REGISTERED
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-manifest, chio-kernel

urn:chio:error:mobile:oracle-unreachablewarningMobile SDK could not reach the hosted receipt oracle within the retry budget.

string code: CHIO-MOBILE-ORACLE-UNREACHABLE
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel-mobile, chio-control-plane

Keep the receipt in the encrypted offline queue and retry with bounded backoff after connectivity returns.

urn:chio:error:mobile:receipt-post-rejectederrorHosted oracle rejected a mobile receipt after a successful network POST.

string code: CHIO-MOBILE-RECEIPT-POST-REJECTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel-mobile, chio-custody-hw

Preserve the queued receipt, surface the oracle response, and do not retry until the tenant, signature, or capability binding is repaired.

urn:chio:error:mobile:receipt-schema-invaliderrorMobile receipt export did not validate against the audit-log export schema.

string code: CHIO-MOBILE-RECEIPT-SCHEMA-INVALID
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-kernel-mobile, chio-siem

Keep the receipt in the offline queue and regenerate the export envelope against spec/audit-log/export-schema.v1.json before retrying.

urn:chio:error:policy:case-server-unknownerrorA policy test case names a server the policy does not govern.

string code: CHIO-POLICY-CASE-SERVER-UNKNOWN
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Use a server id the policy grants, or set the default server at the top of the case file.

urn:chio:error:policy:compile-failederrorPolicy document failed to compile.

string code: CHIO-CLI-POLICY
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-policy, chio-cli

Fix the policy syntax or schema issue reported by the compiler and reload the policy.

urn:chio:error:policy:constraint-invaliderrorPolicy constraint was syntactically valid but semantically invalid.

string code: CHIO-KERNEL-INVALID-CONSTRAINT
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-policy, chio-kernel

Regenerate or edit the constraint so every referenced scope, resource, and operator is supported.

urn:chio:error:policy:decision-deniederrorPolicy evaluation denied the requested action.

string code: CHIO-CLI-POLICY
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-policy, chio-cli, chio-control-plane

Inspect the policy rule path and update the request or policy inputs before retrying.

urn:chio:error:policy:governance-deniederrorGovernance policy denied a governed transaction.

string code: CHIO-KERNEL-GOVERNED-TRANSACTION-DENIED
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-governance, chio-kernel

Follow the governance approval path or remove the governed operation from the request.

urn:chio:error:policy:test-file-invaliderrorA policy test case file does not parse, or a case is missing a required field.

string code: CHIO-POLICY-TEST-FILE-INVALID
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Fix the case and field the message names; every case needs a name, a tool, and an expect value.

urn:chio:error:proof:bundle-not-canonicalerrorA proof bundle is not strict canonical JSON, so its bytes changed after it was signed.

string code: CHIO-PROOF-BUNDLE-NOT-CANONICAL
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Verify the bundle as it was issued, or regenerate it from its source receipts.

urn:chio:error:proof:fixture-unknownerrorNo fixture in the catalog has the id given.

string code: CHIO-PROOF-FIXTURE-UNKNOWN
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Run chio proof fixture list for the ids; the message lists the closest ones.

urn:chio:error:proof:input-not-a-bundleerrorA verify input is not a passport, a bundle directory, or a directory of bundles.

string code: CHIO-PROOF-INPUT-NOT-A-BUNDLE
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass a transaction-passport.json, a bundle directory, or a directory of bundles.

urn:chio:error:provider:anthropicerrorAnthropic provider adapter returned a normalized provider error.

string code: CHIO-PROVIDER-ANTHROPIC
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-anthropic-tools-adapter, chio-provider-conformance

Inspect the provider error details and retry only when the adapter marks the failure transient.

urn:chio:error:provider:bedrockerrorBedrock Converse provider adapter returned a normalized provider error.

string code: CHIO-PROVIDER-BEDROCK
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-bedrock-converse-adapter, chio-provider-conformance

Inspect the provider error details and retry only when the adapter marks the failure transient.

urn:chio:error:provider:openaierrorOpenAI provider adapter returned a normalized provider error.

string code: CHIO-PROVIDER-OPENAI
json-rpc: none
stability: unstable since 0.1.0
consumed by: deferred-openai-adapter-ticket, chio-provider-conformance

Inspect the provider error details and retry only when the adapter marks the failure transient.

urn:chio:error:provider:tool-server-errorerrorTool server returned an adapter or execution error.

string code: CHIO-KERNEL-TOOL-SERVER
json-rpc: 5100
stability: stable since 0.1.0
consumed by: chio-kernel, chio-tool-call-fabric, chio-provider-conformance

Retry with bounded backoff only when the provider marks the failure as transient.

urn:chio:error:release:evidence-missingerrorThe release carries no attached evidence of the kind requested.

string code: CHIO-RELEASE-EVIDENCE-MISSING
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

The release workflow attaches all four evidence documents to every release; report the tag.

urn:chio:error:release:provenance-mismatcherrorA binary or archive is not one of the subjects the release provenance names.

string code: CHIO-RELEASE-PROVENANCE-MISMATCH
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Install the release binary with the published installer, or verify a downloaded archive with chio release verify <ARCHIVE>.

urn:chio:error:release:signature-invaliderrorA release signature, its certificate identity, or its transparency-log entry does not verify.

string code: CHIO-RELEASE-SIGNATURE-INVALID
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Download the archive and its signature bundle again from the release page; do not install an archive that fails this check.

urn:chio:error:release:state-unreadableerrorchio release check could not read a store's identity or schema stamp.

string code: CHIO-RELEASE-STATE-UNREADABLE
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass --state a directory the current user can read, and stop any process that holds the store locked for writing.

urn:chio:error:release:unit-flag-removederrorA service command line uses a flag the target release renames or removes.

string code: CHIO-RELEASE-UNIT-FLAG-REMOVED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Change the unit to the replacement flag the message names before you upgrade.

urn:chio:error:replay:deterministic-mismatcherrorReplay produced a deterministic output mismatch.

string code: CHIO-REPLAY-DETERMINISTIC-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-replay-corpus, chio-conformance

Compare the recorded receipt, model fixture, and guard bundle versions before accepting the replay.

urn:chio:error:replay:fixture-driftwarningReplay fixture no longer matches the registry or schema it was recorded against.

string code: CHIO-REPLAY-FIXTURE-DRIFT
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-replay-corpus, chio-spec-codegen

Regenerate the fixture from the current registry and rerun replay validation.

urn:chio:error:replay:trace-not-founderrorReplay trace could not be found.

string code: CHIO-REPLAY-TRACE-NOT-FOUND
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-replay-corpus, chio-cli

Check the replay corpus path and regenerate the trace if it was not archived.

urn:chio:error:security:evidence-dir-existserrorThe --evidence directory already exists, and self-test evidence is written once.

string code: CHIO-SECURITY-EVIDENCE-DIR-EXISTS
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass a new directory to --evidence.

urn:chio:error:security:suite-unknownerrorchio security selftest was given a suite name it does not ship.

string code: CHIO-SECURITY-SUITE-UNKNOWN
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Run chio security selftest --list for the suite names.

urn:chio:error:security:suite-unsupportederrorA selected suite cannot run on this host, and --require-all was set.

string code: CHIO-SECURITY-SUITE-UNSUPPORTED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Run with --portable on this host, or on Linux with cgroup v2 delegation.

urn:chio:error:threat:coverage-gapwarningThreat model coverage check found an uncovered failure mode.

string code: CHIO-THREAT-COVERAGE-GAP
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-conformance, chio-spec-validate

Add a mapped test, fixture, or documented deferral before closing the coverage finding.

urn:chio:error:transaction:artifact-hash-mismatcherrorTransaction proof artifact digest does not match the passport or evidence graph.

string code: CHIO-TRANSACTION-ARTIFACT-HASH-MISMATCH
json-rpc: 7105
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle, regenerate the artifact set, and retry with matching transaction evidence digests.

urn:chio:error:transaction:authorization-not-bounderrorTransaction evidence does not bind required authorization evidence.

string code: CHIO-TRANSACTION-AUTHORIZATION-NOT-BOUND
json-rpc: 7107
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and include capability, policy, approval, or guard evidence bound to the governed transaction.

urn:chio:error:transaction:budget-exceeds-poolerrorSwarm budget allocations add up to more than the pool they draw from.

string code: CHIO-TRANSACTION-BUDGET-EXCEEDS-POOL
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli, chio-swarm-authority

Reject the passport; the allocations must sum to at most the pool total.

urn:chio:error:transaction:buyer-review-rejectederrorBuyer review evidence required by the transaction verifier was rejected.

string code: CHIO-TRANSACTION-BUYER-REVIEW-REJECTED
json-rpc: 7110
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and regenerate buyer review evidence that matches the transaction passport and verifier policy.

urn:chio:error:transaction:dispute-unbounderrorDispute, refund, or remediation evidence is not bound to the transaction.

string code: CHIO-TRANSACTION-DISPUTE-UNBOUND
json-rpc: 7112
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and bind dispute, refund, remediation, and settlement reversal evidence to the transaction passport and receipts.

urn:chio:error:transaction:graph-cycleerrorTransaction evidence graph contains a cycle.

string code: CHIO-TRANSACTION-GRAPH-CYCLE
json-rpc: 7103
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and emit an acyclic evidence graph whose dependency edges can be topologically verified.

urn:chio:error:transaction:graph-not-closederrorTransaction evidence graph does not close over the required artifact references.

string code: CHIO-TRANSACTION-GRAPH-NOT-CLOSED
json-rpc: 7102
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and include every required evidence, claim-set, policy, and receipt node in the graph.

urn:chio:error:transaction:identity-not-bounderrorTransaction evidence does not bind the required identity or subject.

string code: CHIO-TRANSACTION-IDENTITY-NOT-BOUND
json-rpc: 7106
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and include identity evidence bound to the transaction passport subject and evidence graph.

urn:chio:error:transaction:join-parent-mismatcherrorA swarm join receipt names a parent set that differs from the children it joins.

string code: CHIO-TRANSACTION-JOIN-PARENT-MISMATCH
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli, chio-swarm-authority

Reject the passport; the join receipt must name exactly the joined children.

urn:chio:error:transaction:passport-hash-mismatcherrorTransaction passport root digest does not match its bound evidence.

string code: CHIO-TRANSACTION-PASSPORT-HASH-MISMATCH
json-rpc: 7101
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle, rebuild the passport root, and retry with matching evidence graph, claim set, and policy digests.

urn:chio:error:transaction:passport-schema-unsupportederrorTransaction passport schema is unsupported by the verifier.

string code: CHIO-TRANSACTION-PASSPORT-SCHEMA-UNSUPPORTED
json-rpc: 7100
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and regenerate the passport with a registered transaction passport schema.

urn:chio:error:transaction:receipt-uncheckpointederrorTransaction receipt evidence is not checkpointed or included in the required receipt lineage.

string code: CHIO-TRANSACTION-RECEIPT-UNCHECKPOINTED
json-rpc: 7108
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and provide checkpointed receipt or inclusion evidence for the transaction receipt.

urn:chio:error:transaction:required-claim-missingerrorTransaction verifier policy requires a claim that is not verified.

string code: CHIO-TRANSACTION-REQUIRED-CLAIM-MISSING
json-rpc: 7104
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and add verified evidence for the required claim or remove the unsupported requirement.

urn:chio:error:transaction:runtime-proof-rejectederrorRuntime proof evidence required by the transaction verifier was rejected.

string code: CHIO-TRANSACTION-RUNTIME-PROOF-REJECTED
json-rpc: 7109
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and regenerate runtime security, parity, lease, nonce, revocation, sandbox, ack, and terminal receipt evidence.

urn:chio:error:transaction:settlement-unverifiederrorSettlement evidence required by the transaction verifier is absent or unverified.

string code: CHIO-TRANSACTION-SETTLEMENT-UNVERIFIED
json-rpc: 7111
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and include settlement evidence bound to the transaction order, amount, currency, rail, and receipt lineage.

urn:chio:error:transaction:transparency-preview-not-allowederrorTransaction transparency evidence is only preview or advisory when verified transparency is required.

string code: CHIO-TRANSACTION-TRANSPARENCY-PREVIEW-NOT-ALLOWED
json-rpc: 7113
stability: stable since 0.1.0
consumed by: chio-transaction-passport, chio-cli, chio-proof-room

Reject the proof bundle and provide verified transparency inclusion evidence or remove the transparency claim.

urn:chio:error:transaction:witness-scope-mismatcherrorA swarm attenuation witness binds a child scope that differs from the delegated scope.

string code: CHIO-TRANSACTION-WITNESS-SCOPE-MISMATCH
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli, chio-swarm-authority

Reject the passport; each witness must bind the scope its child was delegated.

urn:chio:error:transport:auth-missing-or-invaliderrorTransport authentication was missing, expired, or invalid.

string code: CHIO-CLI-CREDENTIAL
json-rpc: 1100
stability: stable since 0.1.0
consumed by: chio-http-core, chio-credentials

Refresh credentials and resend the request with valid transport authentication.

urn:chio:error:transport:dpop-verification-failedfatalDPoP proof verification failed.

string code: CHIO-KERNEL-DPOP-VERIFICATION-FAILED
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-kernel, chio-http-core

Reject the request and require a fresh proof bound to the correct method, URI, and key.

urn:chio:error:transport:http-failederrorHTTP transport failed before the kernel could evaluate the request.

string code: CHIO-CLI-HTTP
json-rpc: none
stability: stable since 0.1.0
consumed by: chio-http-core, chio-cli

Check endpoint reachability, TLS configuration, and response body diagnostics before retrying.

urn:chio:error:transport:invalid-request-shapeerrorRequest payload did not match the expected wire shape.

string code: CHIO-CLI-JSON
json-rpc: 1002
stability: stable since 0.1.0
consumed by: chio-http-core, chio-spec-validate

Correct the JSON-RPC or HTTP request shape before retrying.

urn:chio:error:transport:method-not-founderrorJSON-RPC method is not supported by the Chio MCP wrapper.

string code: CHIO-TRANSPORT-METHOD-NOT-FOUND
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-cli

Call a recognized method; the MCP wrapper supports tools/list, tools/call, initialize, ping, and JSON-RPC notifications.

urn:chio:error:transport:protocol-version-unsupportederrorPeer requested an unsupported protocol version.

string code: CHIO-CLI-TRANSPORT
json-rpc: 1000
stability: stable since 0.1.0
consumed by: chio-http-core, chio-mcp-edge, chio-a2a-edge

Negotiate a supported Chio protocol version before retrying.

urn:chio:error:transport:upstream-failureerrorWrapped upstream MCP server returned an error while handling a relayed tool call or listing.

string code: CHIO-TRANSPORT-UPSTREAM-FAILURE
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-cli

Inspect the upstream MCP server response; retry only when the upstream marks the failure transient.

urn:chio:error:trust:credential-expirederrorA passport credential is past its expiration date.

string code: CHIO-TRUST-CREDENTIAL-EXPIRED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Issue a fresh passport with chio passport create.

urn:chio:error:trust:file-invaliderrorA trust file does not parse as chio.trust.v1.

string code: CHIO-TRUST-FILE-INVALID
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Fix the trust file at the line the message names.

urn:chio:error:trust:key-malformederrorA key is not a valid Ed25519 key, did:chio identifier, key file, or partner card.

string code: CHIO-TRUST-KEY-MALFORMED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass the key in one of those forms; the message names the field that failed.

urn:chio:error:trust:passport-emptyerrorA passport carries no credential to evaluate.

string code: CHIO-TRUST-PASSPORT-EMPTY
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Create the passport from receipts with chio passport create, which writes at least one credential.

urn:chio:error:trust:pin-mismatcherrorA remote authority presented a key that differs from the operator's pin for it.

string code: CHIO-TRUST-PIN-MISMATCH
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Confirm the authority rotated its key, then pin the current key with chio trust pin issuer <KEY> and unpin the old one.

urn:chio:error:trust:pin-not-founderrorNo pin has the name given to unpin.

string code: CHIO-TRUST-PIN-NOT-FOUND
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Run chio trust pins for the pinned names.

urn:chio:error:trust:role-unknownerrorA role name is not one the verifiers read.

string code: CHIO-TRUST-ROLE-UNKNOWN
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Run chio trust roles for the role names; the message lists the nearest ones.

urn:chio:error:trust:role-unpinnederrorA verifier needs a key for a role and no key is pinned for it.

string code: CHIO-TRUST-ROLE-UNPINNED
json-rpc: none
stability: stable since 0.2.0
consumed by: chio-cli

Pass --trust <FILE>, or pin a key with chio trust pin <ROLE> <KEY>.

urn:chio:error:weights:bundle-rejectederrorCosign bundle for the model card failed cryptographic verification.

string code: CHIO-WEIGHTS-BUNDLE-REJECTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-weights, chio-kernel, chio-cli

Treat the card as untrusted; do not rebind without a fresh, correctly-signed cosign bundle.

urn:chio:error:weights:card-expirederrorModel card expired before the verifier evaluated it.

string code: CHIO-WEIGHTS-CARD-EXPIRED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-weights, chio-kernel

Mint a fresh card; cards bind to issued_at / expires_at and the kernel rejects past expiry.

urn:chio:error:weights:card-mismatcherrorProvider's loaded weights_hash does not match the signed model card.

string code: CHIO-WEIGHTS-CARD-MISMATCH
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-weights, chio-kernel, chio-cli

Re-sign a card whose weights_hash matches the loaded weights blob, or rebind the provider with the correct weights.

urn:chio:error:weights:internal-encodingfatalModel card surface failed to canonicalize, encode, or decode an envelope.

string code: CHIO-WEIGHTS-INTERNAL-ENCODING
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-weights

Treat as an internal error; do not retry until the encoding bug is resolved. No fresh challenge will help.

urn:chio:error:weights:model-card-missingerrorModel weights or runtime artifact lacks a required model card.

string code: CHIO-WEIGHTS-MODEL-CARD-MISSING
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-tee-frame, chio-attest-verify

Attach the signed model card and verify its hash before running the workload.

urn:chio:error:weights:schema-rejectederrorModel card structural validation failed (bad weights_hash, missing required field, or invalid issued_at / expires_at window).

string code: CHIO-WEIGHTS-SCHEMA-REJECTED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-weights

Re-mint the card with a valid v1 schema; check weights_hash is 64 lowercase hex chars and expires_at >= issued_at.

urn:chio:error:weights:scope-not-subseterrorRequested capability scope set is not a subset of the model card's allowed_capability_set.

string code: CHIO-WEIGHTS-SCOPE-NOT-SUBSET
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-weights, chio-kernel, chio-cli

Bind under a card whose allowed_capability_set covers the requested scope, or narrow the request.

urn:chio:error:weights:tool-bannederrorRequested tool intersects the model card's banned_tools.

string code: CHIO-WEIGHTS-TOOL-BANNED
json-rpc: none
stability: unstable since 0.1.0
consumed by: chio-weights, chio-kernel, chio-cli

The card explicitly forbids the requested tool. Bind under a card that does not list the tool as banned, or remove the tool from the request.

Numeric wire codes

Each numeric code names one condition on the wire and the change that must happen before a retry. A transient code permits a new request; it never permits a second dispatch of an effect whose outcome is still unknown. Read the retry condition, then the retained result of the logical operation, and send an unresolved result through call recovery.

Registered codes

Code	Name and category	Wire mapping	Retry
1000	`protocol_version_unsupported` protocol	JSON-RPC: -32600 Native: none	`do_not_retry_until_version_change` · transient: false Retry only after selecting a supported protocol version.
1001	`session_not_initialized` protocol	JSON-RPC: -32002 Native: none	`reinitialize` · transient: false Open a new session and rerun initialize before retrying the operation.
1002	`invalid_request_shape` protocol	JSON-RPC: -32600 Native: none	`do_not_retry` · transient: false Correct the request shape before retrying.
1100	`auth_missing_or_invalid` auth	JSON-RPC: none Native: none	`retry_after_refresh` · transient: true Acquire valid credentials or refresh the token before retrying.
2100	`capability_denied` capability	JSON-RPC: none Native: capability_denied	`do_not_retry` · transient: false Do not retry the same capability without correcting signature, scope, or subject binding.
2101	`capability_expired` capability	JSON-RPC: none Native: capability_expired	`retry_after_reissue` · transient: false Issue or obtain a fresh capability before retrying.
2102	`capability_revoked` capability	JSON-RPC: none Native: capability_revoked	`retry_after_reissue` · transient: false Obtain a newly issued capability; the revoked capability must not be retried.
3100	`guard_denied` guard	JSON-RPC: none Native: policy_denied	`do_not_retry` · transient: false Adjust the request or policy inputs before retrying.
4100	`budget_exhausted` budget	JSON-RPC: none Native: none	`retry_after_budget_change` · transient: true Retry only after budget replenishment, grant widening, or billing reconciliation.
5100	`tool_server_error` tool	JSON-RPC: none Native: tool_server_error	`retry_with_backoff` · transient: true Use bounded exponential backoff unless upstream tooling documents a permanent failure.
6100	`internal_error` internal	JSON-RPC: none Native: internal_error	`retry_with_backoff` · transient: true Retry with bounded backoff and escalate if the condition persists.
7100	`transaction_passport_schema_unsupported` transaction	JSON-RPC: none Native: transaction_passport_schema_unsupported	`do_not_retry` · transient: false Regenerate the passport with a registered transaction passport schema.
7101	`transaction_passport_hash_mismatch` transaction	JSON-RPC: none Native: transaction_passport_hash_mismatch	`do_not_retry` · transient: false Rebuild the passport root with matching evidence graph, claim set, and policy digests.
7102	`transaction_graph_not_closed` transaction	JSON-RPC: none Native: transaction_graph_not_closed	`do_not_retry` · transient: false Include every required evidence, claim-set, policy, and receipt node in the transaction graph.
7103	`transaction_graph_cycle` transaction	JSON-RPC: none Native: transaction_graph_cycle	`do_not_retry` · transient: false Emit an acyclic evidence graph whose dependency edges can be topologically verified.
7104	`transaction_required_claim_missing` transaction	JSON-RPC: none Native: transaction_required_claim_missing	`do_not_retry` · transient: false Add verified evidence for the required claim or remove the unsupported requirement.
7105	`transaction_artifact_hash_mismatch` transaction	JSON-RPC: none Native: transaction_artifact_hash_mismatch	`do_not_retry` · transient: false Regenerate the artifact set with matching transaction evidence digests.
7106	`transaction_identity_not_bound` transaction	JSON-RPC: none Native: transaction_identity_not_bound	`do_not_retry` · transient: false Bind identity evidence to the transaction passport subject and evidence graph.
7107	`transaction_authorization_not_bound` transaction	JSON-RPC: none Native: transaction_authorization_not_bound	`do_not_retry` · transient: false Bind capability, policy, approval, or guard evidence to the governed transaction.
7108	`transaction_receipt_uncheckpointed` transaction	JSON-RPC: none Native: transaction_receipt_uncheckpointed	`do_not_retry` · transient: false Provide checkpointed receipt or inclusion evidence for the transaction receipt.
7109	`transaction_runtime_proof_rejected` transaction	JSON-RPC: none Native: transaction_runtime_proof_rejected	`do_not_retry` · transient: false Regenerate runtime security, parity, lease, nonce, revocation, sandbox, ack, and terminal receipt evidence.
7110	`transaction_buyer_review_rejected` transaction	JSON-RPC: none Native: transaction_buyer_review_rejected	`do_not_retry` · transient: false Regenerate buyer review evidence that matches the transaction passport and verifier policy.
7111	`transaction_settlement_unverified` transaction	JSON-RPC: none Native: transaction_settlement_unverified	`do_not_retry` · transient: false Include settlement evidence bound to the transaction order, amount, currency, rail, and receipt lineage.
7112	`transaction_dispute_unbound` transaction	JSON-RPC: none Native: transaction_dispute_unbound	`do_not_retry` · transient: false Bind dispute, refund, remediation, and settlement reversal evidence to the transaction passport and receipts.
7113	`transaction_transparency_preview_not_allowed` transaction	JSON-RPC: none Native: transaction_transparency_preview_not_allowed	`do_not_retry` · transient: false Provide verified transparency inclusion evidence or remove the transparency claim.

Next: diagnose from the symptom

Choose a diagnostic procedureDenied calls, stopped workers, missing receipts, peers, and command compatibility.Read the error contractHow the URN registry, the numeric registry, and the wire name one error.

PreviousSchemas & Errors NextSDK Overview