Batch protocol step 1: narrow-scope override fires when unique-file-scope (distinct PUBLISHED files audits touch) < ceil(|V|/2). But which files each audit touches is only known after translating each invariant to a verifiable claim — i.e. after the work the batch decision is supposed to scope. In practice the LLM eyeballs repo file count as a proxy (this run: ~16 files vs threshold 19 → 1 agent).
The script already knows |V| and the PUBLISHED file census. audit mode could emit a batch|ADVISORY|recommended: <n> agents row and retire the hand-computed heuristic — consistent w/ the mechanical-realization invariant (deterministic rules live in the script).
Batch protocol step 1: narrow-scope override fires when unique-file-scope (distinct PUBLISHED files audits touch) < ceil(|V|/2). But which files each audit touches is only known after translating each invariant to a verifiable claim — i.e. after the work the batch decision is supposed to scope. In practice the LLM eyeballs repo file count as a proxy (this run: ~16 files vs threshold 19 → 1 agent).
The script already knows |V| and the PUBLISHED file census.
auditmode could emit abatch|ADVISORY|recommended: <n> agentsrow and retire the hand-computed heuristic — consistent w/ the mechanical-realization invariant (deterministic rules live in the script).