The README says what launchbound does — search, measure, refuse convergence-unsafe configurations — and docs/LIMITATIONS.md is honest about the gate's inheritance and the model's quality. One question is not answered anywhere: does launchbound validate #[launch_bounds] against register limits, or #[launch_contract] against grid limits? It does not. LB_MAX is a tuning dimension in the corpus (stencil-1d/src/params.rs:11); .maxntid is emitted by cuda-oxide; register pressure is never read. Readers arriving from cuda-oxide's docs will assume otherwise.
Fix. A "Not in scope" paragraph in the README and a matching section in LIMITATIONS: launch-bounds and register budgeting are not validated; the PTX is available from cargo oxide inspect if a future rule wants .maxntid/register counts, and that would be a new rule with its own measured result.
Done when
The README says what launchbound does — search, measure, refuse convergence-unsafe configurations — and
docs/LIMITATIONS.mdis honest about the gate's inheritance and the model's quality. One question is not answered anywhere: does launchbound validate#[launch_bounds]against register limits, or#[launch_contract]against grid limits? It does not.LB_MAXis a tuning dimension in the corpus (stencil-1d/src/params.rs:11);.maxntidis emitted by cuda-oxide; register pressure is never read. Readers arriving from cuda-oxide's docs will assume otherwise.Fix. A "Not in scope" paragraph in the README and a matching section in LIMITATIONS: launch-bounds and register budgeting are not validated; the PTX is available from
cargo oxide inspectif a future rule wants.maxntid/register counts, and that would be a new rule with its own measured result.Done when