Summary
Replace MAB-UCB's binary "is this author covered?" reward with a continuous signal: how many of this author's events did this relay actually deliver?
Why
The current reward function treats all covered authors equally. But a relay covering 10 authors while keeping only 7 days of history should score lower than one covering 5 authors with full retention. Per-author event recall as the reward signal would let the algorithm distinguish between relays that technically cover an author and relays that actually deliver their posts.
What to do
- Change the MAB reward from binary coverage to fractional event recall per author
- During each round's observation phase, measure
events_retrieved / events_expected per (relay, author) pair
- Benchmark against binary-reward MAB-UCB across all 6 time windows — especially at longer windows where retention differences matter most
Effort
Higher — requires modifying the reward function and the observation phase to query event counts.
Reference
- IMPLEMENTATION-GUIDE.md: Improvement Opportunities (higher effort)
Summary
Replace MAB-UCB's binary "is this author covered?" reward with a continuous signal: how many of this author's events did this relay actually deliver?
Why
The current reward function treats all covered authors equally. But a relay covering 10 authors while keeping only 7 days of history should score lower than one covering 5 authors with full retention. Per-author event recall as the reward signal would let the algorithm distinguish between relays that technically cover an author and relays that actually deliver their posts.
What to do
events_retrieved / events_expectedper (relay, author) pairEffort
Higher — requires modifying the reward function and the observation phase to query event counts.
Reference