Schemas and Errors
Find a schema file, trace a numeric code or error URN to the wire, and check which versioning rules bind an integration.
On this page
Independently built kernels, SDKs, and verifiers agree through two kinds of registry: schema ids that fix the shape of every signed record, and error codes that name why an operation stopped.
A schema fixes a record's shape; the receiving implementation still applies its own authority and signature checks. With a returned code in hand, go straight to Error Lookup; with only a symptom, start from Troubleshooting.
Registries
Three registries and one manifest pin the bundle. Each file carries its own schema id, version, and entry count.
| File | Schema id and version | Entries | What it names |
|---|---|---|---|
spec/ | chio.bundle 1.0.0 | 382 of 449 schema files | Every signed artifact schema id a verifier accepts, under https://chio-. |
spec/ | chio.updated 2026-06-19 | 25 codes | The numeric wire codes by category, with a JSON-RPC code or native wire name where one exists. |
spec/ | chio.0.1.0, updated 2026-07-14 | 111 codes in 20 domains | Every error URN, urn:chio:error:<domain>:<code>, with severity, remediation, and consumers. |
spec/ | SHA-256 manifestbundle 1.0.0 | 452 entries | A digest of each schema file and of VERSION. |
Schema files
Every JSON Schema in the bundle is draft 2020-12. spec/schemas/registry.json is the verifier-facing list of signed artifact schema ids: load-time and verify-time code rejects a signed artifact whose schema string it does not list. A file the registry leaves out still ships in the bundle, and the explorer marks it unregistered.
| File | Title | Registry ID | Version |
|---|---|---|---|
chio-agent-web/ | Chio Agent Web External Projection Manifest | chio. | v1 |
chio-agent-web/ | Chio Agent Web Interop Verifier Report | chio. | v1 |
chio-agent-web/ | Chio Agent Web Proof Envelope | chio. | v1 |
chio-agent-web/ | Chio Agent Web Proof Envelope v2 | chio. | v2 |
chio-attest/ | Chio Buyer Attestation Explanation | chio. | v1 |
chio-attest/ | Chio Buyer Attestation Packet | chio. | v1 |
chio-attest/ | Chio Buyer Attestation Review Package | chio. | v1 |
chio-attest/ | Chio Buyer Attestation Review Report | chio. | v1 |
chio-attest/ | Chio Buyer Attestation Verification Report | chio. | v1 |
chio-attest/ | Chio Attest Buyer Proof Negative Fixture Corpus | chio. | v1 |
chio-attest/ | Chio Attest Proof Package | chio. | v1 |
chio-attest/ | Chio Attest Selective Disclosure Proof | chio. | v1 |
chio-attest/ | Chio Attest Verifier Report | chio. | v1 |
chio-attest/ | Chio Attest Workflow Intersection | chio. | v1 |
chio-commerce/ | Chio Commerce Event Log | chio. | v1 |
chio-commerce/ | Chio Commerce Federation Trust Bundle | chio. | v1 |
chio-commerce/ | Chio Commerce Mandate Allowance Ledger | chio. | v1 |
chio-commerce/ | Chio Commerce Order Context | chio. | v1 |
chio-commerce/ | Chio Commerce Order Passport | chio. | v1 |
chio-commerce/ | Chio Commerce Payment Lifecycle | chio. | v1 |
chio-commerce/ | Chio Commerce Protocol Payload | chio. | v1 |
chio-commerce/ | Chio Provider Discovery Snapshot | chio. | v1 |
chio-commerce/ | Chio Commerce Provider Passport | chio. | v1 |
chio-commerce/ | Chio Provider Selection Report | chio. | v1 |
chio-commerce/ | Chio Commerce Reputation Snapshot | chio. | v1 |
chio-commerce/ | Chio Commerce Settlement Packet | chio. | v1 |
chio-commerce/ | Chio SLA Commitment | chio. | v1 |
chio-commerce/ | Chio SLA Performance Report | chio. | v1 |
chio- | Chio Comptroller Surface Report | chio. | v1 |
chio-crypto/ | Chio Crypto Verification Context | chio. | v1 |
chio-disclosure/ | Chio BBS Projection Manifest | chio. | v1 |
chio-disclosure/ | Chio Disclosure Capsule | chio. | v1 |
chio-disclosure/ | Chio Disclosure Crypto Context Report | chio. | v1 |
chio-disclosure/ | Chio Disclosure Leakage Ledger | chio. | v1 |
chio-disclosure/ | Chio Disclosure Lineage Verifier Report | chio. | v1 |
chio-disclosure/ | Chio Disclosure Verifier Privacy Profile | chio. | v1 |
chio-economy/ | Chio Economic State Anchor View V1 | chio. | — |
chio-economy/ | Chio Channel Close V1 | chio. | — |
chio-economy/ | Chio Channel Dispute V1 | chio. | — |
chio-economy/ | Chio Channel Funding Acknowledgement V1 | chio. | — |
Read family inventories, individual files, and manifest coverage
Families
The families by file count, largest first. Agents and sidecars parse chio-wire/v1/ and chio-http/v1/ directly; every family is tabled file by file below.
| Family | Files | Registered | Versions | Contents |
|---|---|---|---|---|
chio-pheromone | 85 | 85 | v1 | Signal deposits, concentrations, and gossip batches, with the relay alert-assurance records and negative fixture corpora. |
chio-wire | 55 | 13 | v1 | The native framed transport, specified on Wire protocol. |
chio-economy | 47 | 47 | none | Payment channels, clearing rounds, obligation atoms, credit facilities, and factor assignments for the settlement layer. |
chio-runtime | 45 | 45 | v1 | Runtime admission, orchestration, and lease records, with the evidence manifests, proof-parity reports, and terminal receipts a run produces. |
chio-finding | 37 | 37 | v1 | The cognition- |
chio-federation | 22 | 22 | v1 | Treaty scope, capability leases, issuance bundles and requests, peer pins, revocation checkpoints, and receipt-lineage statements. |
chio-trust | 17 | 17 | v1 | Trust roots, key state, revocation and scorecard snapshots, and the financial agent passport with the credential sources behind it. |
chio-http | 15 | 0 | v1 | The hosted HTTP interface, described on the HTTP transport page. |
chio-commerce | 14 | 14 | v1 | Order and provider passports, provider discovery and selection, payment lifecycle, settlement packets, and SLA commitments. |
chio-outcome | 11 | 9 | v1 | Verified- |
chio-proof-room | 11 | 11 | v1 | Bundle manifests, fixture catalogs, first-run capability and guard evidence, receipt evidence, and the proof-room verifier report. |
chio- | 11 | 11 | v1 | The Transaction Passport and the objects it binds: evidence graph, claim set, capability proof, guard decision, policy bundle, request and response digests, and the verifier policy and report. |
chio-attest | 10 | 10 | v1 | Buyer attestation packets, their review and verification reports, selective- |
chio-web3 | 10 | 10 | v1, v2 | Anchor inclusion proofs and proof bundles, settlement dispatch and execution receipts, and the public- |
chio-fiscal | 9 | 8 | v1 | The fiscal charter and genesis policy, proposals and their admission, approvals, schedules, activation, and continuity checkpoints. |
chio-swarm | 9 | 9 | v1 | The swarm authority bundle, specified on Swarm Protocol. |
chio-disclosure | 6 | 6 | v1 | BBS projection manifests, disclosure capsules, leakage ledgers, lineage verifier reports, and verifier privacy profiles. |
chio-enterprise | 5 | 5 | v1 | Approval cases, control- |
chio-agent-web | 4 | 4 | v1, v2 | External projection manifests, interop verifier reports, and the agent-web proof envelope in two versions. |
chio-frost | 4 | 4 | v1 | FROST threshold- |
chio-parametric | 4 | 1 | v1 | Parametric policy, trigger instance keys, an evidence-corpus manifest, and the shared definitions the three reference. |
chio-risk | 4 | 4 | v1 | Collateral position and risk- |
chio-econsim | 2 | 2 | v1 | The economic- |
chio- | 2 | 2 | v1, v2 | The transparency inclusion proof, v1 and the checkpoint- |
chio-workflow | 2 | 2 | v1 | The workflow preflight plan and the report a preflight run writes. |
root | 2 | 0 | v1 | Shared definition documents at the root of the tree: financial credential definitions and fiscal definitions. |
chio- | 1 | 1 | v1 | The comptroller surface report. |
chio-crypto | 1 | 1 | v1 | The verification context a crypto check carries. |
chio-lineage | 1 | 1 | v1 | The signed lineage subgraph. |
chio-oracle | 1 | 1 | v1 | The conversion evidence a currency oracle emits. |
chio- | 1 | 0 | none | The report shape chio replay --json emits. |
policy | 1 | 0 | none | The policy analysis report. |
chio-wire/v1
The native transport tree, one subdirectory per message family. The Rust types live under crates/core/chio-core-types/src/, and the capability and receipt subtrees are validated against every case in tests/bindings/vectors/.
Across the trust-control subtree, lease, heartbeat, and terminate use camelCase member names (leaseId, leaseEpoch, leaderUrl), so the lease projection, its refresh request, and its termination request stay consistent on the wire.
chio-wire/v1/agent/
| File | Title | Registry id |
|---|---|---|
active- | Chio Governed Active Response Intent Body | unregistered |
governed- | Chio Governed Transaction Intent | unregistered |
heartbeat. | Chio AgentMessage heartbeat | unregistered |
list_ | Chio AgentMessage list_ | unregistered |
tool_ | Chio AgentMessage tool_ | unregistered |
chio-wire/v1/anchor/
| File | Title | Registry id |
|---|---|---|
batch. | Chio anchor batch v1 | chio. |
chio-wire/v1/capability/
| File | Title | Registry id |
|---|---|---|
aggregate- | Chio Aggregate Budget Root Binding | chio. |
aggregate- | Chio Aggregate Invocation Budget | unregistered |
capabilities. | Chio capability negotiation v1 | chio. |
cumulative- | Chio Cumulative Approval Root Binding | chio. |
governed- | Chio Governed Approval Token | unregistered |
grant. | Chio Capability Grant | unregistered |
revocation. | Chio Capability Revocation Entry | unregistered |
supplemental- | Chio Opaque Supplemental Authorization | unregistered |
threshold- | Chio Threshold Approval Proposal | chio. |
token. | Chio CapabilityToken | chio. |
verified- | Chio Verified Approval Set Body | unregistered |
chio-wire/v1/error/
| File | Title | Registry id |
|---|---|---|
capability_ | Chio ToolCallError capability_ | unregistered |
capability_ | Chio ToolCallError capability_ | unregistered |
capability_ | Chio ToolCallError capability_ | unregistered |
internal_ | Chio ToolCallError internal_error | unregistered |
policy_ | Chio ToolCallError policy_denied | unregistered |
tool_ | Chio ToolCallError tool_ | unregistered |
chio-wire/v1/federation/
| File | Title | Registry id |
|---|---|---|
bilateral- | Chio bilateral DSSE signature-slice envelope | chio. |
bilateral- | Chio bilateral DSSE signature-slice statement | unregistered |
chio-wire/v1/jsonrpc/
| File | Title | Registry id |
|---|---|---|
notification. | Chio JSON-RPC 2.0 Notification | unregistered |
request. | Chio JSON-RPC 2.0 Request | unregistered |
response. | Chio JSON-RPC 2.0 Response | unregistered |
chio-wire/v1/kernel/
| File | Title | Registry id |
|---|---|---|
capability_ | Chio KernelMessage capability_list | unregistered |
capability_ | Chio KernelMessage capability_ | unregistered |
combined- | Chio Combined Admission Capture Metadata | unregistered |
execution_ | Chio signed execution nonce | unregistered |
heartbeat. | Chio KernelMessage heartbeat | unregistered |
tool_ | Chio KernelMessage tool_call_chunk | unregistered |
tool_ | Chio KernelMessage tool_ | unregistered |
chio-wire/v1/provenance/
| File | Title | Registry id |
|---|---|---|
attestation- | Chio Provenance Attestation Bundle | unregistered |
context. | Chio Provenance Call-Chain Context | unregistered |
stamp. | Chio Provenance Stamp | unregistered |
verdict- | Chio Provenance Verdict Link | unregistered |
chio-wire/v1/receipt/
| File | Title | Registry id |
|---|---|---|
admission- | Chio Durable Admission Receipt Metadata | chio. |
delivery- | Chio Delivery Contract Receipt Metadata | chio. |
finding- | Chio Finding Delivery Receipt Metadata | chio. |
inclusion- | Chio Receipt Merkle Inclusion Proof | unregistered |
lineage_ | Chio receipt lineage statement | chio. |
record. | Chio Receipt Record | chio.receipt.v1 |
chio-wire/v1/result/
| File | Title | Registry id |
|---|---|---|
cancelled. | Chio ToolCallResult cancelled | unregistered |
err.schema.json | Chio ToolCallResult err | unregistered |
incomplete. | Chio ToolCallResult incomplete | unregistered |
ok.schema.json | Chio ToolCallResult ok | unregistered |
stream_ | Chio ToolCallResult stream_complete | unregistered |
chio-wire/v1/trust-control/
| File | Title | Registry id |
|---|---|---|
attestation. | Chio Trust-Control Runtime Attestation Evidence | unregistered |
budget- | Budget Snapshot Anchor Provenance | chio. |
heartbeat. | Chio Trust-Control Lease Heartbeat | unregistered |
lease. | Chio Trust-Control Authority Lease | unregistered |
terminate. | Chio Trust-Control Lease Termination | unregistered |
chio-http/v1
The hosted HTTP interface, including the hosted finding-market request and event envelopes.
| File | Title | Registry id |
|---|---|---|
caller- | Chio CallerIdentity | unregistered |
chio- | Chio HTTP Request | unregistered |
error- | Chio HTTP Error Envelope | unregistered |
evaluate- | Chio Evaluate Request | unregistered |
evaluate- | Chio Evaluate Response | unregistered |
finding- | Chio Hosted Finding Domain Event Envelope | unregistered |
finding- | Chio Hosted Finding Error | unregistered |
finding- | Chio Hosted Finding Mutation Response | unregistered |
finding- | Chio Hosted Finding Authenticated Request Context | unregistered |
finding- | Chio Hosted Finding Tenant Binding | unregistered |
http- | Chio HTTP Receipt | unregistered |
session- | Chio HTTP Session Init | unregistered |
session- | Chio HTTP Session Resume | unregistered |
stream- | Chio HTTP Stream Frame | unregistered |
verdict. | Chio HTTP Verdict | unregistered |
Top-level schemas
The shared definition schemas at the root of spec/schemas/, which other families reference instead of carrying their own copy.
| File | Title | Registry id |
|---|---|---|
financial- | financial- | unregistered |
fiscal- | fiscal- | unregistered |
Four more root documents use the .v1.json suffix and sit outside the schema tables above.
signature.v1.json: algorithm-aware public-key and signature string encodings that signed artifacts reference.model-card.v1.json: a signed declaration binding a model's loaded weights to an allowed capability set, banned tools, and training-data class.receipt-provenance-v1.json: the receipt-provenance record shape.chio-tee-frame-v1.json: the capture frame the chio-tee shadow runner writes per kernel evaluation.
The other families
Each remaining family by file count, largest first, with every file it holds.
chio-pheromone/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Pheromone Batch | chio. |
v1/ | Chio Pheromone Catch-up Request | chio. |
v1/ | Chio Pheromone Catch-up Response | chio. |
v1/ | Chio Pheromone Concentration | chio. |
v1/ | Chio Pheromone Cost Commitment | chio. |
v1/ | Chio Pheromone Deposit | chio. |
v1/ | Chio Pheromone Deposit Gossip | chio. |
v1/ | Chio Pheromone Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Observation Cost Leaf | chio. |
v1/ | Chio Pheromone Observation Cost Statement | chio. |
v1/ | Chio Pheromone Observation Cost Telemetry Root | chio. |
v1/ | Chio Pheromone Observation Cost Verifier Root | chio. |
v1/ | Chio Pheromone Peer Directory Bundle | chio. |
v1/ | Chio Pheromone Peer Directory Rotation Report | chio. |
v1/ | Chio Pheromone Peer Directory State | chio. |
v1/ | Chio Pheromone Peer Directory | chio. |
v1/ | Chio Pheromone Peer Weights | chio. |
v1/ | Chio Pheromone Query Report | chio. |
v1/ | Chio Pheromone Receive Report | chio. |
v1/ | Chio Pheromone Relay Alert Acknowledgement Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Extraction Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Package Manifest | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Package Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Package Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Profile | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Restore Drill Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Restore Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Archive Restore Profile | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Closeout Profile | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Closeout Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Export Manifest | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Export Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Export Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance External Retention Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Assurance External Retention Profile | chio. |
v1/ | Chio Pheromone Relay Alert Assurance External Retention Review Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Package | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Physical Archive Drill Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Physical Archive Evidence | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Recovery Drill Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Replay Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Retention Handoff Evidence | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Retention Handoff Profile | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Retention Handoff Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Retention Profile | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Retention Report | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Trusted Archive Packagers | chio. |
v1/ | Chio Pheromone Relay Alert Assurance Trusted Exporters | chio. |
v1/ | Chio Pheromone Relay Alert Delivery Drift Report | chio. |
v1/ | Chio Pheromone Relay Alert Delivery Evidence | chio. |
v1/ | Chio Pheromone Relay Alert Delivery Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Delivery Profile | chio. |
v1/ | Chio Pheromone Relay Alert Delivery Report | chio. |
v1/ | Chio Pheromone Relay Alert Drill Report | chio. |
v1/ | Chio Pheromone Relay Alert Handoff Drift Report | chio. |
v1/ | Chio Pheromone Relay Alert Handoff Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Handoff Profile | chio. |
v1/ | Chio Pheromone Relay Alert Handoff Report | chio. |
v1/ | Chio Pheromone Relay Alert Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Alert Normalization Profile | chio. |
v1/ | Chio Pheromone Relay Alert Normalization Report | chio. |
v1/ | Chio Pheromone Relay Alert Report | chio. |
v1/ | Chio Pheromone Relay Alert Route Owner Profile | chio. |
v1/ | Chio Pheromone Relay Alert Route Review Packet | chio. |
v1/ | Chio Pheromone Relay Alert Routing Profile | chio. |
v1/ | Chio Pheromone Relay Alert Suppression State | chio. |
v1/ | Chio Pheromone Relay Config | chio. |
v1/ | Chio Pheromone Relay Drill Report | chio. |
v1/ | Chio Pheromone Relay Event Report | chio. |
v1/ | Chio Pheromone Relay Health Report | chio. |
v1/ | Chio Pheromone Relay HTTP Request | chio. |
v1/ | Chio Pheromone Relay Metrics Snapshot | chio. |
v1/ | Chio Pheromone Relay Negative Fixture Corpus | chio. |
v1/ | Chio Pheromone Relay Observability Report | chio. |
v1/ | Chio Pheromone Relay Operator Report | chio. |
v1/ | Chio Pheromone Relay Supervisor Profile | chio. |
v1/ | Chio Pheromone Relay Tick Report | chio. |
v1/ | Chio Pheromone Relay Trend Report | chio. |
v1/ | Chio Pheromone Scarcity Policy | chio. |
v1/ | Chio Pheromone Scarcity Window Id Preimage | chio. |
v1/ | Chio Pheromone Runtime Transit Policy Envelope | chio. |
v1/ | Chio Pheromone Workflow Context | chio. |
chio-economy/
| File | Title | Registry id |
|---|---|---|
anchor- | Chio Economic State Anchor View V1 | chio. |
channel- | Chio Channel Close V1 | chio. |
channel- | Chio Channel Dispute V1 | chio. |
channel- | Chio Channel Funding Acknowledgement V1 | chio. |
channel- | Chio Channel Funding Evidence V1 | chio. |
channel- | Chio Channel Open Intent V1 | chio. |
channel- | Chio Channel Open V1 | chio. |
channel- | Chio Channel Release Authorization V1 | chio. |
channel- | Chio Channel Reservation V1 | chio. |
channel- | Chio Channel State V1 | chio. |
channel- | Chio Channel Terminal Outcome Commitment V1 | chio. |
channel- | Chio Channel Transition Replay Descriptor V1 | chio. |
clearing- | Chio Clearing Atom Transformation V1 | chio. |
clearing- | Chio Clearing Input Manifest V1 | chio. |
clearing- | Chio Clearing Netting Round Core V1 | chio. |
clearing- | Chio Clearing Output Manifest V1 | chio. |
clearing- | Chio Clearing Participant Acceptance V1 | chio. |
clearing- | Chio Clearing Participant Snapshot Acknowledgement V1 | chio. |
clearing- | Chio Clearing Participant Snapshot V1 | chio. |
clearing- | Chio Clearing Participant Statement V1 | chio. |
clearing- | Chio Clearing Round Abort V1 | chio. |
clearing- | Chio Clearing Round Finalization V1 | chio. |
clearing- | Chio Clearing Round Lifecycle V1 | chio. |
clearing- | Chio Clearing Round Satisfaction V1 | chio. |
clearing- | Chio Clearing Round Transition Proof V1 | chio. |
clearing- | Chio Clearing Settlement Intent V1 | chio. |
clearing- | Chio Clearing Settlement Reconciliation V1 | chio. |
clearing- | Chio Clearing Zero Dispatch Proof V1 | chio. |
clearing- | Chio Clearing Zero Intent Reconciliation V1 | chio. |
credit- | Signed Chio Credit Facility Bind V1 | chio. |
effect- | Chio Economic Effect Dispatch Commit V1 | chio. |
effect- | Chio Economic Effect Slot V1 | chio. |
factor- | Signed Chio Factor Assignment Acknowledgement V1 | chio. |
factor- | Signed Chio Factor Assignment Agreement V1 | chio. |
factor- | Signed Chio Factor Assignment Bind Authorization V1 | chio. |
factor- | Signed Chio Factor Assignment Not Applied V1 | chio. |
factor- | Chio Assignment Offer V1 | chio. |
factor- | Chio Discount Quote V1 | chio. |
factor- | Chio Normalized Assignment Request V1 | chio. |
factor- | Chio Receivable Claim V1 | chio. |
obligation- | Chio Obligation Atom V1 | chio. |
obligation- | Chio Obligation Disposition V1 | chio. |
obligation- | Chio Obligation Settlement Lifecycle V1 | chio. |
obligation- | Signed Chio Obligation Status Proof V1 | chio. |
receivable- | Signed Chio Credit IOU Envelope V2 | chio. |
resource- | Chio Economic Resource Head V1 | chio. |
state- | Chio Economic State Batch V1 | chio. |
chio-runtime/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Runtime Admission Bundle | chio. |
v1/ | Chio Runtime Admission Profile | chio. |
v1/ | Chio Runtime Admission Report | chio. |
v1/ | Chio Runtime Admission Store | chio. |
v1/ | Chio Runtime Artifact Retention Plan | chio. |
v1/ | Chio Runtime Artifact Retention Profile | chio. |
v1/ | Chio Runtime Attack Simulation Report | chio. |
v1/ | Chio Runtime Chaos Run Report | chio. |
v1/ | Chio Runtime Evidence Manifest | chio. |
v1/ | Chio Runtime Evidence Sink Health Report | chio. |
v1/ | Chio Runtime Execution Lease | chio. |
v1/ | Chio Runtime Failure Code Registry | chio. |
v1/ | Chio Runtime Ops Negative Fixture Corpus | chio. |
v1/ | Chio Runtime Ops Status Report | chio. |
v1/ | Chio Runtime Orchestration Negative Fixture Corpus | chio. |
v1/ | Chio Runtime Orchestration Plan | chio. |
v1/ | Chio Runtime Orchestration Profile | chio. |
v1/ | Chio Runtime Orchestration Resume Plan | chio. |
v1/ | Chio Runtime Orchestration Run Report | chio. |
v1/ | Chio Runtime Orchestration Status Report | chio. |
v1/ | Chio Runtime Peer Weights | chio. |
v1/ | Chio Runtime Pheromone Policy Decision | chio. |
v1/ | Chio Runtime Pheromone Policy | chio. |
v1/ | Chio Policy Activation Receipt | chio. |
v1/ | Chio Runtime Proof Drift Report | chio. |
v1/ | Chio Runtime Proof Parity Report | chio. |
v1/ | Chio Runtime Proof Regeneration Input | chio. |
v1/ | Chio Runtime Proof Regeneration Report | chio. |
v1/ | Chio Runtime Provider Bindings | chio. |
v1/ | Chio Runtime Provider Health Report | chio. |
v1/ | Chio Runtime Recovery Drill Report | chio. |
v1/ | Chio Runtime Revocation Freshness Proof | chio. |
v1/ | Chio Runtime Run Contract | chio. |
v1/ | Chio Runtime Run Lease | chio. |
v1/ | Chio Runtime Sandbox Attestation | chio. |
v1/ | Chio Runtime Scheduler Tick Report | chio. |
v1/ | Chio Runtime Step Evidence | chio. |
v1/ | Chio Runtime Supervisor Profile | chio. |
v1/ | Chio Runtime Terminal Receipt | chio. |
v1/ | Chio Runtime Tool Server Acknowledgement | chio. |
v1/ | Chio Runtime Trust Floor State | chio. |
v1/ | Chio Runtime Trusted Time Proof | chio. |
v1/ | Chio Runtime Trusted Verifiers | chio. |
v1/ | Chio Runtime Verifier Trust Bundle | chio. |
v1/ | Chio Runtime Workflow Run Report | chio. |
chio-finding/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Finding Admission | chio. |
v1/ | Chio Finding Audit Epoch (signed envelope) | chio. |
v1/ | Chio Finding Audit Report (signed envelope) | chio. |
v1/ | Chio Finding Audit Round Authorization (signed envelope) | chio. |
v1/ | Chio Finding Authority Status (signed envelope) | chio. |
v1/ | Chio Finding Bond Backing | chio. |
v1/ | Chio Finding Bond Observation Request V1 | chio. |
v1/ | Chio Finding Bond Observation Response V1 | chio. |
v1/ | Chio Finding Challenge Enforcement (signed envelope) | chio. |
v1/ | Chio Finding Challenge Outcome (signed envelope) | chio. |
v1/ | Chio Finding Challenge- | chio. |
v1/ | Chio Finding Challenge (signed envelope) | chio. |
v1/ | Chio Finding Claim Allocation | chio. |
v1/ | Chio Finding Failed Delivery (signed envelope) | chio. |
v1/ | Chio Finding Finalized Bond Snapshot (signed envelope) | chio. |
v1/ | Chio Finding | chio.finding.v1 |
v1/ | Chio Hosted Authenticated Finding Delivery | chio. |
v1/ | Chio Hosted Finding Market Qualification | chio. |
v1/ | Chio Finding Impairment Publisher Request V1 | chio. |
v1/ | Chio Finding Impairment Publisher Response V1 | chio. |
v1/ | Chio Finding Key Revocation (signed envelope) | chio. |
v1/ | Chio Finding Liability | chio. |
v1/ | Chio Open Market Penalty (signed envelope) | chio. |
v1/ | Chio Finding Market Terms | chio. |
v1/ | Chio Finding Pool Allocation | chio. |
v1/ | Chio Finding Purchase Context (unsigned) | chio. |
v1/ | Chio Finding Purchase Record (signed envelope) | chio. |
v1/ | Chio Finding Purchase Result | chio. |
v1/ | Chio Finding Recovery Context (unsigned) | chio. |
v1/ | Chio Finding Replay Observation (unsigned) | chio. |
v1/ | Chio Finding Replay Recipe Input (unsigned) | chio. |
v1/ | Chio Finding Seller Authorization (signed envelope) | chio. |
v1/ | Chio Finding Status Epoch (signed envelope) | chio. |
v1/ | Chio Finding Portable Status Proof Input | chio. |
v1/ | Chio Finding Verified Fix Submission | chio. |
v1/ | Chio Finding Verifier Report | chio. |
v1/ | Chio Finding Voluntary Retraction | chio. |
chio-federation/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Federation Authority Profile | chio. |
v1/ | Chio Federation Bilateral Invocation | chio. |
v1/ | Signed Chio Capability Lease | chio. |
v1/ | Chio Federation Cross-Boundary Admission Report | chio. |
v1/ | Chio Federation Cross-Kernel Continuation | chio. |
v1/ | Chio Federation Governance Ladder Manifest | chio. |
v1/ | Signed Chio Governance Receipt | chio. |
v1/ | Chio Federation Issuance Bundle | chio. |
v1/ | Chio Federation Issuance Request | chio. |
v1/ | Chio Federation Ladder Intersection | chio. |
v1/ | Chio Federation Lease Scope Binding | chio. |
v1/ | Chio Federation Local Signing Keys | chio. |
v1/ | Chio Federation Peer Pins | chio. |
v1/ | Chio Federation Receipt Lineage Bundle | chio. |
v1/ | Chio Federation Receipt Lineage Statement | chio. |
v1/ | Chio Federation Revocation Checkpoint | chio. |
v1/ | Chio Federation Revocation Publication Request | chio. |
v1/ | Chio Federation Treaty Negative Fixture Corpus | chio. |
v1/ | Chio Federation Treaty Runtime Negative Fixture Corpus | chio. |
v1/ | Chio Federation Treaty Scope | chio. |
v1/ | Chio Federation Verification Context | chio. |
v1/ | Chio Federation Verifier Trust Bundle | chio. |
chio-trust/
| File | Title | Registry id |
|---|---|---|
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | financial- | chio. |
v1/ | Chio Trust Key State | chio. |
v1/ | presented- | chio. |
v1/ | Chio Reputation Import Report | chio. |
v1/ | Chio Trust Revocation Snapshot | chio. |
v1/ | Chio Trust Scorecard Snapshot | chio. |
v1/ | Chio Trust Root | chio. |
chio-commerce/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Commerce Event Log | chio. |
v1/ | Chio Commerce Federation Trust Bundle | chio. |
v1/ | Chio Commerce Mandate Allowance Ledger | chio. |
v1/ | Chio Commerce Order Context | chio. |
v1/ | Chio Commerce Order Passport | chio. |
v1/ | Chio Commerce Payment Lifecycle | chio. |
v1/ | Chio Commerce Protocol Payload | chio. |
v1/ | Chio Provider Discovery Snapshot | chio. |
v1/ | Chio Commerce Provider Passport | chio. |
v1/ | Chio Provider Selection Report | chio. |
v1/ | Chio Commerce Reputation Snapshot | chio. |
v1/ | Chio Commerce Settlement Packet | chio. |
v1/ | Chio SLA Commitment | chio. |
v1/ | Chio SLA Performance Report | chio. |
chio-outcome/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Outcome Contractual Zero V1 | chio. |
v1/ | Chio Outcome Delivery Acknowledgement V1 | chio. |
v1/ | Chio Outcome Delivery Checkpoint V1 | chio. |
v1/ | Chio Outcome Delivery Nonacceptance V1 | chio. |
v1/ | Chio Outcome Eligibility V1 | chio. |
v1/ | Chio Outcome Output Provenance V1 | chio. |
v1/ | Chio Outcome Predicate V1 | chio. |
v1/ | Chio Outcome Pricing V1 | chio. |
v1/ | Chio Verified Outcome Request V1 | unregistered |
v1/ | Chio Outcome SLA V1 | chio. |
v1/ | Chio Outcome Verdict V1 | unregistered |
chio-proof-room/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Proof Room Bundle Manifest | chio. |
v1/ | Chio Proof Room Docker Quickstart Evidence | chio. |
v1/ | Chio Proof Room First Run Capability Proof | chio. |
v1/ | Chio Proof Room First Run Command Log | chio. |
v1/ | Chio Proof Room First Run Guard Report | chio. |
v1/ | Chio Proof Room First Run Trust Roots | chio. |
v1/ | Chio Proof Room Fixture Catalog | chio. |
v1/ | Chio Proof Room Fixture Root Catalog | chio. |
v1/ | Chio Proof Room Receipt Evidence | chio. |
v1/ | Chio Proof Room Release Truth | chio. |
v1/ | Chio Proof Room Verifier Report | chio. |
chio-transaction/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Capability Proof | chio. |
v1/ | Chio Transaction Claim Set | chio. |
v1/ | Chio Transaction Evidence Graph | chio. |
v1/ | Chio Guard Decision | chio. |
v1/ | Chio Policy Bundle | chio. |
v1/ | Chio Request Digest | chio. |
v1/ | Chio Response Digest | chio. |
v1/ | Chio Transaction Runtime Security Report | chio. |
v1/ | Chio Transaction Passport | chio. |
v1/ | Chio Transaction Verifier Policy | chio. |
v1/ | Chio Transaction Verifier Report | chio. |
chio-attest/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Buyer Attestation Explanation | chio. |
v1/ | Chio Buyer Attestation Packet | chio. |
v1/ | Chio Buyer Attestation Review Package | chio. |
v1/ | Chio Buyer Attestation Review Report | chio. |
v1/ | Chio Buyer Attestation Verification Report | chio. |
v1/ | Chio Attest Buyer Proof Negative Fixture Corpus | chio. |
v1/ | Chio Attest Proof Package | chio. |
v1/ | Chio Attest Selective Disclosure Proof | chio. |
v1/ | Chio Attest Verifier Report | chio. |
v1/ | Chio Attest Workflow Intersection | chio. |
chio-web3/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Anchor Inclusion Proof | chio. |
v1/ | Chio Anchor Proof Bundle | chio. |
v1/ | Chio Public Settlement Verifier Report | chio. |
v1/ | Chio Web3 Settlement Dispatch | chio. |
v1/ | Chio Web3 Settlement Execution Receipt | chio. |
v1/ | Chio Web3 Settlement Proof Bundle | chio. |
v2/ | Chio V2 Anchor Inclusion Proof | chio. |
v2/ | Chio V2 Anchor Proof Bundle | chio. |
v2/ | Chio Web3 Settlement Dispatch | chio. |
v2/ | Chio Web3 Settlement Execution Receipt | chio. |
chio-fiscal/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Fiscal Activation | chio. |
v1/ | Chio Fiscal Approval | chio. |
v1/ | Chio Fiscal Charter | chio. |
v1/ | Chio Fiscal Consumer Readiness | chio. |
v1/ | Chio Fiscal Continuity Checkpoint | chio. |
v1/ | Chio Fiscal Genesis Policy | unregistered |
v1/ | Chio Fiscal Proposal Admission | chio. |
v1/ | Chio Fiscal Proposal | chio. |
v1/ | Chio Fiscal Schedule | chio. |
chio-swarm/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Swarm Authority Verifier Report | chio. |
v1/ | Chio Swarm Budget Pool | chio. |
v1/ | Chio Swarm Continuation Token | chio. |
v1/ | Chio Swarm Delegation Witness Chain | chio. |
v1/ | Chio Swarm Join Receipt | chio. |
v1/ | Chio Swarm Revocation Epoch | chio. |
v1/ | Chio Swarm Route Plan Receipt | chio. |
v1/ | Chio Swarm Task Graph | chio. |
v1/ | Chio Swarm Terminal Graph Receipt | chio. |
chio-disclosure/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio BBS Projection Manifest | chio. |
v1/ | Chio Disclosure Capsule | chio. |
v1/ | Chio Disclosure Crypto Context Report | chio. |
v1/ | Chio Disclosure Leakage Ledger | chio. |
v1/ | Chio Disclosure Lineage Verifier Report | chio. |
v1/ | Chio Disclosure Verifier Privacy Profile | chio. |
chio-enterprise/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Enterprise Approval Case | chio. |
v1/ | Chio Enterprise Control Evidence Map | chio. |
v1/ | Chio Enterprise Data Governance Report | chio. |
v1/ | Chio Enterprise Evidence Export Bundle | chio. |
v1/ | Chio Enterprise Telemetry Projection | chio. |
chio-agent-web/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Agent Web External Projection Manifest | chio. |
v1/ | Chio Agent Web Interop Verifier Report | chio. |
v1/ | Chio Agent Web Proof Envelope | chio. |
v2/ | Chio Agent Web Proof Envelope v2 | chio. |
chio-frost/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio FROST Authorization Slot Checkpoint | chio. |
v1/ | Chio FROST Authorization | chio. |
v1/ | Chio FROST Epoch Checkpoint | chio. |
v1/ | Chio FROST Roster | chio. |
chio-parametric/
| File | Title | Registry id |
|---|---|---|
v1/ | defs. | unregistered |
v1/ | Chio Parametric Evidence Corpus Manifest V1 | unregistered |
v1/ | Chio Parametric Policy V1 | chio. |
v1/ | Chio Parametric Trigger Instance Key V1 | unregistered |
chio-risk/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Adjudication Jurisdiction Receipt | chio. |
v1/ | Chio Collateral Position Report | chio. |
v1/ | Chio Risk Comptroller Report | chio. |
v1/ | Chio Guarantee Decision | chio. |
chio-econsim/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio economic simulation qualification matrix v1 | chio. |
v1/ | Chio economic simulation scenario result v1 | chio. |
chio-transparency/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Transparency Inclusion Proof | chio. |
v2/ | Chio Checkpoint- | chio. |
chio-workflow/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Workflow Preflight Plan v1 | chio. |
v1/ | Chio Workflow Preflight Report v1 | chio. |
chio-comptroller/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Comptroller Surface Report | chio. |
chio-crypto/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Crypto Verification Context | chio. |
chio-lineage/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Signed Lineage Subgraph | chio. |
chio-oracle/
| File | Title | Registry id |
|---|---|---|
v1/ | Chio Oracle Conversion Evidence | chio. |
chio-replay-report/
| File | Title | Registry id |
|---|---|---|
v1.schema.json | chio- | unregistered |
policy/
| File | Title | Registry id |
|---|---|---|
analysis- | Chio Policy Analysis Report | unregistered |
Manifest and coverage
spec/schemas/MANIFEST.sha256: a SHA-256 over each schema file and overVERSION. A change that adds or edits a schema updates this manifest in the same commit.spec/schemas/COVERAGE.md: a coverage map of the shipped families, updated whenever a schema is added, removed, or renamed. It points at the normative wire spec, the artifact registry, the manifest, and the version file.spec/schemas/VERSION: the bundle version, listed in the registries table.
Error registries
Two registries name an error. The URN registry in spec/errors/registry.yaml is the granular one. A URN entry that maps to a numeric code carries it as jsonrpc_code, and 25 of the 111 URN codes do. The numeric registry names no URN, so the link runs one way. A code without jsonrpc_code is identified by its URN or its CHIO-* string code.
One error, up to three identities
A URN entry that maps to a numeric code carries it as jsonrpc_code; 25 of the 111 URN codes do. Each numeric code then maps to a native wire name, a JSON-RPC code, or neither. Error Lookup.
The numeric registry in spec/errors/chio-error-registry.v1.json is the wire-side taxonomy. Each entry carries a numeric code, a stable name, its category, a transient flag, retry guidance, and a jsonrpcCode or nativeWireName that ties it to the wire. Codes with neither still carry their number and retry strategy.
urn:fatalAdversarial 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:errorArena 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:errorRequired 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:fatalTEE 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:fatalKernel 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:errorReceipt 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:errorCapability 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:errorCapability 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:errorCapability 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:errorCapability 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:fatalCapability 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:errorCapability 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:errorA 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:errorDurable 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:errorA 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:errorA 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:errorchio 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:warningchio 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:warningchio 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:warningchio 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:errorchio 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:errorchio 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:errorTwo 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:errorA 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:errorAn 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:errorCLI 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:errorCLI 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:errorRetired. 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:errorThe 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:errorA 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:errorPreflight 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:errorAn 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:errorA 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:errorThe 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:errorA 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:errorThe 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:errorThe 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:errorCLI 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:errorHost 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:errorAnother 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:errorCLI 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:errorApple 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:errorApple 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:errorApple 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:errorApple 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:errorApple 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:errorApple 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:errorApple 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:errorApple 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:errorWebAuthn 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:errorCapability 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:errorPasskey 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:errorWebAuthn 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:fatalCustody 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:errorGoogle 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:errorGoogle 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:errorGoogle 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:errorGoogle 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:errorCapability 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:errorWebAuthn 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:errorWebAuthn 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:errorDelegation 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:errorA 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:errorA 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:errorA 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:errorA 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:errorNo 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:errorA 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:errorGuard 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:warningGuard 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:warningGuard 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:fatalWASM 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:errorKernel 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:errorDelivered 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:errorRequest 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:errorRevealed 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:errorFinding-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:errorGrant 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:fatalKernel 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:errorReceipt 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:warningKernel 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:errorKernel 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:errorRuntime 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:errorSession 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:errorRequest 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:errorLineage 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:errorRequested 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:errorManifest 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:fatalManifest 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:errorRequested 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
Register the tool in the manifest or request a tool that is present.
urn:warningMobile 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:errorHosted 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:errorMobile 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:errorA 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:errorPolicy 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:errorPolicy 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:errorPolicy 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:errorGovernance 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:errorA 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:errorA 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:errorNo 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:errorA 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:errorAnthropic 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:errorBedrock 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:errorOpenAI 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:errorTool 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:errorThe 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:errorA 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:errorA 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:errorchio 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:errorA 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:errorReplay 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:warningReplay 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:errorReplay 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:errorThe --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:errorchio 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:errorA 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:warningThreat 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:errorTransaction 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:errorSwarm 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:errorBuyer 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:errorDispute, 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:errorTransaction 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:errorTransaction 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:errorTransaction 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:errorA 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:errorTransaction 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:errorTransaction 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:errorTransaction 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:errorTransaction 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:errorRuntime 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:errorSettlement 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:errorTransaction 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:errorA 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:errorTransport 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:fatalDPoP 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:errorHTTP 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:errorRequest 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:errorJSON-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:errorPeer 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:errorWrapped 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:errorA 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:errorA 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:errorA 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:errorA 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:errorA 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:errorNo 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:errorA 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:errorA 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:errorCosign 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:errorModel 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:errorProvider'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:fatalModel 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:errorModel 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:errorModel 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:errorRequested 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:errorRequested 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.
Try transient, nativeWireName, or reserved. Each entry has its own link.
Categories
protocolauthcapabilityguardbudgettoolinternaltransaction
Numeric error codes
| Code | Name | Category | Transient | JSON-RPC | Native wire name | Retry strategy and guidance |
|---|---|---|---|---|---|---|
1000 | protocol_ | protocol | no | -32600 | none | do_. Retry only after selecting a supported protocol version. |
1001 | session_ | protocol | no | -32002 | none | reinitialize. Open a new session and rerun initialize before retrying the operation. |
1002 | invalid_ | protocol | no | -32600 | none | do_not_retry. Correct the request shape before retrying. |
1100 | auth_ | auth | yes | none | none | retry_. Acquire valid credentials or refresh the token before retrying. |
2100 | capability_ | capability | no | none | capability_ | do_not_retry. Do not retry the same capability without correcting signature, scope, or subject binding. |
2101 | capability_ | capability | no | none | capability_ | retry_. Issue or obtain a fresh capability before retrying. |
2102 | capability_ | capability | no | none | capability_ | retry_. Obtain a newly issued capability; the revoked capability must not be retried. |
3100 | guard_denied | guard | no | none | policy_denied | do_not_retry. Adjust the request or policy inputs before retrying. |
4100 | budget_ | budget | yes | none | none | retry_. Retry only after budget replenishment, grant widening, or billing reconciliation. |
5100 | tool_ | tool | yes | none | tool_ | retry_. Use bounded exponential backoff unless upstream tooling documents a permanent failure. |
6100 | internal_error | internal | yes | none | internal_error | retry_. Retry with bounded backoff and escalate if the condition persists. |
7100 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Regenerate the passport with a registered transaction passport schema. |
7101 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Rebuild the passport root with matching evidence graph, claim set, and policy digests. |
7102 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Include every required evidence, claim-set, policy, and receipt node in the transaction graph. |
7103 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Emit an acyclic evidence graph whose dependency edges can be topologically verified. |
7104 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Add verified evidence for the required claim or remove the unsupported requirement. |
7105 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Regenerate the artifact set with matching transaction evidence digests. |
7106 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Bind identity evidence to the transaction passport subject and evidence graph. |
7107 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Bind capability, policy, approval, or guard evidence to the governed transaction. |
7108 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Provide checkpointed receipt or inclusion evidence for the transaction receipt. |
7109 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Regenerate runtime security, parity, lease, nonce, revocation, sandbox, ack, and terminal receipt evidence. |
7110 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Regenerate buyer review evidence that matches the transaction passport and verifier policy. |
7111 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Include settlement evidence bound to the transaction order, amount, currency, rail, and receipt lineage. |
7112 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Bind dispute, refund, remediation, and settlement reversal evidence to the transaction passport and receipts. |
7113 | transaction_ | transaction | no | none | transaction_ | do_not_retry. Provide verified transparency inclusion evidence or remove the transparency claim. |
A nativeWireName names a schema under chio-wire/v1/error/ when a native error schema carries the condition, and otherwise names the string the emitting verifier reports, which has no standalone schema in the bundle. The native channel supplies the structured detail body in both cases, so a consumer classifying an error MUST read both the numeric code and the code string.
URN entry fields
spec/errors/registry.schema.json pins the shape of spec/errors/registry.yaml. Each entry carries its urn and domain, a severity of info, warning, error, or fatal, a summary and help pair, a string_code for the CHIO-* outputs, an optional jsonrpc_code, a since tag, a stability of stable, unstable, or deprecated, and the consumed_by crates.
Domains
Every domain carries a class. A core domain holds codes a deployment raises; a reserved domain names the area it is held for.
| Domain | Class | Codes | Scope | Reserved for |
|---|---|---|---|---|
capability | core | 6 | Capability token validation, scope, subject binding, and revocation failures. | none |
policy | core | 4 | Policy load, compile, and decision failures. | none |
guard | core | 4 | Native, data, external, and WASM guard pipeline failures. | none |
attest | core | 3 | Receipt signing, evidence verification, and provenance failures. | none |
replay | core | 3 | Replay corpus, fixture, and deterministic comparison failures. | none |
provider | core | 4 | Provider adapter and tool-server failures. | none |
manifest | core | 4 | Manifest schema, signature, and registration failures. | none |
kernel | core | 13 | Runtime kernel session, request, budget, and internal failures. | none |
transport | core | 7 | Wire protocol, HTTP, JSON-RPC, auth, and DPoP transport failures. | none |
mobile | core | 3 | Mobile SDK offline queue, hosted oracle posting, and receipt round-trip failures. | none |
cli | core | 11 | Command-line parsing, local I/O, config, and rendering failures. | none |
delegation | reserved | 1 | Delegation chain and revocation oracle failures. | Recursive delegation and revocation oracle. |
adversarial | reserved | 1 | Adversarial escape, mutation, and containment failures. | Adversarial escape suite. |
threat | reserved | 1 | Threat model coverage and evidence classification failures. | Threat-model coverage checks. |
arena | reserved | 1 | Arena replay, verdict, and fixture orchestration failures. | Arena replay coliseum. |
economy | reserved | 1 | Metering, market, settlement, and budget- | Economic layer activation. |
lineage | reserved | 1 | Lineage graph, anchor, and ancestry failures. | Lineage and provenance graph. |
custody | core | 21 | Hardware custody, WebAuthn assertion, and audience-pinned capability envelope failures. | none |
weights | core | 8 | Model-card, weight hash, capability scope binding, and artifact integrity failures. | none |
transaction | core | 14 | Transaction passport, evidence graph, verifier policy, and proof artifact failures. | none |
Kernel delivery and purchase codes
Five codes in the kernel domain cover the delivery contract and the finding purchase path.
| URN | String code | Condition |
|---|---|---|
urn:chio:error:kernel:delivery- | CHIO- | Request carried an output-digest delivery contract the evaluator cannot enforce. |
urn:chio:error:kernel:delivery- | CHIO- | Delivered output did not hash to the frozen expected digest of the delivery contract. |
urn:chio:error:kernel:finding- | CHIO- | Grant carried a finding- |
urn:chio:error:kernel:finding- | CHIO- | Finding- |
urn:chio:error:kernel:finding- | CHIO- | Revealed finding payload did not carry the media type the signed finding advertises. |
Internet-Draft
The Chio protocol Internet-Draft specifies capability authorization, signed receipts, execution budgets, governed transactions, and receipt checkpoints for agent tool calls. It also defines the native framed transport, the hosted MCP binding, and trust-control operations. Its intended status is Standards Track.
The document reader carries the complete draft, section and paragraph links that match the official IETF HTML, and XML, plain text, and PDF downloads. Its metadata comes from the source document.
Versioning
spec/versions/chio-protocol-negotiation.v1.json (schema id chio.protocol-negotiation.v1) publishes the versioning policy: exact-match compatibility, and the rejection behavior of each protocol.
Try protocolVersion, chio.receipt.v1, or unknown members.
Per-protocol rules
| Protocol | Mechanism | Compatibility | Rejection behavior |
|---|---|---|---|
Native Chio | Out-of-band exact match on wire version chio-wire-v1 | exact match; no in-band downgrade | Transport close_; Chio error 1000 |
Hosted MCP | initialize. echoed in result.; MCP- session header | exact match from the supported set, ["2025-11-25"] | JSON-RPC -32600; Chio error 1000 |
Trust-control | Path prefix /v1 | exact prefix match | Standard 404; downgrade behavior not applicable |
Schema, capability, receipt, and manifest versioning
- Schema bundle: pinned by
spec/schemas/VERSIONand the per-filespec/schemas/MANIFEST.sha256. SDKs and codegen pipelines validate against the bundle. - Capability tokens: the schema is
chio.capability.v1;chio-wire/v1/capability/token.schema.jsonpins the canonical members. - Receipts: the schema is
chio.receipt.v1; a bridged invocation MUST use the same schema so the receipt log stays uniform. - Manifests: the schema is
chio.manifest.v1; the OpenAPI bridge MUST emit a manifest that conforms to it.
Compatibility policy
- Additive members MAY appear in JSON responses and signed artifacts; consumers MUST tolerate unknown members.
- Schema identifiers (
chio.*.v1) are exact-match. A schema-tagged artifact whose identifier the registry does not list MUST be rejected. - The protocol fails closed. It defines no downgrade and no speculative compatibility.
- Wire-version negotiation on the native transport is exact match with no downgrade, so an operator upgrading the wire version moves kernels and agents together.
Source files
Every table and browser here reads spec/schemas/, spec/errors/, spec/ietf/, and spec/versions/ in the chio repository, and the bundle version comes from spec/schemas/VERSION. SDKs, codegen pipelines, and conformance harnesses resolve types from these files first and treat hand-written bindings as derived.
spec/errors/README.md describes the URN registry and its fields, and spec/schemas/COVERAGE.md maps the tree family by family. The wire subtree carries its own notes in spec/schemas/chio-wire/v1/README.md and one README per subdirectory beneath it.