01-projects / mac-landing

build spec

Mon May 04 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·project-spec ·status: in-build
maclanding-pagecoming-soondrip-campaignshipping

MAC Landing Page - v0 Build Spec

Greenlit by founder 2026-05-05 16:29 ET in iMessage. Coming-soon page for the MAC info-product, with email collection + Resend-Automations drip campaign. First load-bearing equity-bearing product per the Naval framework execution plan filed earlier today at ../positioning/2026-05-05-rdco-vs-naval-get-rich-framework (action #1: Ship MAC v0).

Positioning

Core hook (already drafted, working as opener):

“TDD changed how we write code. Evals changed how we benchmark LLMs. MAC is how we prove our data models work.”

Founder’s new directives layered on:

Sub-themes (already in the anchor article):

Confidentiality scrub (MANDATORY before publication)

The existing anchor article at ../data-quality-framework/content/2026-04-15-mac-anchor-article-draft-v1 references “gold_opp_pipeline at the Mammoth Growth / Progress engagement” with specific test counts (14 -> 95) and a UAT bug count (3,227 rows). Per the MG 2022 confidentiality clause (see ../../06-reference/internal-review-mg-harness-cc-wrapped-2026-04-13):

This must happen BEFORE the page goes live on the public domain. The prototype on the .raydata.co subdomain is technically still live but lower-stakes; safest path is scrub during the build.

Tech stack (locked, RDCO standards)

LayerChoiceRationale
FrameworkAstroAlready running SC v9.7.4 + squarely-web on Astro
HostingCloudflare PagesAlready running both above on CF Pages
DNSCloudflare DNSraydata.co zone already on CF
Email transactionalResendAlready wired for SC welcome emails
Email dripResend AutomationsNative drip product (founder confirmed 2026-05-05). Event triggers, conditional branching, delays, audience management. NO Loops, NO ConvertKit, NO roll-our-own.
Form submissionCF Pages FunctionServer-side endpoint that adds to Resend Audience + triggers Automation
Bot protectionCloudflare TurnstileAlready wired for SC subscribe form
AnalyticsFathomAlready paid for, drop-in script
RepoRayDataCo/mac-landing (NEW)PR-only workflow per memory rule
Domain (prototype)mac.raydata.coCF DNS record, no purchase needed
Domain (production)modelacceptancecriteria.io (founder buying)Plus modelacceptancecriteria.com redirect

Design spec

Founder’s explicit directives:

Design references named:

Existing memory alignment: ../../../.claude/projects/-Users-ray/memory/feedback_design_taste_high_personality - “founder leans hand-drawn / engraving / glitch / Memphis over flat / Bauhaus / modern-minimal. Texture and character beat restraint.”

Translation to MAC page:

Page structure (initial v0)

  1. Hero: blocky/graffiti headline + 1-line dek + email-capture form
  2. The hook section: TDD-evolved-for-data positioning (“TDD changed code. Evals changed LLMs. MAC for data.”)
  3. The problem: “Your tests are in one cell” with the matrix visual
  4. The framework: Scope x Basis 3x6 matrix shown visually
  5. The agent multiplier: Jevons-paradox-friendly framing (95 tests workable when agents handle the triage)
  6. What you’ll get: 7-email drip course teaser
  7. Email-capture CTA (repeat)
  8. Author bio: 1-paragraph credibility (de-identified MG accomplishments + RDCO context)
  9. Footer: minimal, link to Sanity Check + raydata.co

Drip campaign sequence (proposed v0, 7 emails over 14 days)

Day 1 already drafted at ../data-quality-framework/content/2026-04-15-mac-drip-day1-draft-v1 - “Your tests are in one cell.”

Proposed sequence (subject to founder review):

Each email: 250-500 words. Reusable infrastructure pattern that can serve future products too.

Form submission flow

User fills email + Turnstile + clicks subscribe
  -> POST /api/subscribe (CF Pages Function)
    -> Verify Turnstile token
    -> Add contact to Resend Audience "MAC Waitlist"
    -> Resend Automation trigger "user.subscribed.mac" fires
      -> Day 1 email sent immediately
      -> Day 3 email scheduled
      -> ...
    -> Set sc_subscribed_mac=true cookie (1 year, similar to SC pattern)
    -> Return 200 { ok: true, status: "subscribed" } OR { ok: true, status: "already_subscribed" }
  -> Client swaps form for "you're in" panel before paint

Mirror the SC v9.5 pattern (same dedupe logic, same cookie-based recognition, same Turnstile invisible-mode).

Open questions

  1. Drip cadence approval: 7 emails over 14 days as proposed, or different cadence?
  2. Author bio content: how much MG-era credibility to include after de-identification scrub?
  3. Footer link strategy: hard-link to Sanity Check newsletter signup as cross-promo, or stay focused on MAC?
  4. First-CTA destination after drip ends (day 14): waitlist for paid course? Book pre-order? Consulting inquiry? Need a “what’s next” gate.

These can be resolved after the initial preview ships.

Acceptance criteria for v0 ship