Expand description
2026-09-30: The batched MTP verify’s programs (Mode::VerifyBatch). A batched verify’s
plan depends on its row table (the runs of equal k and their contiguity), and a serve
meets many tables, so each program is compiled the first time its table is verified and kept
in a bounded cache. The legacy forward’s graphs are keyed by the batch’s (slot, k) pairs,
which fix the table, so a graph captured around a program replays that program’s launches.
Owner: model-layers circuit executor. Invariants:
- Every program is laid out from the shared workspace base, and the build sized the workspace
for the widest table it admits (
max_rows); a larger table is refused, never placed past the workspace. - The cache holds at most
CACHE_CAPprograms; a miss compiles, an eviction drops the least recently used.
Structs§
- Parts
- 2026-09-30: The build’s state a batched-verify compile reads.
- Verify
Batch - 2026-09-30: What compiling a batched-verify program reads, kept from the build.
- Verify
Batch Program - 2026-09-30: A compiled batched-verify program and its plan.
Constants§
- CACHE_
CAP - 2026-09-30: Programs kept per executor.
Functions§
- arena_
bytes - 2026-09-30: The arena bytes of
table’s plan. - sizing_
tables - 2026-09-30: The tables the workspace is sized over: for every row count
4..=max_rows, one table of that many rows (runs of 2, with one run of 3 for an odd count).