usage.batch is a request, not a notification, and its answer is the watermark¶
Decision 296 · accepted · 2026-09-13
A notification would leave the pod guessing what landed. usage_seq on the session
row moves as greatest(current, offered) so a retried older batch cannot walk it
backwards, and is not fenced on the epoch: a pod that has since been fenced
still made the calls it is reporting, and refusing them loses money rather than
protecting anything.
Governs: apps/troupe_plane/lib/troupe/plane/control/connection.ex, apps/troupe_worker/lib/troupe/worker/usage.ex