Direction 33: Bounded mailboxes; send never blocks; overflow is a roof

Resolves tension 5 of the comparison-synthesis-draft: “send never blocks or fails” (Q7) against bounded everything (direction 4).

  • Every mailbox has a bound. It is declared in the process header, with a default from the law numbers (Q12).
  • send never blocks and has no try. The source stays as it was.
  • A full mailbox is a broken roof (direction 18): the sender crashes. Overflow means the design has no flow control. The fixes are ask (deadline, backpressure) or a larger declared bound, and the agent gets the crash as a task (direction 21).
process RefundQueue(db: Ledger, clock: Clock) mailbox: 10_000
  ...
end
 
queue.send(Enqueue(request: r))      # never blocks; crashes the sender if the mailbox is full

Why the sender and not the receiver: crashing the receiver loses the messages it already holds; crashing the sender loses one message and points at the code that lacks flow control. TigerBeetle’s fixed-size-everything makes the same call: hitting a limit is an assertion, not a wait.

First tested by: Mo.Sim under load with a slow consumer. Reopen if real programs need send to return rain instead.