Skip to main content

verify

Verify annotated kernels against their specs and apply the policy. On a terminal, a live line shows the current kernel and stage (lifting, searching for counterexamples, proving (Lean 4 · Lemma Hub)). The run ends with the results table, the summary, and the Lemma Hub line. With --format table, policy problems such as expired waivers are printed after the table. A run over a subset of the project (PATHS or --changed-only) is recorded as partial; signoff refuses partial runs.

explain

Show a failure of the last run: the failing configs, the minimal and typical witnesses, correct only when, details, notes and the suspect line. --json prints the full result record.

repro

Write a standalone PyTorch script that runs the kernel on the GPU with the counterexample input, and compares it with the spec’s float64 reference interpreter:
Run it from the project root. It needs a GPU, Triton and PyTorch. Failures without a concrete input, such as an integer-overflow witness found by SMT, cannot be reproduced this way, and repro says so.

guards

Generate a Python module with one guard_<kernel>(...) function per annotated kernel. It checks every assume= entry and every scalar bound to a model constant. See Layouts and assumptions.

mcp

Start the MCP server for coding agents, with the tools spec.get, spec.nodes, verify.quick, verify.full, verify.job, explain and lemma.search. It needs the mcp extra. See Coding agents.