Reference
Documentation
Documentation and examples
Start with a guided task, or go straight to commands, parameters, and package declarations.
For a first example, run a calculator and inspect Why. The Why guide explains how its calculation becomes an explanation; the diagram examples show how analysis exposes code that needs changing.
Build with an agentCompile, verify, and save a replayable run.Review a programRead tool output and decide what to test next.Use WebMCPInspect, edit, and recheck a program with your agent.
Reference
- Get the CLI — source-build instructions and local prerequisites.
- CLI subcommands — commands, flags, and help.
- API MCP tools — typed parameters and generated examples.
- Engine Bosatsu packages — public types, exports, and source.
- Connect an agent — browser relay and Node server setup.
- Organization lenses — how to read a stack, conventions, and differences.
More examples and technical walkthroughs
- APIs and generated frontends
- Worked WebMCP requests
- Program reports · Fact tooling
- Mutation flows · Distributed systems
- Spec-first verification · Batch admission
- Provenance · UI compilation · IO effects
- Runnable route map · Browser compiler
- Service analysis · Explorer trust · Debugger
- Code-shape experiments · Earlier demos and runtime fixtures
How the reference pages are generated
Command pages are generated from the published command list. Tool pages come from
Yichus/Mcp::catalog, the declaration used by the engines. Package pages expose the public Bosatsu declarations.
The reference build tests check that each declared surface has a page.