Yichus / Reference

API MCP tools

Every tool in Yichus/Mcp::catalog. Parameters and recorded examples help you choose a tool; the getting-started walkthrough teaches the loop.

Core

MCP servers list these from the start.

Family ship

Produce what leaves the session: the engine JavaScript and a frontend once api_verify is proven, and the program's IR (YIR) exported for other tools. Listed once api_tools opens the family; any tool runs by name either way.

Family access

Who may read and write each table, and how handlers combine reads and writes: rule snippets, the access check, route permissions, and an IO audit for read-then-write, orphaned IO and writes without reads. Goes deeper than api_verify's access properties. Listed once api_tools opens the family; any tool runs by name either way.

Family concurrency

Races, lost updates and atomic transactions: causal order with per-cell race, stale-read and declared Yichus/Spec checks, multi-instance schedules, escrow admission, protocol cases under the native scheduler or TLC, and commit strategies. Open it when api_verify reports a read-modify-write or interleaving finding, or to check a specific race such as overselling. A lost-edits finding needs no tool from it: guard the save with a version, as the finding's next step says. Listed once api_tools opens the family; any tool runs by name either way.

Family proofs

Stating and checking properties beyond api_law_check: suggested laws, Lean proofs, bounded conformance runs of handlers, kept examples re-checked after edits, claims such as "field x is never read" checked against the program's facts, and FlowSpec families. Listed once api_tools opens the family; any tool runs by name either way.

Family orientation

Ways to read an unfamiliar program: briefs, dossiers, workbooks (including what a change to a binding can affect), structure explorers, organization lenses, the abstraction ladder, several programs side by side, the in-memory world and per-binding facts. Listed once api_tools opens the family; any tool runs by name either way.

Family changes

Compare two versions of the same program (every before-and-after diff is here), or plan a structural change before making it. Listed once api_tools opens the family; any tool runs by name either way.