Yichus / Reference / API MCP tools

api_conformance_check

Check declared Yichus/Spec Conformance and WorldConformance bindings by execution: the compiled handler runs in a real seeded world over generated inputs (one table for Conformance; every table, as one of the declared callers, for WorldConformance), and the declared step is compared against the projected world after every operation. Three-valued verdicts (holds is bounded observation, never proof); divergences render through the declaration's own describe and show_input, and name the caller in the world form. Violated and inconclusive both mean not done.

Kind: ConformanceCheck. Origin: Yichus/Mcp::catalog.

CLI: yichus conformance — the same conformance check by execution.

Parameters

• sources (required, array) — JSON array of {fileName, source} Bosatsu files including the Conformance or WorldConformance bindings.
• module_name (optional, string) — Optional module name for the verdict artifact (default Conformance).
• seed (optional, integer) — Optional run seed; the whole run replays from this one number (default 41).
• trajectories (optional, integer) — Optional fresh-world trajectories per conformance (default 20).
• ops (optional, integer) — Optional operations per trajectory (default 10).

Read the result according to this tool’s scope: static checks, bounded execution checks, and descriptive diagrams answer different questions. A successful call is not a general approval of the program. The safety and permissions guide compares the checks and provides editable ownership, guard, and role examples.