Make it stick · 4 min

A real run

Everything so far was explanation. This actually happened: your own domain at Vercel, on live DNS, from your local audit log.

joycabinet.com, 6 minutesTimes in UTC

02:46:38

CLAIM_CREATEDCreatedby You

You claimed joycabinet.com. The engine found Vercel's nameservers, issued a code and scheduled its first look.

Screen phase: Add record

Step 1 of 7

A snapshot of the audit log from Nov 8, before the product was renamed. The record then was _relay-challenge.joycabinet.com.

Two things read differently todayThe record is now _prufy-challenge, so this exact run would need the new name. And the three early checks that found nothing still come back from the API as fix_needed, but the claim page now shows them as Add record, because isWaitingForRecord in components/claim/phase.ts treats "nothing at the name" as "not added yet". The phases above are what the API reported.

What to notice

In the run	The concept
The first checks are the worker's	Scheduling, and growing backoff
Propagating is logged as `CHECK_FAILED`	The lifecycle event and the screen are different things
20 seconds from propagating to verified	Rule (c), waiting for a public resolver
The record's removal shows up on the next check	Re-checks, and the grace period
At risk, not lost	Nobody is silently revoked