max / makenotwork

Ring a bell when a creator asks for a bigger mail allowance b29d7606's last gap, found by reading its done condition against the code rather than assuming work remained. Everything else was built: the window, the counter, the all-or-nothing reservation, all four send paths gated, the creator's count and cap and reset date, the warning band, the form with a reason, the operator queue, the override write. What a filed request did not do was tell anybody. It landed in a table and waited for someone to remember to open /admin/mail-caps. For a creator whose sends are being refused, that is the soft cap behaving like a hard one: the application path is the whole defence of the design, and an application path nobody is told about is not one. send_alert, which is what this server already uses for an operator who needs to know something -- support tickets, monitor status changes, ingested alerts. After the row is written and never a reason to fail the request: the queue holds the ask whether or not the mail arrives, so a failure costs a doorbell rather than a creator's application. support@ and not info@. Role addresses land in one mailbox and the sorting is done on the address, so a precise one is the whole benefit of having several.