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)
- EmDash setup: the documented path is
npm create emdash@latest. Confirm it against the current docs/README. - EmDash admin auth is passkey-first. Who owns the admin account for v0? Default: create it for ben@raydata.co if email or magic-link sign-in exists. If only a passkey is possible, set it up so the founder can register his passkey on first visit (an invite or first-run setup), and document the exact steps for him. Content for v0 may be seeded via EmDash's own seed/import/MCP mechanism; it must still live in EmDash (editable in the admin), not be hard-coded.
- Can the Worker be served on
denominator-preview.rdco.devbehind the EXISTING quick-sites wildcard Access app? If not, STOP and report (see Stop conditions).
Sources of truth (read first)
- Decisions log: ~/rdco-vault/01-projects/personal-brand/2026-10-02-site-spec.md ("LOCKED" + "Header behavior" lines win on any conflict)
- Locked masthead + icon artwork: ~/rdco-vault/01-projects/personal-brand/assets/wordmark/round4/ (S1-blue desktop + mobile, I1 icon incl. 16px, page-top-1440x900.png = the approved composition, round4-gen.py). WARNING: the round4 S1 SVGs and round4-gen.py (lines ~27, 40, 44) bake in a rule ABOVE the wordmark plus a folio line with the domain and tagline. Both contradict the locked header decisions. Make repo copies with the top rule and the folio text REMOVED (regenerate from a copy of the generator, or build the masthead in HTML/CSS/SVG). NEVER edit files in the vault's round3/ or round4/ folders. Note: round4-gen.py imports
round3, but only round3-gen.py exists, so copy round3-gen.py as round3.py next to your generator copy. - Headshot sticker cutout: ~/rdco-vault/01-projects/personal-brand/assets/wordmark/round3/headshot-sticker.png
- Post #1 draft: ~/rdco-vault/01-projects/personal-brand/drafts/2026-10-02-agents-need-your-definitions-v1.md. Title = its H1. Byline = draft line 13 verbatim, with its
[TITLE: ...]shown as a highlighted callout (the title is unconfirmed). Body = draft lines 15-73 (stop before the LinkedIn cut and "Ben to decide"). - Post #1 diagram: ~/rdco-vault/01-projects/personal-brand/assets/post1-one-agent-two-numbers.svg
- About copy (verbatim): "Most AI agent pilots don't fail on the model. They fail on the data underneath: definitions that drift, history that isn't kept, access nobody can audit. I help data leaders fix that layer so agents can run in production, on Snowflake and Claude." then "Claude Certified Architect – Foundations (Anthropic) · SnowPro Specialty: Gen AI and SnowPro Core (Snowflake)" then "Principal Consultant at phData. Views are my own."
Repo and output locations
gh repo create RayDataCo/the-denominator --private --add-readme(gh is authed as Ray-Ray-RayDCO; on INSUFFICIENT_SCOPES rungh auth switch --user Ray-Ray-RayDCO). Clone to/Users/ray/Projects/the-denominator. Work on branchfeat/v0-previewand open a PR into main. Do not push to main.- Screenshots go to
/Users/ray/Projects/the-denominator/verification/.IMPLEMENTATION-NOTES.mdat the repo root, updated as you go (decisions, deviations, failed commands and why). - Do NOT write anything into ~/rdco-vault (the parent cwd is the vault; don't let relative paths land there).
Cloudflare
~/.claude/scripts/wrangler.sh(fetches its token at call time) and~/.claude/scripts/cloudflare-api.sh. Run allow-listed commands STANDALONE: no&&chains, no env prefixes. Never write secrets to disk or the repo.- In wrangler config:
workers_dev = falseandpreview_urls = false. Route ONLYdenominator-preview.rdco.dev. - Access: the quick-sites wildcard Access app on *.rdco.dev already gates this host (allow: ben@, ray@). Create NO new Access app or policy. For your own signed-in checks, sign in the way ~/Projects/quick-sites/IMPLEMENTATION-NOTES.md describes (Playwright + an email OTP to ray@/ben@ via Gmail; see the ACCEPTANCE CONTRACT RESULTS entries around its lines 20-25).
- Add
<meta name="robots" content="noindex,nofollow">+ a robots.txt Disallow-all. - Free tiers only. Any paid spend: STOP and report.
What the site must do (acceptance contract)
- Home
/: the masthead (S1 blue), NO rule above the wordmark, bottom double rule kept. Under it, a folio line = centered small-caps navWRITING · 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. - 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. - Mobile 390px: no horizontal scroll, nav inline with NO hamburger, the mobile masthead, 16px side gutters.
- 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. - About
/about: the About copy + the sticker. - Subscribe
/subscribe: a styled email form with a disabled submit and a "coming soon" note. It sends nowhere. - Favicon/app icons from I1 (16/32/180/512).
- 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.
- The post + About content live in EmDash and are editable in its admin. Evidence =
wrangler d1 execute --remoteoutput 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. - No console errors; alt text on images; AA contrast.
Verification (literal results)
- Deploy to the preview, then do ALL checks against the DEPLOYED, signed-in URL (not localhost; local D1 differs). A signed-in fetch of the deployed
/and/writing/<slug>must show post #1's title. - Playwright screenshots on the deployed site:
/,/scrolled (sticky state),/writing/<slug>,/about,/subscribe, at 1440 and 390. READ every PNG and fix issues first. - Public-reachability evidence: an unauthenticated curl of the Worker's workers.dev URL (and any version/preview URL) must return no post content.
- Do NOT use an unauthenticated curl 302 as evidence (every *.rdco.dev host 302s to Access, deployed or not).
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
- Any classifier denial on a deploy or production-looking write: stop after ONE denial, don't retry or route around it via another wrapper, and report the exact command.
- Paid spend, any domain/DNS change outside the denominator-preview.rdco.dev route, any new Access app/policy, or anything that would make the site publicly reachable: stop and report.
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.