The effect log's table and module are both called the outbox. That name comes from the transactional outbox pattern, where rows are written so that something else can send them and then forget them.
It stopped being true when the intent log and the effect log collapsed into one. What sits there now is kept indefinitely, read forward by the dispatcher and read back by every client that comes home, and drained by nothing. The module's own opening line calls it the effect log, and so does everything written about it since.
Nothing has shipped yet, so the table can be renamed rather than lived with.
The effect log's table and module are both called the outbox. That name comes from the transactional outbox pattern, where rows are written so that something else can send them and then forget them.
It stopped being true when the intent log and the effect log collapsed into one. What sits there now is kept indefinitely, read forward by the dispatcher and read back by every client that comes home, and drained by nothing. The module's own opening line calls it the effect log, and so does everything written about it since.
Nothing has shipped yet, so the table can be renamed rather than lived with.