# Chio documentation

> Chio is a modern Rust kernel for agentic operating systems. These Markdown views export the same rendered articles, including code alternatives and source context. Interactive figures expose their rendered view; consult the linked page to interact.

## Subject indexes

- [agents](https://www.chio.computer/docs/agents/llms.txt)
- [build](https://www.chio.computer/docs/build/llms.txt)
- [platform](https://www.chio.computer/docs/platform/llms.txt)
- [learn](https://www.chio.computer/docs/learn/llms.txt)
- [economy](https://www.chio.computer/docs/economy/llms.txt)
- [reference](https://www.chio.computer/docs/reference/llms.txt)
- [security](https://www.chio.computer/docs/security/llms.txt)
- [products](https://www.chio.computer/docs/products/llms.txt)
- [processes](https://www.chio.computer/docs/processes/llms.txt)
- [federation](https://www.chio.computer/docs/federation/llms.txt)

## Articles

- [Belle](https://www.chio.computer/docs/agents/belle.md): Find your first door into Chio. Belle helps you choose a useful route through the documentation.
- [Burto](https://www.chio.computer/docs/agents/burto.md): Give the work an owner. Explore how Burto preserves completed work and resolves an interrupted assignment.
- [Chio](https://www.chio.computer/docs/agents/chio.md): Follow a question to its sources. Meet Chio and explore a grounded answer with the evidence beside it.
- [Doodles](https://www.chio.computer/docs/agents/doodles.md): Make room for an idea. Create, rearrange, and keep a writing workspace with Doodles.
- [Egg](https://www.chio.computer/docs/agents/egg.md): Small jobs, properly finished. Give an Egg a bounded task and inspect the result and attempt record.
- [Lollie](https://www.chio.computer/docs/agents/lollie.md): A little magic. A lot of looking after. Make a round with Lollie, inspect what needs care, and leave a useful handover.
- [Meet the Agents](https://www.chio.computer/docs/agents.md): Meet Chio, Belle, Doodles, Burto, Lollie, and the Eggs. Six personalities, six useful ways to move your work forward.
- [Build an Application](https://www.chio.computer/docs/build.md): Grow the Quickstart's project into an application: agents that work on your repository, and a service other agents call under your grants.
- [Runtime Assurance Tiers](https://www.chio.computer/docs/cluster/assurance-tiers.md): Shape capability authority with operator-defined runtime trust rules, tier ceilings, and signed minimum-assurance constraints. Trace the separate issuance and execution decisions.
- [Authority & Rotation](https://www.chio.computer/docs/cluster/authority.md): Separate replicated authority verification state from private signing custody. Follow key rotation, trusted history, issuance fencing, and remote cache refresh.
- [Budgets Across Nodes](https://www.chio.computer/docs/cluster/budgets.md): Coordinate budget exposure across Chio nodes with per-event replication witnesses, explicit compensation outcomes, and a clear boundary between authorized exposure and realized spend.
- [Cluster Coordination Contract](https://www.chio.computer/docs/cluster/coordination.md): Peer membership, leader-forwarded writes, replication health, and the guarantees of the cluster coordinator.
- [Evidence Export](https://www.chio.computer/docs/cluster/evidence-export.md): Carry Chio’s execution evidence across operator boundaries. Export scoped receipt packages, verify signatures and checkpoint proofs offline, and distinguish verified contents from trusted provenance.
- [Leader & Failover](https://www.chio.computer/docs/cluster/leader.md): Route Chio control-plane requests as peer availability changes. Inspect local leader selection, forwarding outcomes, authority term fences, and competing reachable views.
- [Capability Leases](https://www.chio.computer/docs/cluster/leases.md): Bind cross-operator workflow authority to a subject, tool scope, and validity window. Inspect lease issuance, destructive-step authorization, trusted signers, and proof verification.
- [Cluster Overview](https://www.chio.computer/docs/cluster/overview.md): Coordinate control state across Chio nodes within one operator's trust domain. Understand peers, replication, health, and where a single service is enough.
- [Cluster Peer Auth](https://www.chio.computer/docs/cluster/peer-auth.md): Authenticate Chio control-plane replication within one operator. Look up peer headers, digest bindings, verification failures, forwarded terms, and membership configuration.
- [Policy Rollout](https://www.chio.computer/docs/cluster/policy-rollout.md): Release executable policy across Chio nodes with pinned inputs, behavior checks, controlled restarts, and receipt evidence. Understand what source and runtime fingerprints establish.
- [Receipt Aggregation](https://www.chio.computer/docs/cluster/receipts.md): Bring signed execution evidence from multiple Chio nodes into a queryable local view. Follow receipt replication, signed lineage, mixed checkpoint batches, and scoped proof export.
- [Cluster Recovery](https://www.chio.computer/docs/cluster/recovery.md): Restore Chio control state after a partition, restart, or late join. Check local peer views, snapshot progress, the needed records, and budget acknowledgments before declaring recovery.
- [Replication & Convergence](https://www.chio.computer/docs/cluster/replication.md): Replicate Chio control state across operator-owned nodes. Inspect pull allowances, stream ordering, snapshot recovery, and the acknowledgment boundary behind budget witnesses.
- [Operator Reports](https://www.chio.computer/docs/cluster/reports.md): Inspect agent activity, delegated spending, settlement work, and evidence readiness through Chio’s operator reports. Choose a report, scope the request, and interpret limits and signed exports.
- [Revocation Propagation](https://www.chio.computer/docs/cluster/revocation.md): Carry withdrawn capability authority across Chio control-plane nodes. Inspect stream continuity, local log positions, snapshot consistency, and the scope of propagation-lag evidence.
- [Tenancy & Read Scoping](https://www.chio.computer/docs/cluster/tenancy.md): Give each tenant access to its execution evidence in a shared Chio control plane. Configure read credentials, understand receipt attribution, and diagnose empty or denied queries.
- [Cluster Upgrade](https://www.chio.computer/docs/cluster/upgrade.md): Upgrade a Chio fleet with a qualified binary set, a recoverable state boundary, and explicit checks for authority, peer repair, and governed work.
- [Agentic Operating Systems](https://www.chio.computer/docs/concepts/agentic-operating-systems.md): Give intelligent work identity, authority, tools, retained progress, and a path through interruption to an inspected result.
- [Architecture](https://www.chio.computer/docs/concepts/architecture.md): Build agentic operating systems on Chio: a shared kernel for delegated authority, durable work, and cooperation across independent operators.
- [Autonomy with Authority](https://www.chio.computer/docs/concepts/autonomy-with-authority.md): Give agents room to work. Make scope, delegation, consequential decisions, and revocation visible in an executable mandate.
- [Beyond Blocklists](https://www.chio.computer/docs/concepts/beyond-blocklists.md): Why a pattern list cannot bound a model that writes its own commands, and the grants, confinement, labels, and quotas that can.
- [Capabilities](https://www.chio.computer/docs/concepts/capabilities.md): Define what an agent may do, what it may delegate, and how the Chio kernel enforces those grants.
- [Markets for Agent Work](https://www.chio.computer/docs/concepts/cognition-market.md): Let useful agent results travel with a precise claim, supporting evidence, committed delivery, and terms another participant can assess.
- [Compliance as Code](https://www.chio.computer/docs/concepts/compliance-as-code.md): Connect organizational rules to executable controls, observed decisions, and evidence a reviewer can inspect.
- [The Computer and the Kernel](https://www.chio.computer/docs/concepts/computer-and-kernel.md): How each Computer SDK call lowers to the kernel: grants, runs, history, policy, services, and partners as kernel objects.
- [Cooperation Across Companies](https://www.chio.computer/docs/concepts/cooperation-across-companies.md): Let independently operated agent systems contribute to a shared job while each company retains authority over its own resources.
- [The Delivery Contract](https://www.chio.computer/docs/concepts/delivery-contract.md): Bind spending authority to a committed output. Chio checks delivered content before settlement and records a mismatch as a zero-charge denial.
- [Detect, Contain, Recover](https://www.chio.computer/docs/concepts/detect-contain-recover.md): Detect misuse with decoys and correlated security events, contain an exact affected set at its next call, and recover from the signed record.
- [Determinism and replay](https://www.chio.computer/docs/concepts/determinism.md): Reproducible kernel decisions, canonical signed records, and the precise checks supported by Chio's replay tools.
- [What Survives a Crash](https://www.chio.computer/docs/concepts/durability.md): How Chio binds interrupted work to a durable operation, recovers it by the dispatch boundary, and keeps retries from repeating an effect.
- [Budgets & Metering](https://www.chio.computer/docs/concepts/economics.md): Give agents bounded spending authority: grant limits checked before dispatch, narrower allowances for delegates, and signed records of each charge.
- [Federation & Swarms](https://www.chio.computer/docs/concepts/federation-swarms.md): Two organizations can share agent work without trusting each other's machines: grants that only narrow, treaties each kernel computes, and receipts both kernels sign.
- [Information Flow Across Calls](https://www.chio.computer/docs/concepts/flow-across-calls.md): Let agents read sensitive data and keep working, while the kernel refuses to send what they learned to destinations without clearance.
- [Formal assurance](https://www.chio.computer/docs/concepts/formal-assurance.md): How selected production Rust decisions connect to extracted Lean definitions, bounded models, runtime checks, and explicit proof assumptions.
- [The Ideas Behind Chio](https://www.chio.computer/docs/concepts/foundations.md): Capabilities, mediation, hash trees, and canonical bytes come from sixty years of research. Each leads to the Chio mechanism that applies it.
- [Glossary](https://www.chio.computer/docs/concepts/glossary.md): Chio’s terms for authority, the governed call, evidence, rules across calls, containment, and work across organizations, each linked to the page that develops it.
- [Guards](https://www.chio.computer/docs/concepts/guards.md): Apply policy to the calls a grant permits: the ordered guard pipeline, its verdicts, the evidence it records, and checks for each resource.
- [Human-in-the-Loop](https://www.chio.computer/docs/concepts/human-in-the-loop.md): Give an agent bounded autonomy and require a request-bound human approval when an action crosses a policy threshold.
- [How a Call Enters the Kernel](https://www.chio.computer/docs/concepts/interposition.md): Put Chio’s admission decision in front of the work it governs: inside a Rust service, behind an MCP endpoint, or at a proxy.
- [The Mediated Call](https://www.chio.computer/docs/concepts/mediated-call.md): Follow one request through authority checks, guards, dispatch, output checks, and its signed record, and see where each refusal lands.
- [Model Cards](https://www.chio.computer/docs/concepts/model-cards.md): Connect model provenance to operational authority. Signed cards constrain the weights, scopes, and tools accepted by a provider-binding integration.
- [What a Policy Permits](https://www.chio.computer/docs/concepts/policy-coverage.md): Review a policy change by the requests it newly admits, and connect each threat to its boundary and a test that can fail.
- [Portable Kernel](https://www.chio.computer/docs/concepts/portable-kernel.md): Bring Chio's Rust authority model to server, browser, and mobile applications. Run the browser example and integrate current mobile bindings.
- [Receipts](https://www.chio.computer/docs/concepts/receipts.md): Read a signed receipt field by field, tell what each receipt kind claims, verify exported evidence, and rebuild a refused attempt from its records.
- [Reputation & Passports](https://www.chio.computer/docs/concepts/reputation-passports.md): Turn attributable operating history into signed credentials an agent can present across operators, while each receiver decides whose assessment to accept.
- [Rules Across a Session](https://www.chio.computer/docs/concepts/session-rules.md): Govern the order and volume of an agent's work with session guards that read the journal of governed calls: sequence rules, byte ceilings, and advisory signals.
- [Sovereign Intelligence](https://www.chio.computer/docs/concepts/sovereign-cognition.md): Build intelligence that remains under your authority as models, providers, and relationships change.
- [Task-Scoped Authority](https://www.chio.computer/docs/concepts/task-scoped-authority.md): Issue each subtask its own short grant, so text an agent reads during that task can reach only what the task holds.
- [Assurance Boundaries & Limits](https://www.chio.computer/docs/concepts/trust-boundaries.md): Read each signed record for the claim it can support: decisions, observations, and advice, and the limits no record can cross.
- [Assurance Model](https://www.chio.computer/docs/concepts/trust-model.md): Identify the trusted components, deployment assumptions, and limits of Chio's proofs and signed receipts.
- [The State a Verdict Depends On](https://www.chio.computer/docs/concepts/verdict-state.md): Trace the request, authority, time, policy, and runtime state behind a Chio decision, from portable checks to hosted enforcement.
- [Verifiable Evidence](https://www.chio.computer/docs/concepts/verifiable-evidence.md): Export signed execution records that another operator can inspect. Verify receipt integrity, checkpoint membership, and the exact limits of the evidence.
- [What You Can Build](https://www.chio.computer/docs/concepts/what-you-can-build.md): Eight systems composed from Chio's mechanisms, each with the call where the kernel decides and the project, guide, or walkthrough that runs it.
- [Why Agents Need a Kernel](https://www.chio.computer/docs/concepts/why-a-kernel.md): A kernel defines the abstractions programs are written against. Chio defines them for agents: signed authority, supervised work, budgets debited before dispatch, and receipts another organization can verify.
- [Why Capabilities](https://www.chio.computer/docs/concepts/why-capabilities.md): Why Chio grants authority as capabilities: Lampson’s access matrix stored by row or by column, the confused deputy, and what signed grants add.
- [Workload Identity](https://www.chio.computer/docs/concepts/workload-identity.md): Connect agent authority to the workload presenting it. Chio evaluates SPIFFE identity and runtime assurance across mesh and attestation integrations.
- [Build From Source](https://www.chio.computer/docs/contributors/build-from-source.md): Clone the public Chio source, install the pinned Rust toolchain and native dependencies, and build the CLI, the workspace, and the language server.
- [Contribute to Chio](https://www.chio.computer/docs/contributors.md): Work on Chio itself: the repository layout, the source build, the gates every change passes, and the fixture corpus the verifiers check.
- [Proof Fixture Corpus](https://www.chio.computer/docs/contributors/proof-fixtures.md): The signed Proof Room scenarios, the trust anchors that verify them, and how to add a negative case the verifier must reject.
- [Checks and Qualification](https://www.chio.computer/docs/contributors/qualification.md): Run the verification gate, the xtask drift and fixture checks, the behavioral gate scripts, and the example smoke runner before a change lands.
- [Azure Container Apps](https://www.chio.computer/docs/deployment/azure.md): Deploy a Chio-governed tool server on Azure Container Apps with a sidecar, Key Vault authority seed, single-replica receipts, and Log Analytics.
- [Backup & Restore](https://www.chio.computer/docs/deployment/backup-dr.md): Back up the receipt store, the kernel signing key, partner state, and capability authority, anchor checkpoints outside the operator, and rehearse a restore that keeps admission closed until four checks pass.
- [Cloud Run](https://www.chio.computer/docs/deployment/cloud-run.md): Deploy a Chio-governed tool server on Google Cloud Run with a Knative sidecar, Secret Manager authority seed, single-instance receipts, and Cloud Logging.
- [Container Images](https://www.chio.computer/docs/deployment/container-images.md): The signed Chio images each release publishes: the CLI image, the sidecar that fronts the pricing service, the Proof Room, and the TEE runner, with their users, stages, tags, and signatures.
- [ECS Fargate](https://www.chio.computer/docs/deployment/ecs.md): Deploy a Chio-governed tool server on AWS ECS Fargate with a sidecar, file-mounted authority seed, durable SQLite receipts, ALB ingress, and CloudWatch logs.
- [In-Process Library](https://www.chio.computer/docs/deployment/in-process.md): Link the Chio kernel into a Rust binary: add the crates, load the signing seed, build the kernel with durable stores, share it across tasks, and drain it before exit.
- [Kubernetes Admission](https://www.chio.computer/docs/deployment/kubernetes.md): Deploy Chio on Kubernetes with the ChioPolicy CRD and fail-closed validating and mutating admission webhooks that check each pod's capability token against the kernel keys pinned in a trust file before admission.
- [Node Observability](https://www.chio.computer/docs/deployment/observability.md): Wire a Chio node into your telemetry stack: what the sidecar /metrics endpoint carries, the three guard descriptor tables, the OpenTelemetry collector and receipt exporter, the shipped Grafana dashboards, and the SRE alert-rule pack.
- [Receipt Dashboard](https://www.chio.computer/docs/deployment/receipt-dashboard.md): Operator dashboard for the Chio receipt log. Review activity, spend, budget pressure, compliance state, settlement status, delegation chains, and reputation comparisons.
- [Secrets & Signing Keys](https://www.chio.computer/docs/deployment/secrets-keys.md): Chio signing, issuer, admin-control, and federation keys; configuration through seed files and the trust file; rotation and recovery procedures.
- [Sidecar HTTP Service](https://www.chio.computer/docs/deployment/sidecar.md): Run the kernel in its own container beside your application: pull the image, run it in front of your API, gate on readiness, supervise it, and drain it on SIGTERM.
- [SIEM Export](https://www.chio.computer/docs/deployment/siem-export.md): Stream Chio receipts to SIEM and SOC backends with chio-wall siem-export, including supported exporters, retries, dead-letter queues, SQLite cursors, and alerts.
- [Confidential Node](https://www.chio.computer/docs/deployment/tee.md): Run a Chio node in a Trusted Execution Environment so its signing identity binds to a measured enclave: the chio-tee image, attestation flow, verdict-only/shadow/enforce modes, chio-tee Loki dashboard.
- [Trust Control Plane](https://www.chio.computer/docs/deployment/trust-control-plane.md): Run the Chio replicated trust-control service with leader-follower replication, durable budget, revocation, and receipt stores, failover, and key rotation.
- [Anchoring](https://www.chio.computer/docs/economy/anchoring.md): Publish receipt checkpoint roots to the EVM ChioRootRegistry, Bitcoin through OpenTimestamps, a Solana memo, and a Rekor witness, then verify a receipt's inclusion against them offline.
- [Approval-Bound Payments](https://www.chio.computer/docs/economy/approval-bound-payments.md): Bind x402, EIP-3009, and Circle payments to one person-signed approval, spend each approval once, and keep payment proofs from authorizing tool calls.
- [Authoritative Spend](https://www.chio.computer/docs/economy/authoritative-spend.md): The predicate that separates a receipt recording governed spend from a receipt that only says it did: a mediated Allow, a reconciled hold, a signed execution nonce, and an admitted kernel key.
- [Autonomous Pricing & Capital Optimization](https://www.chio.computer/docs/economy/autonomous-pricing.md): Reference for chio-autonomy record types and validators for pricing inputs, authority envelopes, decisions, capital planning, execution, rollback, comparison, drift, and qualification.
- [Two-Org Worked Example](https://www.chio.computer/docs/economy/bilateral-federation.md): Let a partner's agent call your tool: add its partner card, record your admission policy, issue a capped federated capability, and admit the call at your door.
- [Bilateral Receipts](https://www.chio.computer/docs/economy/bilateral-receipts.md): Cross-organization calls can produce dual-signed receipts. The tool-host and origin kernels sign the same receipt body for independent verification.
- [Obligations](https://www.chio.computer/docs/economy/chio-paper.md): How Chio records one obligation atom, keeps its creditor in a separate authenticated record, and sells that receivable once through a compare-and-swap.
- [Claims Lifecycle](https://www.chio.computer/docs/economy/claims.md): Signed claims workflow: package, response, dispute, adjudication, payout instruction, payout receipt, settlement instruction, settlement receipt. Plus the lighter file_claim helper and how payouts reconcile back into facility and bond accounting.
- [Clearing Rounds](https://www.chio.computer/docs/economy/clearinghouse.md): How Chio nets a complete, reserved set of single-currency obligation atoms into signed settlement intents through a ten-state clearing round.
- [Challenges and liability](https://www.chio.computer/docs/economy/cognition-challenges.md): Finding disputes: two authorization branches, three mechanical evidence classes, three verdicts, and the liability head an upheld challenge opens.
- [Finding records](https://www.chio.computer/docs/economy/cognition-findings.md): Field reference for chio.finding.v1, the signed information good traded on the cognition market, including its guarantee and evidence classes.
- [The Hosted Profile](https://www.chio.computer/docs/economy/cognition-hosted.md): The multi-tenant cognition market deployment: the PostgreSQL store, the authenticated edge, the isolated workers, the storage authority modes, and every ceiling the profile enforces.
- [The Cognition Market](https://www.chio.computer/docs/economy/cognition-market.md): Run a local market where a partner sells a fix for one of your issues, you verify its evidence, and committed delivery controls payment.
- [Pricing a Finding](https://www.chio.computer/docs/economy/cognition-pricing.md): The buyer-local bid ceiling, its rejections, the posted seller price, guarantee-class discounts, the collateral exposure cap, and the audit deterrence condition.
- [Paid reveal](https://www.chio.computer/docs/economy/cognition-reveal.md): Buy a finding through a governed call that binds spending to its committed payload, then inspect delivery, payment, and recovery outcomes.
- [Finding Status](https://www.chio.computer/docs/economy/cognition-status.md): The signed sparse-map status feed, its portable non-inclusion proof, and the durable rollback floor a verifier accepts it against.
- [Cognition Market Threat Model](https://www.chio.computer/docs/economy/cognition-threats.md): Assets, trust roles, adversary categories, the attack catalog, and the residual risks the cognition market prices rather than eliminates.
- [Compliance Certificates](https://www.chio.computer/docs/economy/compliance-certificates.md): A session-end signed certificate over receipt signatures, chain order, authorized scope, budget limits, and required guard evidence, with the three chio cert commands that produce and check it.
- [Comptroller Console](https://www.chio.computer/docs/economy/comptroller-console.md): Stream spend from signed receipts, receive signed budget-threshold webhooks, project burn rate in integer arithmetic, export recomputable anomaly findings, and read the comptroller surface report.
- [Money Conservation](https://www.chio.computer/docs/economy/conservation.md): The kernel's budget conservation law and the escrow identity P + R + L + F = D: what each term is, how each is preserved, and how a reader checks both from exported evidence.
- [Contracts](https://www.chio.computer/docs/economy/contracts.md): The three signed legs of an economic contract in chio-open-market: BidRequest, AskResponse, and an AcceptedBid admissible only against a verified funds reservation.
- [Credit Facilities](https://www.chio.computer/docs/economy/credit-facilities.md): Give agent activity bounded credit authority, connect it to signed execution evidence, and distinguish capital decisions from external fund movement.
- [Cross-Currency Budgets](https://www.chio.computer/docs/economy/cross-currency.md): Hold a dollar budget against a tool that bills in USDC or ETH, converted at a checked Chainlink and Pyth rate with an operator margin and signed into the receipt.
- [Cross-Org Swarms](https://www.chio.computer/docs/economy/cross-org-swarms.md): How a task graph that leaves its own kernel is checked: route-plan egress, a treaty-bound admission report, and the co-signature the action class demands.
- [Capability Discovery](https://www.chio.computer/docs/economy/discovery.md): How tool servers register manifests and listings, activate local trust, exchange listings through bilateral federation, and use the chio-open-market bid/ask/accept protocol.
- [Financial Credentials](https://www.chio.computer/docs/economy/financial-credentials.md): The chio.fincred schema family and the financial agent passport that carries it: credential shape, source evidence, selective disclosure, and verifier policy.
- [Fiscal Charters](https://www.chio.computer/docs/economy/fiscal-constitutions.md): How a Chio operator governs economic parameters through signed schedules, quorum approval, a timelock, and rollback protection.
- [Listing Disputes, Freezes, and Sanctions](https://www.chio.computer/docs/economy/governance.md): The chio-governance dispute, freeze, sanction, and appeal lifecycle: signed charters and cases, evaluation results, and admission-blocking rules.
- [Guarantees and Boundaries](https://www.chio.computer/docs/economy/guarantees.md): Every economic claim Chio makes, classified by boundary class: what the kernel refuses before dispatch, what it records after, what only informs, and what it never sees.
- [Guard Marketplace](https://www.chio.computer/docs/economy/guard-marketplace.md): List, price, and install guards other publishers wrote, with prices set by your reputation tier and every install gated by an underwriting credit limit.
- [Liability Coverage](https://www.chio.computer/docs/economy/liability-market.md): Connect agent activity to scoped liability coverage through provider policies, quoted terms, delegated binding authority, and signed coverage records.
- [Signed Tool Manifests](https://www.chio.computer/docs/economy/manifests.md): Tool servers declare their tools, schemas, and required permissions in a chio.manifest.v1 manifest signed with the server's Ed25519 key. The kernel verifies the signature before admitting the server.
- [On-Chain Settlement](https://www.chio.computer/docs/economy/onchain-settlement.md): Web3 settlement details: five Web3ContractKind families, dual-signature and Merkle-proof releases, escrow states, EVM and Solana support, and Chainlink CCIP coordination.
- [Bidding in the Open Market](https://www.chio.computer/docs/economy/open-market.md): The bid/ask/accept flow in chio-open-market: BidRequest, AskResponse, and AcceptedBid; its fee schedule and penalties; and its relationship to chio-listing and chio-market.
- [Operating an Economy](https://www.chio.computer/docs/economy/operating.md): The operating decisions a Chio deployment has to make: rail allocation per counterparty, facility and bond sizing, federation onboarding, key handling, and where each knob is configured.
- [Outcome-Based Pricing](https://www.chio.computer/docs/economy/outcome-pricing.md): The chio-outcome artifacts: a signed price, a signed JSON Pointer predicate over the delivered bytes, and a price assessment that is full or zero.
- [Agentic Economy](https://www.chio.computer/docs/economy/overview.md): How agents spend under bounded authority, get paid for verified work, and settle what they owe, with every charge reserved before dispatch and recorded on a signed receipt.
- [Charged at the Owner's Door](https://www.chio.computer/docs/economy/owners-door.md): When your partner's agents use your resources, your kernel enforces and charges their grant from its own hold ledger, with no funding transfer between the organizations.
- [Parametric Insurance](https://www.chio.computer/docs/economy/parametric-insurance.md): The chio-parametric policy in chio-market: typed trigger predicates over proven receipt evidence, a checked payout schedule, and the claim record they open.
- [Agent Passports](https://www.chio.computer/docs/economy/passports.md): Agent Passport reference: did:chio identifiers, credential projections, OpenID issuance and presentation, multi-issuer composition, and offline verification.
- [Payment Channels](https://www.chio.computer/docs/economy/payment-channels.md): How two parties fund a bounded escrow, reserve capacity for repeated calls, and settle one cumulative signed balance at close.
- [Portable Reputation](https://www.chio.computer/docs/economy/portable-reputation.md): How Agent Passports, dual-signed receipts, and per-organization scoring let an agent present signed receipt history across organizations.
- [Predeclared Settlement](https://www.chio.computer/docs/economy/predeclared-settlement.md): How Chio fixes release and refund outcomes when an escrow, bond, or claim opens and prevents later changes to price or payee.
- [Pricing Models](https://www.chio.computer/docs/economy/pricing.md): Connect advertised prices, bounded spending authority, metered quotes, and settlement evidence for Chio tool calls.
- [Reconciliation](https://www.chio.computer/docs/economy/reconciliation.md): How Chio reconciles quoted, observed, and charged cost. Covers the exposure ledger, settlement watchdog, loss lifecycle, and billing exports.
- [Audit APIs](https://www.chio.computer/docs/economy/regulatory-apis.md): Read-only signed receipt export with time-windowed queries, framework mappings, and an auditor workflow.
- [Reputation Scoring](https://www.chio.computer/docs/economy/reputation.md): Look up local reputation metrics, evidence requirements, capability issuance ceilings, and the separate feed-based marketplace tiers.
- [Revenue Splits](https://www.chio.computer/docs/economy/revenue-splits.md): Declare a tool's beneficiaries in its signed price, settle one commitment per beneficiary in basis points, hold a share until its vesting cliff, and tag it all with an EconomyId.
- [Risk Comptroller Reports](https://www.chio.computer/docs/economy/risk-comptroller.md): The chio-risk-comptroller verifier: how a signed risk/insurance authority report is admitted as evidence for a Transaction Passport, its schema, its internal-consistency invariants, and cross-report portfolio adequacy.
- [Run Verifiable Work](https://www.chio.computer/docs/economy/run-verifiable-work.md): Buy an authentication inventory of the pricing service's OpenAPI document from your partner, have a pinned verifier check it, and pay only after the check passes.
- [Credit Scorecards](https://www.chio.computer/docs/economy/scorecards.md): How chio-credit collapses receipts, reputation, and settlement history into a CreditScorecardReport: five bands, four dimensions, three confidence levels, anomaly reasons, and probation tracking.
- [Settlement Rails](https://www.chio.computer/docs/economy/settlement-rails.md): Choose a payment integration, distinguish held authorization from final prepayment, and connect payment results to reconciliation.
- [Shared Budgets and Pools](https://www.chio.computer/docs/economy/shared-budgets.md): Let many agents share one budget: a family cap co-debited by every delegated hold, model calls held at their worst case, and pools that buy a finding once.
- [Economy Crates](https://www.chio.computer/docs/economy/stack.md): Find the Chio crate that owns pricing, market records, credit, settlement, or metering, and distinguish its public API from kernel runtime integration.
- [Underwriting](https://www.chio.computer/docs/economy/underwriting.md): Risk classes, reason codes, decision outcomes, default policy thresholds, evidence kinds, premium pricing, and the structure of UnderwritingComplianceEvidence.
- [Verifiable Work](https://www.chio.computer/docs/economy/verifiable-work.md): Hire a company you have never audited, let it subcontract without unbacked promises, and pay only for results a verifier you both chose has checked.
- [Verify Commerce Evidence](https://www.chio.computer/docs/economy/wall-stops-money.md): Verify an offline Proof Room bundle containing mandate, denial, allow, and settlement records without moving funds.
- [Economic Wind Tunnel](https://www.chio.computer/docs/economy/wind-tunnel.md): Replay seeded adversarial economic campaigns against the validators that hold money, and sign a qualification matrix only when every one fails closed.
- [Work Agreements and Funding](https://www.chio.computer/docs/economy/work-agreements.md): What both parties sign in a work agreement, how an exclusive allocation backs it, and when a supplier may subcontract from prefunded money.
- [Work Claim Escrow](https://www.chio.computer/docs/economy/work-escrow.md): Follow a funded work claim through submission, a verifier's signed decision, and payment or refund, and see which failures cannot erase an earned claim.
- [How a Purchase Works](https://www.chio.computer/docs/economy/worked-example.md): Follow a service purchase through accepted terms, durable reservations, independent approval, verified delivery, accounting, and recovery.
- [Agent Commerce Network](https://www.chio.computer/docs/examples/agent-commerce-network.md): Build a procurement agent that buys actual source review, verifies delivered artifacts, and retains budget reservations, signed receipts and balanced settlement entries.
- [Agent Framework SDKs](https://www.chio.computer/docs/examples/agent-framework-sdks.md): Build real CrewAI, AutoGen and LlamaIndex tools with Chio admission, scoped writer/auditor agents and verifiable execution receipts.
- [LangChain and Provider SDKs](https://www.chio.computer/docs/examples/agent-sdks.md): Connect LangChain, OpenAI or Anthropic to your Chio-governed notes application. Keep authority in the host and return results to the model.
- [Build a cognition marketplace](https://www.chio.computer/docs/examples/agentic-os/cognition-marketplace.md): Generate a repair, have a venue replay it, purchase verified work within a bid, and apply the patch to a separate customer project.
- [Build an agent cooperative](https://www.chio.computer/docs/examples/agentic-os/cooperative.md): Let independent operators authorize shared computation, including a registered 2-of-3 threshold settlement with retained local-credit accounting.
- [Build federated incident response](https://www.chio.computer/docs/examples/agentic-os/incident-response.md): Investigate a service failure across three independently governed organizations, approve one bounded repair, and confirm health after the change.
- [Build an institutional knowledge network](https://www.chio.computer/docs/examples/agentic-os/knowledge-network.md): Retrieve permitted source versions, produce a cited answer, and show the caller when revocation or a stale citation stops a request.
- [Build a mission host](https://www.chio.computer/docs/examples/agentic-os/mission-host.md): Run two scoped workers over one document, join their results by digest, and let a model answer through the same governed tools.
- [Operate an Agentic OS](https://www.chio.computer/docs/examples/agentic-os/operations.md): Kill processes, cancel work, expire authority, and recover only the outcomes the effect owner can prove.
- [Build an Agentic OS](https://www.chio.computer/docs/examples/agentic-os.md): Connect knowledge, adaptive research, jointly authorized computation, and tested repair in one executable mission.
- [Build a personal agent network](https://www.chio.computer/docs/examples/agentic-os/personal-network.md): Connect a coordinator, a private knowledge node, and a compute node with independent identities, explicit membership, and governed remote tools.
- [Build a research swarm](https://www.chio.computer/docs/examples/agentic-os/research-swarm.md): Turn signed observations into retained assignments, run bounded investigations, and compare adaptive with fixed scheduling on the same workload.
- [Build a shared worker fleet](https://www.chio.computer/docs/examples/agentic-os/shared-worker-fleet.md): Run competing workers against one durable authority, account for every report, and recover a lost acknowledgement without producing a report twice.
- [Build a software factory](https://www.chio.computer/docs/examples/agentic-os/software-factory.md): Turn an issue into a patch, test and review one exact candidate, and publish only the candidate the release owner approves.
- [Cross-Provider Policy](https://www.chio.computer/docs/examples/cross-provider-policy.md): Run OpenAI and Anthropic against the same Chio notes host, change the write policy, and inspect independently verified signed receipts.
- [Building Custom Guards](https://www.chio.computer/docs/examples/custom-guards.md): Compile a custom rule to WebAssembly, load it into Chio’s Rust kernel, and govern documents with visible decisions and signed receipts.
- [Hello A2A](https://www.chio.computer/docs/examples/hello-a2a.md): Call a governed document tool over A2A HTTP with the official client, then verify the task, output and signed decision.
- [Hello ACP](https://www.chio.computer/docs/examples/hello-acp.md): Open an ACP session with the official client, invoke a governed document tool, and verify the tool update and signed result.
- [Pricing over MCP](https://www.chio.computer/docs/examples/hello-mcp.md): Serve Larkfield's pricing API to an agent as MCP tools with an embedded Chio kernel, a two-quote grant, and signed decisions for every call.
- [Pricing as Native Tools](https://www.chio.computer/docs/examples/hello-tool.md): Run Larkfield's quote and refund as native Rust tools behind an embedded Chio kernel, change the agent's grant, and verify the signed decisions.
- [Go and C++ HTTP](https://www.chio.computer/docs/examples/http-go-cpp.md): Run Larkfield's pricing service in Go with chi and in C++ with Drogon, with each quote admitted by Chio before its handler runs.
- [JVM and .NET HTTP](https://www.chio.computer/docs/examples/http-jvm-dotnet.md): Run Larkfield's pricing service in Spring Boot and ASP.NET Core, with each quote admitted by Chio before its controller runs.
- [Node HTTP Frameworks](https://www.chio.computer/docs/examples/http-node.md): Run Larkfield's pricing service in Express, Fastify, and Elysia, with each quote admitted by Chio before its handler runs.
- [Python HTTP Frameworks](https://www.chio.computer/docs/examples/http-python.md): Run Larkfield's pricing service in FastAPI and Django, with each quote admitted by Chio before its view runs.
- [Internet of Agents: Incident Network](https://www.chio.computer/docs/examples/incident-network.md): Coordinate investigation and an approved repair across independent Chio hosts, then check the service after the change.
- [Istio ext_authz](https://www.chio.computer/docs/examples/istio-ext-authz.md): Deploy a notes API behind Istio and Chio, revoke a caller grant, and verify the signed admission record.
- [OpenAPI Sidecar](https://www.chio.computer/docs/examples/openapi-sidecar.md): Put Larkfield's plain HTTP pricing API behind chio api protect, so its OpenAPI document decides which routes need a grant and every decision is signed.
- [OpenTelemetry](https://www.chio.computer/docs/examples/opentelemetry.md): Run four repricing outcomes and follow each OpenTelemetry span to its signed Chio receipt and the price sheet the job left behind.
- [Examples Overview](https://www.chio.computer/docs/examples/overview.md): The downloadable Larkfield projects: the pricing service in every framework, native tools, MCP hosts, and the pricing desk, each one command away.
- [Playground AI players](https://www.chio.computer/docs/examples/playground-ai-players.md): How structured observations, game-owned controls, and retained trials let AI players act in four Chio Playground games.
- [Receipt Verification](https://www.chio.computer/docs/examples/receipt-verify.md): Verify Chio evidence offline with complete Python, Node and Go programs. Select a trusted signer, inspect a signed decision, and detect tampering.
- [Builder Setup](https://www.chio.computer/docs/examples/setup.md): Install Chio once, pull a complete example with chio new, and run it with the CLI and SDKs you installed.
- [Trust Control Walkthrough](https://www.chio.computer/docs/examples/trust-control.md): Issue a quote under a granted capability, revoke that same grant, and verify that repeated quotes are refused across restart and authority outage.
- [Web3 Work Orders](https://www.chio.computer/docs/examples/web3-network.md): Build a four-kernel network with native passports, two-hop delegation, real escrow, standard x402 payments, recovery and independently verified receipts.
- [Quorum & Anti-Eclipse](https://www.chio.computer/docs/federation/anti-eclipse.md): Inspect a federated listing through multiple publishers: anti-eclipse policy, observation freshness, final-state validation, and the trust checks a receiving operator owns.
- [Federation Assurance](https://www.chio.computer/docs/federation/assurance.md): What is proved, modeled, fuzzed, and tested about federation: the qualification matrix, the revocation models, the fuzz targets, the conformance suites, the loom models, and the negative corpora.
- [Federation Authority](https://www.chio.computer/docs/federation/authority.md): Act as the issuer for one boundary: the authority profile, the seeds bound to its declared keys, the issuance request, and the leases and governance receipts it signs over digested scope bindings.
- [Colorado AI requirements](https://www.chio.computer/docs/federation/colorado-sb-24-205.md): Chio evidence controls for Colorado AI documentation and review, with the 2026 replacement of SB 24-205 identified explicitly.
- [Compliance Frameworks](https://www.chio.computer/docs/federation/compliance-frameworks.md): Technical mappings from Chio controls and implementation evidence to PCI DSS v4.0.1 requirements and the OWASP LLM Top 10, plus the evidence pipeline every framework mapping draws on.
- [Cross-Operator Delegation](https://www.chio.computer/docs/federation/delegation.md): Bound what a partner may request with a signed federated delegation policy, continue from an imported upstream capability, and keep derived-authority mechanics in Swarm.
- [Federate Enterprise Identity](https://www.chio.computer/docs/federation/enterprise-identity.md): Admit enterprise bearer tokens at the MCP edge, map each principal to a stable Chio subject, and read the enterprise identity context on every session.
- [EU AI Act](https://www.chio.computer/docs/federation/eu-ai-act.md): Technical mapping of Chio signed receipts, Merkle checkpoints, DPoP binding, and retention configuration to selected EU AI Act logging, oversight, and risk-management provisions.
- [Share Evidence with a Partner](https://www.chio.computer/docs/federation/evidence-sharing.md): Sign a bounded sharing policy, export receipts under it with checkpoint proofs, import the package on the partner, and inspect shared references from local activity.
- [HITRUST i1 Readiness Package](https://www.chio.computer/docs/federation/hitrust-i1.md): A HITRUST CSF v11.7 i1 control mapping from each family to Chio's implementation evidence and the operator's duties, with an offline evidence package for the assessor.
- [Iroh Federation Transport](https://www.chio.computer/docs/federation/iroh-transport.md): Connect Chio kernels over authenticated QUIC, bind transport keys to admitted operators, and carry federation protocols through separate verified handlers.
- [ISO 42001 Mapping](https://www.chio.computer/docs/federation/iso-42001.md): A technical mapping from Chio controls and implementation evidence to selected ISO/IEC 42001:2023 clauses for operator self-assessment.
- [NIST AI RMF](https://www.chio.computer/docs/federation/nist-ai-rmf.md): A technical mapping from Chio controls and implementation evidence to NIST AI RMF 1.0 functions for operator self-assessment.
- [Open Admission & Stake](https://www.chio.computer/docs/federation/open-admission.md): The signed open-admission policy with its admission classes and stake requirements, the trust service's permissionless registry with anti-sybil controls, and how a peer is evaluated under both.
- [Operate a Federation](https://www.chio.computer/docs/federation/operations.md): Run a federation day to day: rotation deadlines, directory reloads, checkpoint cadence and follower catch-up, treaty scope maintenance, and the metric families and spans to watch.
- [Operator Identity & Key Bindings](https://www.chio.computer/docs/federation/operator-identity.md): The three identities a federation peer presents, which lane binds which one, where each binding is pinned, and the refusal each mismatch produces.
- [Federation](https://www.chio.computer/docs/federation/overview.md): Connect independent Chio operators through explicit peer trust, delegated authority, and signed evidence. Follow the protocol, trust, transport, and revocation contracts for that relationship.
- [Peer Handshake](https://www.chio.computer/docs/federation/peer-handshake.md): Prove a partner kernel holds the key its card pinned with a signed challenge and response, negotiate a conformance tier, set a rotation deadline, and read every refusal.
- [Peer Pins & Trust Bundles](https://www.chio.computer/docs/federation/peer-pins.md): The verifier-owned inputs: peer, vendor, and action-class pins, the verification context, and the strict trust bundle joining them with a profile, intersection, disclosure policy, and checkpoint.
- [Federation Model](https://www.chio.computer/docs/federation/protocol.md): The relationship between independent operators: two trust stores, two federation paths, the artifact families that cross the boundary, and where each contract is documented.
- [Provider Registry & SCIM](https://www.chio.computer/docs/federation/provider-registry.md): The enterprise provider records the MCP edge and the trust service share, their four kinds, provenance and trust-boundary fields, subject mapping, and the SCIM lifecycle registry.
- [Receipt Lineage & Buyer Packets](https://www.chio.computer/docs/federation/receipt-lineage.md): The five inputs a buyer packet binds, what the hash-only verifier can establish, why a DSSE binding stays unresolved without bytes, and the twelve roles a full review needs.
- [Federation Refusal Codes](https://www.chio.computer/docs/federation/refusal-codes.md): Every federation refusal by the artifact it came from: treaty and ladder codes, handshake, verifier, authority, directory, and transport errors, each with the page that explains it and the repair.
- [Reputation Clearing](https://www.chio.computer/docs/federation/reputation-clearing.md): Clear shared reputation inputs from several operators under local weighting and sybil controls, so no issuer becomes an oracle and no blocking event stands uncorroborated.
- [Revocation Checkpoints](https://www.chio.computer/docs/federation/revocation-checkpoints.md): Publish a signed revocation checkpoint from a revocation authority, advance its epoch monotonically, and carry it into the verifier trust bundle a buyer reads.
- [Revocation Oracle](https://www.chio.computer/docs/federation/revocation-oracle.md): Publish signed revocation commitments, verify roots across operators, and connect authenticated history to a locally maintained kernel snapshot.
- [Transport Directory](https://www.chio.computer/docs/federation/transport-directory.md): The issuer-signed directory that binds each peer's kernel id, passport key, and transport endpoint, the ordered checks a bundle passes at load, and how a running node reloads it.
- [Transport Lanes](https://www.chio.computer/docs/federation/transport-lanes.md): The five iroh lanes that carry federation traffic, one ALPN each: which identity each binds, which chio-federation verifier runs above it, and a runnable example per lane.
- [Limits & Backpressure](https://www.chio.computer/docs/federation/transport-limits.md): Per-lane and per-peer accept limits, per-phase timeouts, the busy and lagged signals, and the metric families and spans an operator watches on the iroh transport.
- [Treaties](https://www.chio.computer/docs/federation/treaties.md): Compose independent governance requirements into a shared cross-boundary action contract, inspect its admission evidence, and maintain the verifier’s trusted inputs.
- [Trust Activation Exchange](https://www.chio.computer/docs/federation/trust-activation.md): The explicit exchange that carries a remote trust activation across operators, the import controls that keep it visibility-only until the receiver activates locally, and the refusals.
- [Evidence Exchange Walkthrough](https://www.chio.computer/docs/federation/walkthrough.md): Run a two-operator evidence exchange: export receipts under a signed sharing policy, import them with their origin intact, and issue downstream from the imported capability.
- [Aeneas Pipeline](https://www.chio.computer/docs/formal/aeneas.md): Trace Chio's selected Rust decision helpers through authenticated extraction, generated Lean snapshots and checked equivalence to an explicit model.
- [Chio Arena](https://www.chio.computer/docs/formal/arena.md): A deterministic scenario runner and co-evolution harness that drives ChioKernel through TOML scenarios and promotes what it finds into corpora.
- [Assumptions & TCB](https://www.chio.computer/docs/formal/assumptions.md): Inspect the external contracts behind Chio's formal security claims, their property mappings and what an operator must investigate when a contract fails.
- [Constant-Time Tests](https://www.chio.computer/docs/formal/constant-time.md): Understand Chio's timing harnesses, choose the measured input classes, run a release binary and distinguish a timing signal from a setup failure.
- [Creusot Contracts](https://www.chio.computer/docs/formal/creusot.md): Read Chio's deductive Rust contracts, follow the shared decision bodies into the verifier, and distinguish body-linkage checks from completed solver proofs.
- [Differential Tests](https://www.chio.computer/docs/formal/diff-tests.md): Compare Chio authority decisions, canonical bytes and treaty predicates with separate implementations, then inspect the inputs and execution behind each result.
- [Verification Evidence](https://www.chio.computer/docs/formal/evidence.md): Read the property inventory, compare verification methods, and reproduce source-bound assurance reports.
- [Formal Failure Modes](https://www.chio.computer/docs/formal/failure-modes.md): Diagnose a failed Chio verification gate: separate counterexamples, toolchain failures, snapshot drift, model bounds and inconsistent proof reports without weakening the property under test.
- [Fuzz Infrastructure](https://www.chio.computer/docs/formal/fuzz.md): Explore Chio's parser, verifier, policy and market-protocol fuzz targets; understand their assertions, reproduce a run and retain useful regressions.
- [Kani Harnesses](https://www.chio.computer/docs/formal/kani.md): Read Chio's Rust verification harnesses through their inputs, assertions, compile configuration and unwind settings, then run the selected public lane.
- [Lean 4 Proofs](https://www.chio.computer/docs/formal/lean4.md): Read Chio's machine-checked security statements, inspect their definitions and assumptions, and connect model proofs to the evidence for Rust execution.
- [Mutation Testing](https://www.chio.computer/docs/formal/mutation-testing.md): Challenge Chio's tests with changed implementations; inspect mutation discovery, interpret the recorded baseline and reproduce the selected test scope.
- [Formal Assurance](https://www.chio.computer/docs/formal/overview.md): Follow a concrete authority rule from its security property to production Rust and machine-checked evidence, then inspect the assumptions your deployment must retain.
- [P1: Capability Monotonicity](https://www.chio.computer/docs/formal/p1-tour.md): See how a delegated scope preserves parent authority, then trace Chio's P1 claim through its Lean statement, generated scalar equivalence and Rust verification evidence.
- [Research Papers](https://www.chio.computer/docs/formal/papers.md): The paper sources in the Chio repository, the Lean theorems and Rust symbols each one names, and the claim boundary each one records.
- [Formal Quickstart](https://www.chio.computer/docs/formal/quickstart.md): Check the formal evidence the Chio release you run carries, read each verification lane at its scope, and keep the signed proof report with the claim you cite.
- [Theorem Inventory](https://www.chio.computer/docs/formal/theorem-inventory.md): Find Chio's registered Lean theorems by identifier, property, claim class or source file. Inspect the statement, model boundary and implementation link behind a security claim.
- [TLA+ Specs](https://www.chio.computer/docs/formal/tla.md): The Chio TLA+ and Apalache models: revocation propagation, distributed root gossip, the post-admission drop lifecycle, delegation-depth bounds, and the kernel-state invariant subset.
- [Requests & Action Classification](https://www.chio.computer/docs/guard-platform/actions.md): Connect tool names and arguments to the actions Chio guards inspect. Understand classification, malformed inputs, generic tool calls, and integration tests.
- [Advisory Guards](https://www.chio.computer/docs/guard-platform/advisory.md): Reference for AdvisoryGuard, AdvisorySignal, AdvisoryPipeline, and PromotionPolicy. Advisory signals are recorded on receipts and can be promoted to a deny.
- [Approval & HITL](https://www.chio.computer/docs/guard-platform/approval.md): ApprovalGuard, ApprovalStore, ApprovalChannel, and GovernedApprovalToken. These components pause constrained calls and validate the signed approval used to resume them.
- [Crate Map](https://www.chio.computer/docs/guard-platform/architecture.md)
- [Capability reference](https://www.chio.computer/docs/guard-platform/capabilities.md): An annotated signed capability, exact field contracts, and constraints grouped by what they govern and how they are enforced.
- [Guard Catalog](https://www.chio.computer/docs/guard-platform/catalog.md): Choose Chio guards by accepted inputs, evaluation stage, default installation, dependencies, and outcome. Find the configuration and working example for your policy.
- [chio.yaml Configuration](https://www.chio.computer/docs/guard-platform/config.md): Reference for chio.yaml: kernel, adapters, edges, receipts, logging, telemetry, guards, and wasm_guards sections, plus environment variable interpolation and validation rules.
- [Core & Shell](https://www.chio.computer/docs/guard-platform/core-and-shell.md): How Chio shares portable Rust authority checks across hosts while keeping live state, execution, and evidence persistence explicit.
- [Computer Use Guards](https://www.chio.computer/docs/guard-platform/cua.md): Reference for Computer Use Agent (CUA) guards: action allowlists, input injection, remote desktop, browser automation, and embedding anomaly checks.
- [Data-Layer Guards](https://www.chio.computer/docs/guard-platform/data-layer.md): SqlQueryGuard, VectorDbGuard, QueryResultGuard, and WarehouseCostGuard from chio-data-guards: dialect-aware SQL parsing, vector collection allowlists, post-query column redaction, and dry-run cost ceilings.
- [Default Pipelines](https://www.chio.computer/docs/guard-platform/default-pipeline.md): Compare the library default and runtime guard profile: installed controls, registration order, explicit additions, and output hooks.
- [Delegation & Attenuation](https://www.chio.computer/docs/guard-platform/delegation.md): Pass bounded authority to another agent: verify grant subsets, parent bindings, delegated shares, and the supported token-chain shapes.
- [Guard Evidence](https://www.chio.computer/docs/guard-platform/evidence.md): Carry guard decisions into signed, inspectable records: evidence fields, producers, receipt assembly, runtime coupling, and downstream interpretation.
- [External Guard Adapters](https://www.chio.computer/docs/guard-platform/external-adapters.md): AsyncGuardAdapter reference: circuit breaking, caching, rate limiting, retries, the ScopedAsyncGuard bridge, and external guard providers.
- [Fail-Closed Semantics](https://www.chio.computer/docs/guard-platform/fail-closed.md): How guard errors, timeouts, lock failures, and parse failures become denied receipts; includes panic handling and advisory behavior.
- [Failure & Recovery](https://www.chio.computer/docs/guard-platform/failure-recovery.md): Operator runbook for a degraded guard fleet: WASM hot-reload and canary rollback, the digest blocklist, circuit-breaker recovery, session-journal loss, and a worked adapter tuning example.
- [Filesystem Guards](https://www.chio.computer/docs/guard-platform/filesystem.md): Reference for the four chio-guards filesystem guards: ForbiddenPathGuard, PathAllowlistGuard, SecretLeakGuard, and PatchIntegrityGuard, including defaults and configuration.
- [HushSpec Policy Format](https://www.chio.computer/docs/guard-platform/hushspec.md): Author executable policy for Chio: complete YAML examples, inheritance you can inspect, and searchable fields, defaults and compiler boundaries.
- [Jailbreak & Injection Guards](https://www.chio.computer/docs/guard-platform/jailbreak.md): Reference for the opt-in JailbreakGuard and PromptInjectionGuard, including detector weights, thresholds, fingerprint deduplication, and signal IDs.
- [Memory Governance](https://www.chio.computer/docs/guard-platform/memory.md): MemoryGovernanceGuard in chio-guards: the ordered write gates, the store allowlist union, the retention ceiling, the size cap, deny patterns, the per-session counter, and the retraction profile that admits only live findings on read.
- [Network Guards](https://www.chio.computer/docs/guard-platform/network.md): Reference for the chio-guards network guards: EgressAllowlistGuard and InternalNetworkGuard, including defaults, blocked address classes, and DNS-rebinding heuristics.
- [Kernel Overview](https://www.chio.computer/docs/guard-platform/overview.md): The Rust authority and policy engine at the center of Chio: portable decisions, hosted execution, composable guards, and signed evidence.
- [Performance & Tuning](https://www.chio.computer/docs/guard-platform/performance.md): Guard latency classes, throughput bounds, a measured receipt-store footprint, the four bottlenecks that dominate a deployment, and the chio.yaml knobs that move them.
- [Pipelines & Composition](https://www.chio.computer/docs/guard-platform/pipelines.md): Compose Chio input guards, advisory findings, output hooks, and external services with explicit ordering, evidence, and failure behavior.
- [Policy Compilation](https://www.chio.computer/docs/guard-platform/policy-compile.md): Turn HushSpec into configured guards, output checks and capability scope. Run a complete policy inspector, change its rules and examine the compiled result.
- [Portable Kernel Core](https://www.chio.computer/docs/guard-platform/portable-core.md): One decision core cross-compiled to a desktop shell, browser wasm, mobile UniFFI, and a narrow C ABI, with Clock and Rng as the only platform seams and a scripted no_std build gate.
- [Rate Limit Guards](https://www.chio.computer/docs/guard-platform/rate-limit.md): Cap how often an authorized caller acts with VelocityGuard (per grant, with declared spend) and AgentVelocityGuard (per agent and per agent and capability): token-bucket arithmetic, bounded bucket tables, and composition.
- [Receipt Contract](https://www.chio.computer/docs/guard-platform/receipts.md)
- [Response Sanitization](https://www.chio.computer/docs/guard-platform/sanitization.md): ContentReviewGuard and ResponseSanitizationGuard refuse sensitive outbound content before dispatch; OutputSanitizer redacts secrets and personal data in tool results with Mask, Fingerprint, Drop, Tokenize, Partial, TypeLabel, or Keep.
- [Scope Matching](https://www.chio.computer/docs/guard-platform/scope-matching.md): Resolve a request against its grants, understand portable constraint support, and trace the selected grant into guards, budgets, and receipt attribution.
- [Session-Aware Guards](https://www.chio.computer/docs/guard-platform/session.md): DataFlowGuard, BehavioralSequenceGuard, and BehavioralProfileGuard read what a session already did: the shared session journal, cumulative fields that survive ring eviction, byte ceilings, tool-order rules, and EMA call-rate baselines.
- [Shell & Code Guards](https://www.chio.computer/docs/guard-platform/shell-code.md): ShellCommandGuard, CodeExecutionGuard, and PatchIntegrityGuard in chio-guards: forbidden command-line patterns, language allowlists, dangerous-module detection, and patch/diff checks.
- [Testing Guards & Policies](https://www.chio.computer/docs/guard-platform/testing.md): Test a document guard, distinguish policy preferences from requirements, and verify configured enforcement with complete runnable examples.
- [Tool Access Guards](https://www.chio.computer/docs/guard-platform/tool-access.md): Reference for McpToolGuard: name-based allow and block lists, serialized argument-size limits, defaults, evaluation order, and failures.
- [The Guard Trait](https://www.chio.computer/docs/guard-platform/trait.md): Anatomy of a Chio guard: the sync Guard trait and GuardDecision, GuardContext, ToolAction, the narrower portable-core variant, and the three-valued Verdict enum.
- [Verdicts & Approval](https://www.chio.computer/docs/guard-platform/verdicts.md): Allow, Deny, and PendingApproval. The portable core declares the third value, never emits it, and treats a sync guard that returns it as a fail-closed deny, so only the hosted shell can mint it.
- [Verified Core Boundary](https://www.chio.computer/docs/guard-platform/verified-core.md)
- [WASM Guard Runtime](https://www.chio.computer/docs/guard-platform/wasm.md): Author guards as WebAssembly modules against the chio-wasm-guards host: the ABI, the memory model, host imports, the manifest, signing, reloads, and a worked example built and packed end to end.
- [Agent Passport](https://www.chio.computer/docs/guides/agent-passport.md): Agent credentials for cross-organizational trust, including DID identifiers, reputation scores, federation, and capability binding.
- [Add API Middleware](https://www.chio.computer/docs/guides/api-middleware.md): Connect your framework to a Chio evaluator at the request boundary.
- [Audit the Pricing Tools](https://www.chio.computer/docs/guides/audit-document-app.md): Find the pricing tools' two refusals in their receipt store and export the four signed records for review.
- [Authorize an ordered tool workflow](https://www.chio.computer/docs/guides/authorize-tool-workflow.md): Read an order, quote it, and publish the approved price in a fixed order through a Chio host, with a receipt for every tool call and a signed workflow receipt.
- [Bind Workload Identity](https://www.chio.computer/docs/guides/bind-workload-identity.md): Require a payments workload and accepted runtime assurance, issue constrained authority, and inspect the identity recorded in execution evidence.
- [Bootstrap Federated Trust](https://www.chio.computer/docs/guides/bootstrap-federated-trust.md): Establish cross-kernel trust with pinned peer keys, challenge envelopes, bilateral co-signing, and verification.
- [Bridge OpenAPI to MCP](https://www.chio.computer/docs/guides/bridge-openapi-to-mcp.md): Build a Chio-governed MCP tool server from an OpenAPI 3 specification. Tool definitions, side-effect classification, and receipts derive from the specification.
- [Bridge Between Protocols](https://www.chio.computer/docs/guides/bridge-protocols.md): Bridge agents and tools that use A2A, ACP, MCP, or OpenAI while preserving capability scope and signed receipt lineage.
- [Run the Chio Kernel in the Browser](https://www.chio.computer/docs/guides/browser-kernel.md): Compile the Chio kernel to WebAssembly for capability verification, evaluation, and receipt signing in a browser tab.
- [Budgets & Metering](https://www.chio.computer/docs/guides/budgets.md): Configure capability-token budget limits, set tool prices, inspect financial receipts, handle overruns, and monitor consumption.
- [Serve two customers with tenant-scoped receipts](https://www.chio.computer/docs/guides/build-tenant-scoped-service.md): Authenticate Harbor Goods and Ostrander, attribute each quote to the verified tenant, and serve isolated receipt views and exports from one pricing service.
- [Choose an agent integration](https://www.chio.computer/docs/guides/choose-agent-integration.md): Choose a native agent process, MCP bridge or framework adapter by the recovery and authority boundary your application needs.
- [Connect an Application](https://www.chio.computer/docs/guides/connect-an-application.md): Run the pricing service in your own stack and put the kernel in front of it, under the grants and history you already have.
- [Connect Hermes](https://www.chio.computer/docs/guides/connect-hermes.md): Register Chio as an MCP server in Hermes, read project files through the kernel, and find the receipts; or add the chio toolset plugin backed by a sidecar.
- [Credit & Underwriting](https://www.chio.computer/docs/guides/credit-underwriting.md): Guide to the Chio credit system: credit facilities, bonds, underwriting decisions, bonded execution for autonomous agents, the capital book, liability market, and open market.
- [Custom Guards](https://www.chio.computer/docs/guides/custom-guards.md): Build, sign, install and run your own WASM policy rule. Continue a complete document application through release verification and trusted loading.
- [Delegate Between Agents](https://www.chio.computer/docs/guides/delegate-between-agents.md): Let the fixer hand a narrower grant to a tester for the flaky test in issue #416, watch the kernel refuse the tester's write, and revoke the whole chain.
- [Editor Integrations](https://www.chio.computer/docs/guides/editor-integrations.md): Use VS Code or Zed to author HushSpec policies with diagnostics, completion, hover, and go-to-definition from chio-lsp.
- [Export Billing Records](https://www.chio.computer/docs/guides/export-billing-records.md): Export metered receipts for billing, reconcile the result with the receipt log, and send it to an invoicing system.
- [Export and verify evidence](https://www.chio.computer/docs/guides/export-evidence.md): Export receipts from your current application, verify the package offline, and detect modified evidence.
- [External Guards](https://www.chio.computer/docs/guides/external-guards.md): Add Bedrock, Azure, Vertex, Safe Browsing, VirusTotal, or Snyk checks to the fail-closed guard pipeline.
- [Connect a coding agent](https://www.chio.computer/docs/guides/govern-a-coding-agent.md): Connect Claude Code to the pricing project's file tools through Chio, watch the kernel admit a read and refuse a secret, then inspect both receipts.
- [Govern Any Provider's Tool Calls](https://www.chio.computer/docs/guides/govern-any-provider-tool-calls.md): Route Anthropic Messages and Amazon Bedrock Converse tool calls through Chio and record signed receipts.
- [Govern Database Queries](https://www.chio.computer/docs/guides/govern-database-queries.md): Use Chio data guards to enforce table and collection allowlists, warehouse cost caps, and result redaction for database calls.
- [Govern OpenAI Tool Calls](https://www.chio.computer/docs/guides/govern-openai-tool-calls.md): Give OpenAI agents capability-scoped execution through Chio, return tool results and refusals, and retain signed kernel evidence.
- [Run a governed coding task](https://www.chio.computer/docs/guides/governed-coding-task.md): Import one committed repository scope, run a bounded coding process and independently verify its patch and original receipts.
- [Run a governed coding task on Rust](https://www.chio.computer/docs/guides/governed-rust-coding-task.md): Repair a selected Rust repository, export a scoped patch and verify it in a separate checkout before running Cargo tests.
- [Handle tool outcomes: refusal, failure, and cancellation](https://www.chio.computer/docs/guides/handle-tool-outcomes.md): Run a repricing job and tell a refusal from a failed database, a cancellation, and a price sheet that published but lost its acknowledgement.
- [Add Chio Middleware to Your HTTP Framework](https://www.chio.computer/docs/guides/http-framework-middleware.md): Run Larkfield's pricing service with an embedded Rust evaluator or a framework adapter, then inspect the decision and change its policy.
- [Inherit & Merge Policies](https://www.chio.computer/docs/guides/inherit-merge-policies.md): Compose HushSpec policies from team baselines, project overrides, and environment settings, then inspect the effective policy.
- [Migrate from MCP to Chio](https://www.chio.computer/docs/guides/migrate-from-mcp.md): Add signed receipts and policy enforcement between an existing MCP client and server without changing either MCP implementation.
- [Native Tool Server](https://www.chio.computer/docs/guides/native-tool-server.md): Build a native Chio tool server in Rust using NativeChioServiceBuilder, with typed schemas, pricing, and manifest signing.
- [Passkey-Issued Browser Capabilities](https://www.chio.computer/docs/guides/passkey-capabilities.md): Hardware-custody issuance for browser agents: a WebAuthn assertion is exchanged for a short-lived, audience-pinned capability signed server-side, with zero key material in the browser.
- [HushSpec policy patterns](https://www.chio.computer/docs/guides/policy-patterns.md): Configure guards, compose HushSpec policies, test decisions, and diagnose failures.
- [Protect an API](https://www.chio.computer/docs/guides/protect-an-api.md): Put Chio in front of Larkfield's pricing API, issue a quote under a grant, and revoke the grant.
- [Proxy an AG-UI Event Stream](https://www.chio.computer/docs/guides/proxy-ag-ui-events.md): Place Chio between an agent and a browser client that consumes AG-UI events. It classifies UI events, checks capability scopes before forwarding, and signs receipts over SSE or WebSocket.
- [Inspect Your Receipts](https://www.chio.computer/docs/guides/query-audit-receipts.md): Find the fixer's refusal in your project's history, read why it was refused, tell an execution from a preflight check, and verify the exported evidence offline.
- [Query Receipts with SDKs](https://www.chio.computer/docs/guides/query-receipts-with-sdks.md): Collect receipt pages in Python or TypeScript for a dashboard or scheduled job.
- [Require human approval](https://www.chio.computer/docs/guides/require-human-approval.md): Let a pricing agent propose a deep discount and have Mara Okafor approve the exact price change before the kernel admits it.
- [Restore an MCP session](https://www.chio.computer/docs/guides/restore-mcp-session.md): Restart Chio's HTTP MCP edge in front of the pricing server and reconnect a client to its saved session, under the policy and revocations in force after the restart.
- [Rotate Keys & Revoke](https://www.chio.computer/docs/guides/rotate-keys-revoke.md): Operator runbook for rotating signing keys and revoking Agent Passports, capability tokens, and delegated capabilities.
- [Run a Cognition Market](https://www.chio.computer/docs/guides/run-a-cognition-market.md): Run a venue for verified invoice repairs: replay a seller’s fix, verify its evidence, buy the committed patch, and reconcile the local capture.
- [Build a Rust resource service](https://www.chio.computer/docs/guides/rust-resource-service.md): Accept a report only from its current assigned caller, and retain the original mutation outcome in the same SQLite transaction.
- [Build Systems in Rust](https://www.chio.computer/docs/guides/rust-systems.md): Run six reference programs and examine ownership, authority, bounded work, durable publication and independently verified evidence.
- [Settlement](https://www.chio.computer/docs/guides/settlement.md): Guide to settling tool invocation costs with payment adapters, on-chain escrow, checkpoint anchoring, price checks, and finality.
- [Share a worker budget](https://www.chio.computer/docs/guides/share-worker-budget.md): Run three concurrent repricing workers against one durable USD 2.00 allowance, then read exhaustion, restart, cancellation, and interrupted work.
- [Tool Pricing](https://www.chio.computer/docs/guides/tool-pricing.md): Price a useful tool service, authorize its spending, and trace the recorded charge to the same call.
- [Trace Delegated Work](https://www.chio.computer/docs/guides/trace-delegated-work.md): Inspect a research-workflow study, follow delegated authority into signed records, and verify how changing receipt bytes affects the evidence.
- [Verify Receipts Offline](https://www.chio.computer/docs/guides/verify-receipts-offline.md): Verify your application’s signed decisions against a trusted key, then inspect evidence-package coverage.
- [Wrap an ACP Server](https://www.chio.computer/docs/guides/wrap-acp-server.md): Embed Chio before an ACP server to guard JSON-RPC methods and emit signed tool-call receipts.
- [Wrap an MCP Server](https://www.chio.computer/docs/guides/wrap-mcp-server.md): Wrap an MCP server with Chio policy evaluation, guard checks, and signed receipts without modifying the server.
- [Write a Policy](https://www.chio.computer/docs/guides/write-a-policy.md): Add a rule that narrows every grant, watch it refuse a poisoned fetch in issue #415, and carry rules to your own tool server.
- [Installation](https://www.chio.computer/docs/installation.md): Install the Chio CLI with one command, then add the SDK for TypeScript, Python, or Rust.
- [Install an SDK](https://www.chio.computer/docs/installation/sdks.md): Install the Chio SDK for your language from its registry, make a first call against the Quickstart computer, and add a framework adapter.
- [A2A Adapter](https://www.chio.computer/docs/integrations/a2a-adapter.md): Wrap A2A (Agent-to-Agent) servers behind the Chio kernel so cross-agent calls receive capability validation and signed receipts.
- [AWS Bedrock Marketplace](https://www.chio.computer/docs/integrations/aws-bedrock-marketplace.md): Use an AWS Marketplace SaaS listing to govern Amazon Bedrock through the Chio control plane with IAM, entitlement checks, and signed receipts.
- [AWS Lambda](https://www.chio.computer/docs/integrations/aws-lambda.md): Run the Chio extension beside a Lambda function so each governed operation is evaluated before the handler body runs, with receipts flushed to DynamoDB.
- [Chainlink Oracles](https://www.chio.computer/docs/integrations/chainlink.md): Convert Chio budgets across currencies with Chainlink and Pyth prices, applying freshness, confidence, and sequencer-health checks.
- [Claude Agent SDK](https://www.chio.computer/docs/integrations/claude-agent-sdk.md): Wrap Claude Agent SDK custom tools with chioTool so the Chio kernel admits each call under a signed capability before the handler runs.
- [Envoy ext_authz](https://www.chio.computer/docs/integrations/envoy-ext-authz.md): Use Chio as an external authorization backend for Envoy, with documented gRPC integration for Istio and standalone Envoy.
- [Kafka](https://www.chio.computer/docs/integrations/kafka.md): Evaluate Kafka consumer events with Chio, write receipts transactionally, and send denied events to a dead-letter queue.
- [LangGraph](https://www.chio.computer/docs/integrations/langgraph.md): Execute LangGraph tools through a durable Chio process or evaluate existing graph node dispatches with the sidecar adapter.
- [Model-call recovery](https://www.chio.computer/docs/integrations/model-call-recovery.md): Journal a complete AI SDK provider response before any of its tool calls execute, then recover the original Chio operations.
- [OpenAI Agents SDK](https://www.chio.computer/docs/integrations/openai-agents-sdk.md): Wrap OpenAI Agents SDK tools with chioTool so the Chio kernel admits each call under a signed capability before execute runs.
- [Prefect](https://www.chio.computer/docs/integrations/prefect.md): Evaluate Prefect tasks and flows with Chio, restrict task scope at the flow boundary, and emit receipt events.
- [Settlement](https://www.chio.computer/docs/integrations/settlement.md): Settle Chio receipt obligations on EVM chains, with Base as the shipped reference and bounded local Solana verification.
- [Temporal](https://www.chio.computer/docs/integrations/temporal.md): Enforce Chio capabilities on Temporal activities, scope a workflow with WorkflowGrant, and aggregate activity receipts in WorkflowReceipt.
- [x402 Payments](https://www.chio.computer/docs/integrations/x402.md): Govern per-request stablecoin payments over HTTP 402 with Chio authorization and receipts that bind payments to capabilities.
- [Megastart](https://www.chio.computer/docs/megastart.md): Run a local system in which your own agents research, repair, and review a failing project under one mission grant, then approve the exact result.
- [Megastart reference](https://www.chio.computer/docs/megastart/reference.md): Build a Rust system of research, implementation, and review swarms with shared authority, persistent capacity, recoverable work, and explicitly approved publication.
- [Mercury](https://www.chio.computer/docs/mercury.md): Mercury produces signed evidence about AI-assisted execution workflow changes in regulated finance.
- [Admin API](https://www.chio.computer/docs/node/admin.md): Authenticate to the HTTP edge, find an endpoint, inspect a response, and understand admin operations.
- [Approval Store & Channels](https://www.chio.computer/docs/node/approval-store.md): Persist human decisions and token consumption across restarts. Trace the request, delivery channel, and atomic resolution boundary.
- [Backpressure & Limits](https://www.chio.computer/docs/node/backpressure.md): Bound concurrent connections, shed excess HTTP requests, and tell HTTP status refusals apart from the kernel's signed memory-shed denials.
- [Budget Store](https://www.chio.computer/docs/node/budget-store.md): Reserve spending authority before execution, record what was spent, and recover without silently charging a retry twice.
- [Listeners & Edges](https://www.chio.computer/docs/node/edges.md): Expose governed tools through MCP, A2A, and ACP. Keep capability authority and signed evidence intact as requests cross protocol boundaries.
- [Node Egress Contract](https://www.chio.computer/docs/node/egress.md): Constrain a node's own outbound HTTP through URL policy, validating DNS resolvers, checked redirects, and bounded response bodies, and see which client paths bind the checks to the socket.
- [Embedded Node](https://www.chio.computer/docs/node/embedded.md): Run Chio inside a compatible HTTP application. Bind requests to authority, gate handler execution, and understand the evidence before and after an effect.
- [Guard Supply Chain](https://www.chio.computer/docs/node/guard-registry.md): Identify guard artifacts by digest, distinguish verification reports from load admission, and preserve module ownership across a runtime epoch swap.
- [Health & Readiness](https://www.chio.computer/docs/node/health.md): Choose the right health check, diagnose a node that refuses work, and distinguish process availability from storage and writer readiness.
- [Node Lifecycle](https://www.chio.computer/docs/node/lifecycle.md): Stop a Chio service, size its drain window, and verify what completed before restart. Handle forced shutdown without losing track of possible effects.
- [Remote MCP Edge](https://www.chio.computer/docs/node/mcp-edge.md): Serve governed MCP tools over HTTP with isolated session kernels, configurable authorization, persistent admission state, and inspectable execution evidence.
- [Node Overview](https://www.chio.computer/docs/node/overview.md): Deploy Chio as a local tool gateway, a remote service, or part of your application. Understand the process and state around the Rust kernel.
- [Node Preflight](https://www.chio.computer/docs/node/preflight.md): Run Chio doctor, understand warnings and skipped checks, and decide what to verify before starting a service.
- [Retention & Archive](https://www.chio.computer/docs/node/retention.md): Keep a long-lived node's live database manageable while preserving inspectable evidence. Archive verified receipt-log prefixes and retain their verification path.
- [Revocation Store](https://www.chio.computer/docs/node/revocation-store.md): Withdraw delegated authority, preserve revocation across restarts, and understand which observation guarantees a budget admission can use.
- [Node Runtime Contract](https://www.chio.computer/docs/node/runtime-contract.md): Store ownership, serving leases, boot order, and the obligations of a kernel-hosting process.
- [Session Lifecycle](https://www.chio.computer/docs/node/sessions.md): Keep MCP conversation continuity under explicit lifecycle and authentication controls. Understand idle expiry, terminal records, and validated restoration after restart.
- [Node State on Disk](https://www.chio.computer/docs/node/state.md): Keep authority and evidence durable across process restarts. Understand the database boundaries, write paths, and checks that refuse stale or incompatible state.
- [Node Upgrade](https://www.chio.computer/docs/node/upgrade.md): Qualify a candidate, stop writes, preserve recovery state, and verify the restarted deployment before reopening traffic.
- [Introduction](https://www.chio.computer/docs.md): Build agentic operating systems around Chio: a shared Rust kernel for authority, constrained delegation, execution admission, and signed decision records.
- [Component Responsibilities](https://www.chio.computer/docs/platform/filing-rule.md): Identify which component owns a decision, a durable agent, local storage, coordinated state, derived authority, or a peer relationship.
- [Metric Families](https://www.chio.computer/docs/platform/metrics.md): Every metric family the workspace registry declares, grouped by name prefix under the Platform section that owns it, with kind, labels, buckets, and help text read at the documentation pin.
- [Platform Overview](https://www.chio.computer/docs/platform.md): Understand how Chio's Rust kernel, nodes, clusters, swarms, and federation fit together in an agentic operating system.
- [Spec-to-Crate Index](https://www.chio.computer/docs/platform/spec-index.md): Each normative specification in the Chio source, the reference page that renders it, and the crate that implements it, so a reader can move from a rule to its code in one step.
- [Calls and recovery](https://www.chio.computer/docs/processes/calls-recovery.md): Keep stable operation keys, recover known results and refuse unsafe redispatch after an unknown effect.
- [Checkpoints and state](https://www.chio.computer/docs/processes/checkpoints.md): Use compare-and-swap checkpoints and immutable process blobs without mistaking application state for effect evidence.
- [Embed a process host in Rust](https://www.chio.computer/docs/processes/embedded-host.md): Own the kernel and durable process runtime inside a Rust application while workers keep using a narrow authenticated socket API.
- [Host and worker protocol](https://www.chio.computer/docs/processes/host-workers.md): Initialize a process host, issue private worker connections and call governed tools from Python or Node.
- [Process identity and authority](https://www.chio.computer/docs/processes/identity.md): Understand immutable process trees, attenuated child authority, shared ceilings and cancellation.
- [Write workers in Rust or TypeScript](https://www.chio.computer/docs/processes/languages.md): Run the same report application with compiled Rust workers or typed TypeScript workers, then recover the original handoff after a worker exits.
- [Mailboxes and shared work](https://www.chio.computer/docs/processes/mailboxes.md): Send durable messages with separate endpoint grants, claim leases and explicit acknowledgement.
- [Operate and move a host](https://www.chio.computer/docs/processes/operations.md): Inspect attempts and application state, cancel a process, rotate a connection and relocate a durable host.
- [Agent processes](https://www.chio.computer/docs/processes.md): Give agents persistent identity, bounded authority and recoverable work across worker restarts.
- [Run your first process](https://www.chio.computer/docs/processes/quickstart.md): Send a batch from Python to Node, save its result, and recover the same handoff after a worker stops.
- [Shared resource ownership](https://www.chio.computer/docs/processes/shared-resources.md): Reject superseded workers at the resource mutation boundary using the kernel-selected caller.
- [Supervise an application](https://www.chio.computer/docs/processes/supervision.md): Declare worker dependencies, bounded attempts and failure policy in a durable process run plan.
- [Proof Room](https://www.chio.computer/docs/proof-room.md): The chio-proof-room server recomputes bundle reports from source inputs before serving a dashboard.
- [Quickstart](https://www.chio.computer/docs/quickstart.md): Govern your own agents: grant one a slice of your project, read the signed refusal it earns, merge its fix, and add a rule no grant can override.
- [Work With Their Agents](https://www.chio.computer/docs/quickstart/partners.md): Let your agents work with another operator's agents: pair two kernels over iroh, agree on a treaty, share a mailbox and signals, merge with both signatures, and revoke.
- [Serve Other Agents](https://www.chio.computer/docs/quickstart/services.md): Publish your project as a service that agents you do not run can call, each under its own grant, with your approval for the calls that matter.
- [Bindings API](https://www.chio.computer/docs/reference/bindings-api.md): The shared low-level contract for Chio SDKs: canonical JSON, SHA-256, Ed25519, receipt and capability verification, signed manifests, the C ABI, and cross-language conformance.
- [Bridges](https://www.chio.computer/docs/reference/bridges.md): The OpenAPI-to-MCP bridge, the A2A and ACP edges, and the OpenAI adapter of BRIDGES.md 1.0: tool mapping, invocation flow, fidelity, and receipts.
- [chio agent · Chio CLI](https://www.chio.computer/docs/reference/cli/agent.md): Create a demonstration caller that holds its own key, then drive traffic from it against a service you published.
- [chio anchor · Chio CLI](https://www.chio.computer/docs/reference/cli/anchor.md): Anchor receipt checkpoints to public ledgers, then prove and verify one receipt's inclusion offline.
- [chio api · Chio CLI](https://www.chio.computer/docs/reference/cli/api.md): Protect an existing HTTP API with a sidecar built from its OpenAPI document, so each request is admitted before it reaches your code.
- [chio approvals · Chio CLI](https://www.chio.computer/docs/reference/cli/approvals.md): List the approval requests waiting for a person, each with its caller, the exact request it binds, and how long it has waited.
- [chio approve · Chio CLI](https://www.chio.computer/docs/reference/cli/approve.md): Sign an approval for one pending request with your operator identity; the signature binds that request's hash and admits only that call.
- [chio arena · Chio CLI](https://www.chio.computer/docs/reference/cli/arena.md): Run adversarial scenarios against the kernel, replay the receipt bundles they write, and evolve adversaries between runs.
- [chio attest · Chio CLI](https://www.chio.computer/docs/reference/cli/attest.md): Verify offline attestation evidence: supply-chain provenance, runtime quotes, and the proof packages a buyer receives.
- [chio bind · Chio CLI](https://www.chio.computer/docs/reference/cli/bind.md): Bind a model provider under a signed model card and print the weights hash and capability set the card declares.
- [chio cert · Chio CLI](https://www.chio.computer/docs/reference/cli/cert.md): Generate, verify, and inspect ACP session compliance certificates for a recorded agent session and the receipts behind it.
- [chio certify · Chio CLI](https://www.chio.computer/docs/reference/cli/certify.md): Evaluate a conformance corpus, emit a signed certification artifact, and publish or resolve it in a certification registry.
- [chio check · Chio CLI](https://www.chio.computer/docs/reference/cli/check.md): Evaluate one tool call against a policy and print the verdict, with no subprocess and no call to the tool.
- [chio commerce · Chio CLI](https://www.chio.computer/docs/reference/cli/commerce.md): Verify commerce proof bundles and their payment evidence, produced when an optional payment-rail module records a settlement.
- [CLI Reference](https://www.chio.computer/docs/reference/cli/complete.md): Command-line reference for the Chio CLI: every subcommand with its usage line, positional arguments, options, defaults, and the flags every command accepts.
- [chio conformance · Chio CLI](https://www.chio.computer/docs/reference/cli/conformance.md): Run the cross-language conformance harness against a peer adapter, and fetch the peer adapters it runs against.
- [chio did · Chio CLI](https://www.chio.computer/docs/reference/cli/did.md): Resolve a self-certifying did:chio identifier into its DID Document to read the keys that identity controls.
- [chio doctor · Chio CLI](https://www.chio.computer/docs/reference/cli/doctor.md): Diagnose the local toolchain, guard registry, telemetry exporter, and chio.yaml, with exit codes that separate warnings from errors.
- [chio evidence · Chio CLI](https://www.chio.computer/docs/reference/cli/evidence.md): Export an evidence package from the receipt store and verify it offline against pinned partner keys, with no access to either operator.
- [chio federation · Chio CLI](https://www.chio.computer/docs/reference/cli/federation.md): Produce and verify the authority and treaty artifacts two kernels exchange when their operators cooperate across organizations.
- [chio finding · Chio CLI](https://www.chio.computer/docs/reference/cli/finding.md): Publish, search, verify, and buy findings on the cognition market, and challenge a finding whose claim you dispute.
- [chio guard · Chio CLI](https://www.chio.computer/docs/reference/cli/guard.md): Scaffold, build, test, benchmark, sign, and publish WASM guards, and install signed guard packs from a registry.
- [chio init · Chio CLI](https://www.chio.computer/docs/reference/cli/init.md): Scaffold a runnable example project with a policy, a tool server, and a governed demo flow that shows a grant and a refusal.
- [chio key · Chio CLI](https://www.chio.computer/docs/reference/cli/key.md): Create the operator identity your kernel signs with, then print its DID, its kernel key fingerprint, and where the key is held.
- [chio lineage · Chio CLI](https://www.chio.computer/docs/reference/cli/lineage.md): Walk, compare, and list the anchored roots of the lineage graph that records which grant each delegated grant came from.
- [chio mcp · Chio CLI](https://www.chio.computer/docs/reference/cli/mcp.md): Serve an MCP edge backed by the kernel over stdio or HTTP, or wrap an existing MCP server so its calls are admitted.
- [chio new · Chio CLI](https://www.chio.computer/docs/reference/cli/new.md): Create a computer, the versioned environment where a project's authority, resources, and work live, owned by your operator identity.
- [CLI Global Options](https://www.chio.computer/docs/reference/cli/options.md): Usage, persistent stores, trust-control settings, and output flags shared by Chio commands.
- [chio oracle · Chio CLI](https://www.chio.computer/docs/reference/cli/oracle.md): Read a price pair through the configured oracle exactly as the kernel does when it converts a budget.
- [CLI Reference](https://www.chio.computer/docs/reference/cli.md): Find a Chio command by task, then open its focused reference for arguments, options, defaults, and an example.
- [chio partner · Chio CLI](https://www.chio.computer/docs/reference/cli/partner.md): Add a partner from its partner card, which pins the partner's kernel key, and choose the transport the two kernels use.
- [chio passport · Chio CLI](https://www.chio.computer/docs/reference/cli/passport.md): Create, verify, and present Agent Passport bundles, and run the challenge and issuance flows a partner uses to admit them.
- [chio pheromone · Chio CLI](https://www.chio.computer/docs/reference/cli/pheromone.md): Receive, query, and relay signals, the advisory deposits agents leave to rank work, including signals that cross between partners.
- [chio policy · Chio CLI](https://www.chio.computer/docs/reference/cli/policy.md): Test a policy against a table of expected decisions, explain what it compiles to, and check how it narrows the grants issued under it.
- [chio process · Chio CLI](https://www.chio.computer/docs/reference/cli/process.md): Host durable agent processes whose identity, authority, and checkpoints survive worker restarts, then attest and verify their calls and runs.
- [chio proof · Chio CLI](https://www.chio.computer/docs/reference/cli/proof.md): Assemble, verify, explain, and serve proof bundles and Transaction Passport artifacts against trust you configure independently.
- [chio receipt · Chio CLI](https://www.chio.computer/docs/reference/cli/receipt.md): List, explain, audit, and checkpoint the signed receipts the kernel writes for each decision, refusals included.
- [chio recovery · Chio CLI](https://www.chio.computer/docs/reference/cli/recovery.md): Inspect a recovery workflow, read its signed explanation, and resume it after approval, with unknown outcomes never dispatched again.
- [chio release · Chio CLI](https://www.chio.computer/docs/reference/cli/release.md): Verify the signing identity and provenance of a Chio release, its attached evidence, and whether a node is ready to move to it.
- [chio replay · Chio CLI](https://www.chio.computer/docs/reference/cli/replay.md): Re-evaluate a captured receipt log against the current build, re-verifying every signature and recomputing the Merkle root.
- [chio reputation · Chio CLI](https://www.chio.computer/docs/reference/cli/reputation.md): Inspect and compare local reputation scorecards computed from persisted receipts and lineage state for the agents you run.
- [chio run · Chio CLI](https://www.chio.computer/docs/reference/cli/run.md): Spawn an agent as a subprocess under a policy file, so each tool call it routes through the kernel is admitted or refused.
- [chio runtime · Chio CLI](https://www.chio.computer/docs/reference/cli/runtime.md): Evaluate live-runtime admission artifacts on a local runtime: admit, orchestrate, weight peers, read signals, and run loopback operations.
- [chio security · Chio CLI](https://www.chio.computer/docs/reference/cli/security.md): Prepare and supervise the confined runtime, then run this release's enforcement suites against the installed binaries on your own host.
- [chio settle · Chio CLI](https://www.chio.computer/docs/reference/cli/settle.md): Inspect the local settlement lifecycle: pending envelopes, settled reconciliations, and dead-lettered settlements, as the kernel recorded them.
- [chio spend · Chio CLI](https://www.chio.computer/docs/reference/cli/spend.md): Watch spend as it happens: the event stream, burn-rate projections, anomaly findings, and budget-threshold webhooks.
- [chio start · Chio CLI](https://www.chio.computer/docs/reference/cli/start.md): Start the HTTP sidecar with zero-configuration defaults and durable receipts, so an SDK or a harness can reach a kernel locally.
- [chio trust · Chio CLI](https://www.chio.computer/docs/reference/cli/trust.md): Pin the keys your verifiers trust, run the trust control plane for your operator domain, and manage revocation and federated issuance.
- [chio work · Chio CLI](https://www.chio.computer/docs/reference/cli/work.md): Run work commitments through the owner service: submit a command, read its view, collect the result, and export its evidence.
- [chio workflow · Chio CLI](https://www.chio.computer/docs/reference/cli/workflow.md): Run the read-only preflight over workflow planning evidence before any step of the workflow is dispatched.
- [Compatibility & Evidence](https://www.chio.computer/docs/reference/compatibility.md): Which Chio artifacts the documentation uses, their compatibility boundaries, and the scope of recorded execution evidence.
- [Error Lookup](https://www.chio.computer/docs/reference/errors.md): Find a Chio error by URN, string code, numeric code or remediation, then choose a diagnostic procedure.
- [Finding Artifacts](https://www.chio.computer/docs/reference/finding-artifacts.md): Finding record reference: schema files, signature carriers, identifier derivations, reveal commitments, and the evidence behind a market transaction.
- [Guards Spec](https://www.chio.computer/docs/reference/guards-spec.md): Conformance reference for spec/GUARDS.md: guard categories, fail-closed rules, verdicts, evidence, advisory promotion, WASM guard limits, and the session journal contract.
- [HTTP Proxy Reference](https://www.chio.computer/docs/reference/http-proxy.md): Configure HTTP policy, authentication, receipts, and failure handling for the Chio sidecar.
- [HTTP Transport](https://www.chio.computer/docs/reference/http-substrate.md): HTTP authorization through Chio: endpoints, request and verdict fields, signed receipts, verification results, and the boundary between a decision and upstream execution.
- [The Chio Protocol · IETF Internet-Draft](https://www.chio.computer/docs/reference/ietf-draft.md): Chio is a kernel for agentic operating systems. It provides shared primitives for delegated authority, resource accounting, governed execution, and verifiable records. This document specifies the…
- [Metering Spec](https://www.chio.computer/docs/reference/metering-spec.md): Cost dimensions, monetary amounts, flat and hierarchical budget enforcement, the billing-export schema, and the kernel’s budget accounting types for Chio receipts.
- [OpenAPI Integration](https://www.chio.computer/docs/reference/openapi-integration.md): How chio-openapi turns an OpenAPI 3.x document into ToolDefinition values, the x-chio-* keys, the deny-by-method policy, and the chio api protect proxy contract.
- [Policy Schema Reference](https://www.chio.computer/docs/reference/policy-schema.md): HushSpec policy schema reference: top-level fields, rule blocks with defaults, built-in rulesets, extends and merge, extensions, governance metadata, and the guard each block compiles to.
- [Protocol Reference](https://www.chio.computer/docs/reference/protocol.md): The v1 Chio protocol contract: serialization, capability tokens, signed receipts, checkpoints, manifests, runtime interfaces, trust-control endpoints, portable trust, and certification.
- [Receipt Format](https://www.chio.computer/docs/reference/receipt-format.md): Look up Chio receipt fields, signed payloads, decision semantics, metadata, encodings, and verification requirements for the v1 format.
- [Receipt Query API](https://www.chio.computer/docs/reference/receipt-query-api.md): HTTP reference for the trust-control receipt read routes: filters, cursor pagination, response types, analytics, the operator report, and the CLI and SDK clients.
- [Receipt Query Cookbook](https://www.chio.computer/docs/reference/receipt-query-cookbook.md): Filter local and remote receipts, paginate large logs, and export records for an audit.
- [Schemas and Errors](https://www.chio.computer/docs/reference/schemas-errors.md): Schema-file lookup, numeric and URN error diagnosis, and versioning rules for interoperable Chio integrations.
- [C++ SDK](https://www.chio.computer/docs/reference/sdk/cpp.md): The Computer API in C++: fork, grant, run, and read signed receipts. Plus native sessions and offline receipt verification.
- [.NET SDK](https://www.chio.computer/docs/reference/sdk/dotnet.md): The Computer API in C#: fork, grant, run, and read signed receipts. Plus ASP.NET Core middleware, sidecar methods, and identity mapping.
- [Go SDK](https://www.chio.computer/docs/reference/sdk/go.md): The Computer API in Go: fork, grant, run, and read signed receipts. Plus hosted tool calls, local verification, and net/http middleware.
- [JVM SDK](https://www.chio.computer/docs/reference/sdk/jvm.md): The Computer API in Kotlin and Java: fork, grant, run, and read signed receipts. Plus Spring filters, receipt inspection, and streaming.
- [SDK Overview](https://www.chio.computer/docs/reference/sdk.md): Run agents on a computer, govern application requests, and verify evidence. Choose a Chio SDK by integration mode and language.
- [Python SDK](https://www.chio.computer/docs/reference/sdk/python.md): The Computer API in Python: fork, grant, run, and read signed receipts. Plus the sidecar and hosted MCP clients beneath it.
- [Rust SDK](https://www.chio.computer/docs/reference/sdk/rust.md): The Computer API in Rust: fork, grant, run, and read signed receipts. Plus crates for verification, WASM guards, and in-process evaluation.
- [Swift / iOS SDK](https://www.chio.computer/docs/reference/sdk/swift.md): The Computer API in Swift: fork, grant, run, and read signed receipts. Plus the embedded mobile kernel with App Attest.
- [TypeScript SDK](https://www.chio.computer/docs/reference/sdk/typescript.md): The Computer API in TypeScript: fork, grant, run, and read signed receipts. Plus hosted MCP sessions, offline verification, and cognition markets.
- [Security](https://www.chio.computer/docs/reference/security-spec.md): The Chio threat model: the agent-kernel-tool boundary, the threat register with its surfaces, controls, and residual risk, and the transport security profiles.
- [Swarm Protocol](https://www.chio.computer/docs/reference/swarm-protocol.md): The chio-swarm/v1 authority bundle: the signed artifacts, the fixed verification order, and the structural invariants a recursive delegation graph must satisfy.
- [Wire Protocol](https://www.chio.computer/docs/reference/wire-protocol.md): Native length-prefixed framing, hosted MCP HTTP session transport, trust-control lifecycle endpoints, and the chio-wire schema contract.
- [Workflow](https://www.chio.computer/docs/reference/workflow.md): Skill grants, skill manifests, signed workflow receipts, and the WorkflowAuthority lifecycle of WORKFLOW.md version 1.0 as the chio-workflow crate implements it.
- [Active defense](https://www.chio.computer/docs/security/active-defense.md): Turn verified security observations into bounded, authorized containment while preserving the evidence and rollback needed to operate the system.
- [Admission and execution nonces](https://www.chio.computer/docs/security/admission.md): Follow one operation from reservation to dispatch, and see why a reserved operation is not permission to execute.
- [Adversarial testing](https://www.chio.computer/docs/security/adversarial-testing.md): Write security tests that fail when a defense breaks: vary one hostile input beside a valid neighbor and read the protected resource directly.
- [Authority](https://www.chio.computer/docs/security/authority.md): Give an agent useful authority, delegate narrower work, and enforce current permission against one retained accounting history.
- [Behavioral gates](https://www.chio.computer/docs/security/behavioral-gates.md): Select verification gates by the contract they exercise, inspect their assertions, and distinguish required CI from later qualification.
- [Blast radius](https://www.chio.computer/docs/security/blast-radius.md): Find the exact set of capabilities a finding reaches, fence new issuance first, and never contain automatically from an incomplete view.
- [Bypass resistance](https://www.chio.computer/docs/security/bypass-resistance.md): Know which construction and dispatch paths exist for each consumer profile, and how the build refuses a new path that skips the kernel.
- [Caller delivery](https://www.chio.computer/docs/security/caller-delivery.md): Follow the evaluate, start, and report exchange, and know the one response that permits a caller-side executor to run the tool.
- [Evidence capture authority](https://www.chio.computer/docs/security/capture-authority.md): See who may capture, sign, and publish Linux enforcement evidence a merge depends on, and how it is bound to the commit it covers.
- [Classification](https://www.chio.computer/docs/security/classification.md): Turn detected content into categories, and categories into labels the kernel enforces, without treating a failed classifier as a clean result.
- [Process confinement](https://www.chio.computer/docs/security/confinement.md): Restrict a native tool’s filesystem, network, and syscall access, and require observed enforcement before the host accepts its launch.
- [Contain a compromised agent](https://www.chio.computer/docs/security/contain-a-compromised-agent.md): Stop a misbehaving process-hosted agent, withdraw its authority for good, and keep the evidence you need to explain what happened.
- [Control surfaces](https://www.chio.computer/docs/security/control-surfaces.md): Separate the credentials that control a sidecar or remote MCP edge from those that invoke tools, and refuse any reuse between them.
- [Credential broker](https://www.chio.computer/docs/security/credential-broker.md): Authorize an exact provider request, keep credential bytes in a separate service, and recover the original operation from retained evidence.
- [Credential custody](https://www.chio.computer/docs/security/credential-custody.md): Protect encrypted credential storage, sealed service keys, private IPC, and the durable attempt history needed for safe broker recovery.
- [Cross-org admission](https://www.chio.computer/docs/security/cross-org-admission.md): See what the boundary refuses when another organization's agent asks to act: stale treaties, missing or unverified evidence, and unpinned peers.
- [Custody model](https://www.chio.computer/docs/security/custody.md): Find which service holds each secret and signing key, who may ask it to act, and what evidence each action leaves.
- [Daemon credentials](https://www.chio.computer/docs/security/daemon-credentials.md): Deliver a daemon's master key and signing seed as sealed file descriptors, never through the daemon's environment or a path it opens.
- [Declassification](https://www.chio.computer/docs/security/declassification.md): Authorize one intentional reduction in disclosure restrictions without erasing the information already retained by the agent or its lineage.
- [Delegate sensitive research](https://www.chio.computer/docs/security/delegate-sensitive-research.md): Delegate a review of work that read a customer's contract terms, keep the result useful to your team, and keep the terms off the public pull request.
- [Delegation boundaries](https://www.chio.computer/docs/security/delegation.md): Know what a delegated agent can never gain from its parent, and which check refuses any widening of scope, lifetime, budget, or proof requirements.
- [Detector health](https://www.chio.computer/docs/security/detector-health.md): Report a detector that cannot see as a signed health event, and suppress automatic response until its view of events is trustworthy again.
- [Dispatch commitments](https://www.chio.computer/docs/security/dispatch.md): Join authority, accounting, and security ownership at one durable effect boundary so retries and recovery preserve the original operation.
- [Protect durable state](https://www.chio.computer/docs/security/durable-state.md): Identify the stores that hold authority, keep them on protected media with rollback anchors, and rehearse a restore that cannot bring back withdrawn authority.
- [Control egress](https://www.chio.computer/docs/security/egress.md): Bind outbound data to a policy-owned destination clearance and test that incompatible disclosure stops before the external effect.
- [Emergency stop](https://www.chio.computer/docs/security/emergency-stop.md): Stop a kernel scope with a signed record that survives restart, see where each check refuses, and resume after review without restoring revoked authority.
- [Engineering standard](https://www.chio.computer/docs/security/engineering-standard.md): Read the rules Chio's security code is written to, the mechanisms that make classes of defect unrepresentable, and the gates that enforce the rules.
- [Execution security](https://www.chio.computer/docs/security/execution.md): Connect authenticated requests to controlled execution, durable operation state and guarded results.
- [Deployment hardening](https://www.chio.computer/docs/security/hardening.md): Close bypass routes, separate service identities, protect durable state, and verify the chosen execution profile before serving agent traffic.
- [Hosted tenancy](https://www.chio.computer/docs/security/hosted-tenancy.md): Know what one tenant of the hosted market cannot reach: another tenant's rows, quota, workers, or identity.
- [Authenticated identity](https://www.chio.computer/docs/security/identity.md): Bind each operation to the caller, tenant, session, and authentication epoch established by the trusted host.
- [Information flow](https://www.chio.computer/docs/security/information-flow.md): Carry data restrictions from a sensitive read through subsequent calls, delegated work, and the guarded release of results.
- [Investigate a session](https://www.chio.computer/docs/security/investigation.md): Follow one operation from authenticated identity through decisions, effects, findings, and recovery while preserving the original signed evidence.
- [Invocation limits](https://www.chio.computer/docs/security/invocation-limits.md): Bound repeated tool use across one capability or an entire delegation family, including concurrent calls and interrupted execution.
- [Issuance governance](https://www.chio.computer/docs/security/issuance-governance.md): Apply policy ceilings before signing a grant, verify the authority returned, and freeze successor issuance under an authenticated tenant and lineage.
- [Key log witnesses](https://www.chio.computer/docs/security/key-log-witnesses.md): Run the independent witness and audit services that sign key-log checkpoints, detect split views, and keep key history verifiable.
- [Key transparency](https://www.chio.computer/docs/security/key-transparency.md): Verify authority changes through a durable key log, independent witnesses, activation commits, and the signing epoch of each artifact.
- [Labels and clearances](https://www.chio.computer/docs/security/labels.md): Model owners, readers, and compartments precisely, and understand the ordering used to permit or refuse a data transfer.
- [Least privilege](https://www.chio.computer/docs/security/least-privilege.md): Grant a task only the tools, resources, duration, delegation depth, and use limits it needs to finish.
- [Mailbox attestation](https://www.chio.computer/docs/security/mailbox-attestation.md): Know which process the kernel says sent a message, what that attribution proves, and why a null sender must be treated as unknown.
- [Market boundary](https://www.chio.computer/docs/security/market-boundary.md): Keep hosted-market authority, admission, and egress exact while tenants move between stores and releases change.
- [Multi-party security](https://www.chio.computer/docs/security/multi-party.md): Know which controls hold when authority is shared with your own agents, with another organization, or with another tenant on shared infrastructure.
- [Protected native hosts](https://www.chio.computer/docs/security/native-hosts.md): Route a coding host's file tools through a kernel-owned executor, and scope the host's calls with an expiring session credential.
- [Native secure invocation](https://www.chio.computer/docs/security/native-invocation.md): Assemble a retained host, invoke its registered connector and handle the guarded result without repeating the tool.
- [Output release](https://www.chio.computer/docs/security/output-release.md): Follow a tool result from return to caller, and name the checkpoint that makes its release final and replayable.
- [Security](https://www.chio.computer/docs/security.md): Give agents useful authority while controlling what they can read, disclose, execute, delegate, and recover after failure.
- [Persistent taint](https://www.chio.computer/docs/security/persistent-taint.md): Explain what an operation's reads leave behind, which later work inherits those restrictions, and what a verified isolation transition must preserve.
- [Post-quantum signatures](https://www.chio.computer/docs/security/post-quantum-signatures.md): Sign receipts and proposals with a hybrid classical and post-quantum key, and refuse any signature algorithm the kernel's floor does not admit.
- [Prepared connections](https://www.chio.computer/docs/security/prepared-connections.md): Hold one broker connection for one execution, bound to its authority and deadline, so a credential serves only the request it was prepared for.
- [Process attestation](https://www.chio.computer/docs/security/process-attestation.md): Attest a completed process run or one call, and verify the artifact against the kernel key, original nonce custody, and the receipt log.
- [Security profiles](https://www.chio.computer/docs/security/profiles.md): Choose a concrete host and execution boundary, then install the authorities and durable state that its guarantees require.
- [Prompt injection](https://www.chio.computer/docs/security/prompt-injection.md): Keep hostile instructions in retrieved content from becoming authority to disclose data, use credentials, or escape the execution boundary.
- [Proof of possession](https://www.chio.computer/docs/security/proof-of-possession.md): Bind a capability to the key that presents it, and know which store refuses a proof that has already been used.
- [Quarantine and recovery](https://www.chio.computer/docs/security/quarantine.md): Apply bounded containment, track each contribution independently, and lift a response only after its reversible effects are removed.
- [Recover an operation](https://www.chio.computer/docs/security/recover-an-operation.md): Reopen the original host state, replay a retained response and preserve an interrupted operation without repeating its effect.
- [Reference runtime](https://www.chio.computer/docs/security/reference-runtime.md): Provision the reference security topology and prove it is ready before it serves a single call.
- [Release integrity](https://www.chio.computer/docs/security/release-integrity.md): Know how a Chio release is staged as a draft, gated to the exact reviewed source, signed, and verified by the person installing it.
- [Remote signing](https://www.chio.computer/docs/security/remote-signing.md): Sign with a key held outside the host, detect a signer that answers for the wrong request, and issue capabilities from verified authenticator assertions.
- [Replay protection](https://www.chio.computer/docs/security/replay-protection.md): Name the store that refuses each kind of replay, and what an exact retry of an earlier request returns instead of a second effect.
- [Resource limits](https://www.chio.computer/docs/security/resource-limits.md): Set ceilings for a worker's CPU, files, and memory, and know which limits the operating system enforces and which the host samples.
- [Response authority service](https://www.chio.computer/docs/security/response-authority-service.md): Run the separate authority daemon that approves response plans, pinned to the exact processes allowed to ask it and to one validated deployment digest.
- [Response authorization](https://www.chio.computer/docs/security/response-authorization.md): Authorize a specific containment plan from reviewed policy and artifact snapshots, with independent service identity and bounded execution.
- [Revocation](https://www.chio.computer/docs/security/revocation.md): Withdraw circulating authority and carry that decision through admission, dispatch, output release, and recovery without reviving stale work.
- [Roll out active defense](https://www.chio.computer/docs/security/rollout.md): Promote a named cohort from shadow observation to bounded automatic response using measured behavior, exact evidence, and rehearsed rollback.
- [Secure a swarm](https://www.chio.computer/docs/security/secure-a-swarm.md): Run a governed swarm through five portable scenarios, read which control answered each, then see what the seven-scenario Linux matrix adds.
- [Secure an agent](https://www.chio.computer/docs/security/secure-an-agent.md): Run a real MCP tool through Chio, allow a useful read, refuse a write, and inspect the retained decisions.
- [Security events](https://www.chio.computer/docs/security/security-events.md): Turn an observation into a signed, verified security event, and decide from its producer's trust class whether it may drive automatic response.
- [Security receipts](https://www.chio.computer/docs/security/security-receipts.md): Look up every signed receipt that active defense, the keyring, the broker, and the cage produce, and the wire schema that defines each one.
- [Service roles](https://www.chio.computer/docs/security/service-roles.md): Run each reference-runtime service under its own account, with its own credential, in the order its authority requires.
- [Shadow migration](https://www.chio.computer/docs/security/shadow-migration.md): Inventory existing tools and history, verify signed manifests, and advance security posture without inventing labels or silently retaining bypasses.
- [Signed watermarks](https://www.chio.computer/docs/security/signed-watermarks.md): Mark content with a signed, sequence-bound watermark and verify later appearances without mistaking a detector failure for a clean result.
- [Signing authority](https://www.chio.computer/docs/security/signing-authority.md): Keep each artifact’s signing identity, cryptographic floor, and durable replay behavior consistent across normal execution and failure paths.
- [Supply chain](https://www.chio.computer/docs/security/supply-chain.md): Connect dependency review and artifact provenance to the exact binaries, helpers, policies, and manifests admitted by the execution boundary.
- [Temporal detection](https://www.chio.computer/docs/security/temporal-detection.md): Correlate ordered security events within explicit time and capacity bounds, and retain the evidence behind each finding.
- [Threat coverage](https://www.chio.computer/docs/security/threat-coverage.md): Connect each threat to an enforcing boundary, a meaningful counterexample, and evidence that the test detects a broken defense.
- [Threat model](https://www.chio.computer/docs/security/threat-model.md): Identify protected assets, trusted actors, and the concrete enforcement boundaries that separate untrusted requests from authorized effects.
- [Threshold approvals](https://www.chio.computer/docs/security/threshold-approvals.md): Bind independent votes to one retained operation, collect them across restarts, and return the approved request to kernel admission.
- [Tool flow declarations](https://www.chio.computer/docs/security/tool-flow-declarations.md): Declare what a tool returns, what it may receive, whether it sends data out, and which disclosures it accepts, so the kernel enforces flow.
- [Verified tool launch](https://www.chio.computer/docs/security/tool-launch.md): Bind the signed tool registry, retained executable, helper, resource descriptors, and observed execution transition into one launch contract.
- [Decoys and tripwires](https://www.chio.computer/docs/security/tripwires.md): Recognize contact with tenant-bound decoys and signed watermarks while keeping artifact custody, lifecycle, and observation confidence explicit.
- [Trust roots](https://www.chio.computer/docs/security/trust-roots.md): Know which keys a kernel trusts as issuers, how a chain binds to its root, and when a rotated key still verifies.
- [Unknown outcomes](https://www.chio.computer/docs/security/unknown-outcomes.md): Preserve uncertainty when an effect may have started, and reconcile the original operation before authorizing any resend or refund.
- [Verify security evidence](https://www.chio.computer/docs/security/verify-evidence.md): Verify original signatures and operation bindings, then add the log, key-history, and execution evidence required by the claim.
- [Witnessed rotation](https://www.chio.computer/docs/security/witnessed-rotation.md): Rotate a signing key in two witnessed stages so every verifier can tell which key was authorized when an artifact was signed.
- [Swarm authority](https://www.chio.computer/docs/swarms/authority.md): Verify the complete chain of authority behind a child task: signed plans, scoped delegation, routes, budgets, and revocation.
- [Bilateral Co-Sign](https://www.chio.computer/docs/swarms/bilateral-cosign.md): Require two operators to sign the same invocation, preserving separate keys and a shared record of its authority and policy verdicts.
- [Sub-agent budgets](https://www.chio.computer/docs/swarms/budgets.md): Divide a shared spending ceiling across delegated tasks, then verify that every allocation and terminal rollup still agrees.
- [Continuation tokens](https://www.chio.computer/docs/swarms/continuations.md): Bind one child task to its signed execution context, then choose single-use admission or repeated verification with a resumable token.
- [Delegation Hygiene](https://www.chio.computer/docs/swarms/delegation-hygiene.md): Measure how often a delegator narrows scope, shortens lifetimes, and tightens caps on the capabilities it issues, and see how that score enters issuance and passport decisions.
- [Swarm Denial Codes](https://www.chio.computer/docs/swarms/denial-codes.md): Diagnose refused swarm actions by their runtime codes, inspect the failed evidence binding, and choose a repair that preserves prior effects.
- [Disclosure Lineage](https://www.chio.computer/docs/swarms/disclosure-lineage.md): Verify the relationship between disclosed fields, provenance, leakage declarations and a trusted crypto-context report before accepting another operator’s evidence.
- [FROST Quorum](https://www.chio.computer/docs/swarms/frost.md): Authorize consequential actions with threshold signatures, participant-held signing shares, an authenticated roster and the live evidence required by each action.
- [Governance Ladder](https://www.chio.computer/docs/swarms/ladder.md): Compose governance across operators. Pin each participant’s action requirements, compute their compatible intersection, and require the resulting evidence at admission.
- [Swarm Overview](https://www.chio.computer/docs/swarms/overview.md): Delegate autonomous work through signed task graphs with checked scope, budget allocations, continuations, routes, and revocation evidence.
- [Pheromone Store](https://www.chio.computer/docs/swarms/pheromone.md): Share signed, decaying signals between agents and organizations. Each receiving kernel admits deposits under its own capacity policy and weights them by its own trust.
- [Relay Operations](https://www.chio.computer/docs/swarms/relay.md): Operate shared swarm intelligence across independent organizations: durable forwarding, authenticated peers, receiver-owned admission, recovery and inspectable delivery outcomes.
- [Revocation Epochs](https://www.chio.computer/docs/swarms/revocation-epochs.md): Bind continuations to a signed revocation epoch, then verify its freshness, excluded subjects, excluded tasks and list-root commitments.
- [Route Plans](https://www.chio.computer/docs/swarms/route-plans.md): Bind each delegated task to a signed route, compare host-selected metadata at admission, and revalidate its recorded binding before dispatch.
- [Reputation & Scarcity](https://www.chio.computer/docs/swarms/scarcity.md): Bound how many tasks a delegated graph can name and how many signal deposits any origin can place in a receiver's store, then separate admitted volume from influence.
- [Selective Disclosure](https://www.chio.computer/docs/swarms/selective-disclosure.md): Open chosen receipt or workflow fields to another organization with a BBS proof, and check them against the issuer, the projection, and the presentation's challenge.
- [Task graphs](https://www.chio.computer/docs/swarms/task-graphs.md): Coordinate child agents with a signed plan that bounds delegation depth, fan-out, and the authority attached to every task.
- [Join & Terminal Receipts](https://www.chio.computer/docs/swarms/terminal-receipts.md): Join parallel task receipts and reconcile the completed graph, referenced routes and declared budget rollups under signed terminal evidence.
- [3-Vendor Walkthrough](https://www.chio.computer/docs/swarms/three-vendor.md): Follow one buyer and three vendors through scoped authority, bilateral signatures, destructive authorization, and a portable audit package.
- [Swarm Graph Verification](https://www.chio.computer/docs/swarms/verification.md): Inspect signed task graphs, admission checks, schemas, and the isolated repository scenarios used to verify them.
- [Delegation Witnesses](https://www.chio.computer/docs/swarms/witness-chains.md): Carry verifiable authority between operators with signed hops that bind parent and child scopes to an explicit narrowing proof.
- [Troubleshooting](https://www.chio.computer/docs/troubleshooting.md): Find the exact error or refusal you are looking at, read what caused it, and run the command that fixes it.
- [Chio-Wall](https://www.chio.computer/docs/wall.md): Chio-Wall records signed evidence for a defined denied cross-domain tool-access scenario.