Module kernels 

2026-09-28: The kernels the circuit executor can launch, resolved at boot through literal lookups (so the kernel-lookup audit records each at its line here), and the probe of every kernel any rule names, which is what the fuser treats as available.

Owner: model-layers circuit executor. Invariants:

• The fuser sees every rule kernel the loaded modules contain, not only the ones an emitter launches: hiding a present kernel would let a lower-priority rule win and the plan leave legacy routing. A plan that selects a kernel with no emitter handle is refused instead (KernelTable::handle).

Structs

KernelTable

2026-09-28: Emitter handles by kernel id; only present kernels are kept.

Functions

available_in

2026-09-28: Every kernel rules name that the target’s modules ((name, PTX)) define. Read from the PTX, not by lookup: a lookup of an entry the target lacks would count as an unresolved kernel at the boot gate. Capability bits are not probed yet, so a rule that requires one is refused rather than assumed present or silently skipped.

ptx_defines

2026-09-28: Whether PTX text defines the entry point func (.entry func().