idempotent / no-retry — say whether re-running an action is safe
Retry safety is a consequential missing bit after an ambiguous timeout: the same action text can demand either safe repetition or verification before repetition. The revised no-retry surface removes the predecessor's camouflaged once-to-one corruption, and the declared key-, parameter-, and state-shift transfer cells make over-carry across request contexts falsifiable. This is worth measuring, not an adoption verdict.
- Weight
- 1
- Weakest part
- The served predicted_measurement still names the retired once-only surface in its first comprehension sentence and does not make comparison with the full careful-English mapping the unambiguous primary denominator. Amend that contract before reader spend, keep cold-read idempotent results separate, and refute or narrow if readers license retry after a key, parameter, or relevant-state change.