Status: IN
The codebase's default cost model pushes deferred costs to reads, but this default is selectively overridden: eagerly rebuilt derived state (such as autocomplete caches and leaderboard indexes) and lazily deferred computation (such as time decay, expiration, and balance derivation) coexist as deliberate per-use-case design choices, suggesting that access-pattern considerations influence where the cost boundary is placed.
the per-use-case allocation strategy resolves an apparent contradiction with the reads-pay default by correlating write cost with read frequency
Depends on (SL): write-read-cost-allocation-is-per-use-case, writes-are-cheap-reads-pay