Draft ADR for "smart" quota implementation #295
Description
Our daily global message limit is primarily intended to keep our number of database records below a certain threshold. We do this by incrementing a Redis key on each message. However, now that we auto-archive successful messages, this key no longer reflects the actual state of the DB.
Instead, we'd like to have the ability to send new messages depend on the actual number of records. This should allow users significantly more daily flexibility while still achieving our goals.
Because the annual threshold still depends on all messages sent (since that threshold is about infrastructure costs rather than records retention), the annual threshold should remain a hard cap rather than changing along with this one.