An operation you can run a thousand times and change nothing after the first. Press it again. Nothing. That is the point.
Press the button — or mash it; the elevator cannot tell the difference. The first press creates the request; every press after lands in the exact same state and produces the exact same result. That property has a name, stamped here in green: a safe, repeatable no-op. The car arrives precisely once, supremely indifferent to your urgency. He is not being ignored. He is being handled correctly.
In Linear Associative Algebra, Peirce marks the elements where x·x = x — applying the operation twice lands exactly where applying it once did. He calls them idempotent: same-powered. Under ordinary multiplication only two numbers qualify, 0 and 1, the two most patient numbers there are.
Absolute value. Rounding a number that was already round. Multiplying by one. A function f where f(f(x)) equals f(x): once you have applied it, applying it again is a formality. The result has nothing left to learn from repetition.
HTTP draws a line through its methods. GET, PUT, and DELETE are idempotent — call them twice and the server lands in the same state. POST is not, which is exactly why your browser warns you before re-submitting a form. The reliability of the entire web rides on that one distinction.
INSERT … ON CONFLICT DO UPDATE. Run it once, or run it on every retry of a flaky job — the table holds exactly one row either way. Idempotence is how a database survives a client that cannot honestly promise it pressed the button only once.
Networks lose acknowledgements, so senders retry, so messages arrive twice. The trick is not to deliver exactly once — that is nearly impossible — but to make handling a message twice indistinguishable from handling it once. An idempotent consumer turns a duplicate into a no-op, and a hard problem into a solved one.
Send an Idempotency-Key with a payment and Stripe remembers it: retry after a dropped connection and you get the original result back, not a second charge. A single HTTP header standing between a network hiccup and your customer's fury. The word, doing real work, in production, right now.
Kubernetes reconciles toward a desired state — apply the manifest ten times, same cluster. Terraform plans, CI deploys, message queues, an agent re-running a tool after a timeout: all safe only because the operation underneath can be repeated without harm. The button has been pressed. It remains, as ever, done.