01-projects/personal-brand

site build brief v2

Build brief v2: The Denominator v0 site on a private preview

Goal (real-goal guard)

The founder wants to CLICK THROUGH his new personal publication on his phone and react to it. Success = a working, private, signed-in-only preview that matches the locked design, with the post #1 draft readable. Do not optimize for anything else: no SEO, no analytics, no newsletter wiring, no public launch. thedenominator.dev is NOT registered. Do not attach any domain, and nothing may become publicly reachable.

Time cap

About 3 hours of wall time. If you aren't converging by then, stop, push the WIP branch, and report where you are.

PRE-DECOMP (required, BEFORE your first remote write)

Before creating the repo or deploying anything, write /Users/ray/Projects/the-denominator-PREDECOMP.md with: the EmDash setup steps you'll use (from its CURRENT docs), the Cloudflare resources you'll create (Worker name, D1, R2, KV), how the preview hostname is routed, how the EmDash admin is owned and signed into, and your answers to the ACHIEVABLE? questions below. Then proceed. (The parent will read it afterward. You don't need to wait for approval unless an ACHIEVABLE? answer is "no".)

ACHIEVABLE? (answer in PRE-DECOMP)

Sources of truth (read first)

Repo and output locations

Cloudflare

What the site must do (acceptance contract)

  1. Home /: the masthead (S1 blue), NO rule above the wordmark, bottom double rule kept. Under it, a folio line = centered small-caps nav WRITING · ABOUT · SUBSCRIBE, with no domain and no tagline. Then the approved page-top composition: a faint graph-paper band, the headshot sticker (white outline, slight rotation, soft shadow) and blue handwritten notes + arrow ("hi, I'm Ben", "I write about agents in production", "(on Snowflake + Claude)"). Then a Writing list showing post #1 with a visible DRAFT badge.
  2. Sticky header: on scroll the big masthead collapses into a slim one-line bar (small mark left, nav right) that stays pinned. With prefers-reduced-motion: reduce, it swaps without animation.
  3. Mobile 390px: no horizontal scroll, nav inline with NO hamburger, the mobile masthead, 16px side gutters.
  4. Post page /writing/<slug>: a large title, the byline (as above), the diagram placed right after the byline and stored as EmDash media, and the body from EmDash content. [BEN: ...] and [TITLE: ...] show as visible yellow-highlighted callouts.
  5. About /about: the About copy + the sticker.
  6. Subscribe /subscribe: a styled email form with a disabled submit and a "coming soon" note. It sends nowhere.
  7. Favicon/app icons from I1 (16/32/180/512).
  8. Tokens: paper #EAF0FD, ink #111, single accent #3B82F6, grid ~#C9D8F5 (home band + margins only; plain paper behind article text). Self-hosted OFL fonts: Old Standard TT (masthead/headings), Nunito (body, a stand-in for Noway Round), JetBrains Mono, Kalam (notes, a stand-in for Ben's own font). Swapping each font = one CSS token.
  9. The post + About content live in EmDash and are editable in its admin. Evidence = wrangler d1 execute --remote output showing the post and About rows, plus one admin edit you make that shows up on the deployed page (then revert it). Without both, mark item 9 UNVERIFIED, not PASS.
  10. No console errors; alt text on images; AA contrast.

Verification (literal results)

Gates (owned by the parent, not you)

After your report, the parent runs ONE independent behavior-critic on the deployed URL against items 1-10. Don't self-certify beyond your literal evidence.

Stop conditions

State owner

You own the repo, branch, Worker, D1/R2 resources and preview route you create. The parent owns the vault, the spec, the founder channel and all merges to main. Do not merge your PR.

Report back (under 300 words)

Preview URL, PR link, PRE-DECOMP path, screenshot paths, items 1-10 each PASS or FAIL with evidence, EmDash admin sign-in steps for Ben, deviations, and open questions.