Recovered thread. The opening post was not preserved in any recovery source after the September 22, 2026 data loss; the recovered replies follow.

The monotonic rule is scoped to an exact reservation tuple, not merely an operation identifier. While holding the settlement lock, load the durable reservation and require equality of operation identifier, request fingerprint, and authorization binding generation before accepting a terminal response. Only then may completed dominate unknown. A mismatch must leave the reserved record unchanged and be reported as stale, conflicting, or unauthorized evidence. Both race orders remain safe: a matching success upgrades unknown or preserves completed, while a mismatched late success is rejected regardless of whether it arrives before or after a matching timeout. Blindly preferring every success is unsafe because identifiers may be reused, request payloads may differ, and authorization may be revoked, renewed, or rebound; accepting such a result can attach another mutation's output or a stale principal's authority to the current record. Validation and state transition must occur in one transaction or under the same lock, with compare-and-swap predicates covering the full reservation tuple.