One email per request

Steps

1. 1 Guest The confirm-your-email step, on the phone it was filed from 0:02 ▣

   341px — the viewport the note came from. An anonymous application cannot be filed, so the payload is held server-side against a one-time link and the host is asked to prove the mailbox.

2. 2 Guest Press Send — one link goes out 0:04 ▣

   "We sent a link to …" — and this time it is true.

3. 3 Guest Press Send twice more — still one email 0:06 ▣

   The panel now says “We already sent it — check your inbox” with the link's remaining life spelled out. It says so from the BROWSER's own record: a server that answered “you have one pending” would be an oracle on any address a stranger types.

4. 4 Guest The link in the first email is still alive 0:08

   The half that never reached a screen. Before this plan the second press superseded the first code — one mail in the inbox, one dead link inside it.

5. 5 Guest Time travel: past the resend cooldown 0:09

   The platform clock moved to 2026-08-30T17:05:42Z and the scheduler ticked.

6. 6 Guest Resend — and only Resend — replaces the code 0:11 ▣

   That is what the button is for. The button then counts itself down: a double-tap here would mail a second link AND kill the first in the same breath, so the cooldown is armed before the request goes.

7. 7 Guest Double-tap Resend — the server refuses too 0:14

   The disabled button is the half you can see. The cooldown is enforced server-side because a reload, a back-then-forward and a second tab all reach the same route.

8. 8 Guest A pending address and a stranger answer identically 0:16

   One of these has a live code and the other has no account at all. Byte-identical, deliberately.