What changed

font-display was Instrument Serif at weight 400. The shine was hidden on a repeat visit in the same session.

font-display is Inter, weight 500, −0.05em. The hero is 68px at most with 0.96 line height, and the closing heading 48px. The shine always plays, from 0.3s when the entrance is skipped.

The input was always open, with the cursor in it on a computer, and the command sat on its own line below. The page was 442px wide on a 375px phone.

Verify a domain and the command sit side by side. Pressing Verify animates the same button and shell into the field with one spring, focuses it, and Escape closes it. The page fits 375px.

The mark was two strokes, a ring and a tick, copied into logo.tsx, the icon route and the favicon. The hero tile was graphite like every other tile.

MARK_PATH in logo.tsx is the one definition, and the icon route imports it. AppIcon draws the hero tile: rim, green body, glow, echoes of the mark, a soft top highlight, and the mark with a glow and a shadow. Its colours come from the globe's green, #46FEA5.

The globe ignored the pointer, and a page change only moved and resized it, like a flat picture. A step's body clipped the selected card's ring. The Activity strip cut events off at a hard edge, with the platform's scrollbar.

Two new uniforms, yaw and pitch, turn the globe. Each scene has its own, eased with the position, and a mouse drag adds an offset with a fling. The step body's clip is 8px wider. The strip uses ScrollArea with scroll-fade-x.

Content scrolled off at a hard line, and the globe was cut off by the window. On a claim page the globe was a thin strip along the top, at a height that changed with the window.

EdgeFade adds a fixed vignette and six stacked backdrop blurs at each edge. On claim, setup and email pages the globe's lower edge is pinned 300px down (240px on a phone), content starts lower, and ClaimSurface darkens the sphere behind the title.

The confirmation link was a GET that confirmed by being opened, and an alert had no way to turn itself off.

The links in emails open /confirm-email and /unsubscribe, each a page with one button that POSTs. Every alert has an unsubscribe link and List-Unsubscribe headers, so mail apps show their own button.

Limits were counted in memory. Each function instance kept its own count, so a limit of 5 an hour was really 5 an hour per instance.

One row per counted action, as a sliding window. An advisory lock per key makes two requests for the same key take turns, so they can't both read 'under the limit'.

Clicking the confirmation link landed on the home page with ?email=confirmed in the URL and no message. If the confirmation email failed to send, the address stayed saved as if a link were on its way.

components/landing/email-notice.tsx shows a toast for confirmed or expired and tidies the URL. setEmail clears the address when the send fails. The setup page no longer says the owner was told, which is only true if they turned alerts on.

The notes only existed in an old worktree under apps/demo, described the Relay engine with its demo account switcher, and stopped at 775 tests.

They sit beside the app they describe. New chapters: Sessions without sign-up, Setup links, Alerts, The page and its motion, The globe, and Installable, with push.

A website only. Nothing could reach someone who'd closed the tab.

app/manifest.ts makes it installable, app/icons/[size]/route.tsx draws the icon at five sizes, and public/sw.js handles pushes.

A form, a table and a stack of cards whose only job was to exercise the engine. An account switcher sat in the header.

/ is the hero and three short sections. /claims/<id> is your domain, add one record, we check it, verified. /setup/<token> is the helper's view. All three read view.phase and lay themselves out to match.

A plain black page.

components/stage/globe.wgsl draws it, start-globe.ts runs it with vgpu, and pages steer it through a plain object in stage-store.ts.

The only way to find out what happened was to keep the page open, and the only person who could act on a claim was whoever started it.

alertForTransition in core decides what's worth a message, move in claim-service.ts reports state changes to it, and share-service.ts makes links that are safe to forward.

A header naming an account, and a dropdown to switch between two seeded ones. It proved nothing.

A sessions table, a random token in an HttpOnly, SameSite=Lax cookie, and only the token's SHA-256 in the database.

Domain verification was one step inside Relay, an email marketing product, and the record was _relay-challenge with relay-domain-verification=.

One product with one job. The repo, the app folder, the local database, the Domain Connect template and the record all carry the new name.

The demo only deployed when someone ran the CLI, and previews didn't exist.

Pushing does the deploying. Previews sit behind Vercel login and use their own free Neon database, so test claims never reach production.

The app only ran on your laptop, with a setInterval loop as its worker and Postgres in Docker.

It runs in Vercel Functions on real Node. Vercel Cron calls /api/cron/run-due-work every minute, and the database is Neon's free plan in iad1.

The work lived only on this machine, on a branch called claude/domain-claim-engine-63b051.

It's on GitHub as PR #2, and the branch name no longer mentions Claude.

The notes were untracked files, one git add . away from a commit, and nothing required them to stay current.

Git ignores both. Each change updates the affected chapters and logs itself here, with why it happened and what isn't finished.

PGlite has a single in-process connection, so two transactions could never overlap, and the concurrency tests couldn't really contend.

Real Postgres on port 55432. Tests use separate connections, so transactions truly overlap, and each test gets its own database cloned from a migrated template.

z.url() accepted any scheme, including javascript:, and one of these URLs gets opened in the person's browser. Provider errors were stored at any length.

z.url({ protocol: /^https$/ }) refuses everything else, and MAX_PROVIDER_ERROR_LENGTH caps what's stored at 200 characters.

Nothing connected the written docs to the code they described.

apps/web/lib/docs.test.ts compares the state diagram and transition table in the docs with the ones the code produces.

The logic existed only as packages that nothing was calling.

You can claim a domain in a browser, and a worker keeps re-checking it without you.

An empty workspace with strict TypeScript, Vitest and CI set up.

A complete claim lifecycle, from a typed domain to a stored and audited verdict.