Examples Overview

The projects here are the pricing service from the Quickstart, rebuilt the way real services are built: inside a framework, behind a sidecar, as native tools, as an MCP server, and as a small internal desk. Each one shows a decision the kernel signs and the effect it leaves behind.

Every project starts with the same command. chio new fetches the published bundle, checks its digest against the signed index, and unpacks it into a directory of that name.

chio new pricing-desk --example pricing-desk

fetched    pricing-desk, 134 KB, sha256 3b7e…c41a verifies
index      chio.computer/examples, signature verifies against the key in chio 0.2.0
created    pricing-desk, owned by did:chio:z6Mkf3…Qp9
next       cd pricing-desk, then the entry point in README.md

chio new --list-examples lists every published project with its languages and what it runs. Each page below also offers the same bytes as a download.

What will you build?

The projects

The repository face has its own projects: the Quickstart computer, the Megastart Rust project, the security labs, and the swarm proofs, each on its own page.

Follow one application through its lifecycle

The pricing desk carries one set of state through several guides:

• Approvals: a deep discount that waits for Mara, then an ordered price change.
• Customers: Harbor Goods and Ostrander, with their own quotes and receipts, then application CI.
• Repricing: outcomes and cancellation, a shared USD 2.00 allowance, and traces tied to receipts.

One contract in every HTTP stack

Every framework project serves the same contract: POST /v1/quote needs a grant and records the quote, and GET /v1/quotes lists them. A request with no grant is refused, a granted one returns the price, and sku-999 is admitted and then rejected by the handler. What differs is where each framework lets the adapter read the body and where the handler finds its receipt.

An adapter's receipt can record status 200 for a request the handler later rejects with 400: read the response and the receipt together. HTTP Framework Middleware explains what the OpenAPI document controls.

Keep one project through the journey

For a Rust tool, run pricing-tools, change its grant, then audit its receipts. For an HTTP API, start with Protect an API and keep the same quotes when you serve them over MCP. You do not need every language.

Build a project

Each project pins its Chio dependencies: Rust projects through the git revision in Cargo.toml, and the others through their registries' lockfiles. Projects that start a sidecar use the installed CLI. Building Chio itself from source is covered in Contributors.

Check the project's prerequisites

Each walkthrough names its toolchain and framework dependencies. The Rust hosts use Unix file locking. The C++ project builds Drogon and the Rust FFI into its own .deps directory, so it needs CMake, a C++17 compiler, and Rust as well.

Next: start with a useful result