← Operating Docs · Everything left before June 1

Launch Punch List — Everything Left

Date: May 18, 2026 T-6 days to Foundation Cohort outreach (May 24) T-13 days to public launch (June 1) Status: ~70% of launch infrastructure is shipped. The remaining 30% is the difference between a quiet launch and a real one.

Organized by who owns it. Items in bold are critical-path — if they slip, launch slips.


🔴 BRIAN — only you can do these

Critical path (must hit by date)

Date Task Why it matters
May 19-20 Film Atlanta boardroom block — A1, A2, A3, A4, A5, A6, A7 in one morning One outfit, one room, 4 hours. After May 21 you don't get this lighting/setting back until you fly back.
May 21 Finish GHL Workflow 1 — 22 actions following /docs/ghl-workflows.html Without it, May 24 outreach doesn't fire.
May 22 Verify Stripe Foundation Cohort price routing — test a self-checkout with the foundation tag applied Without this, patients click the link and see $19.99 instead of $9.99. Trust dies.
May 22 Test scan flow on production end-to-end (and every day until launch) Catches regressions before customers do. 60 sec/day.
May 23 Bulk-tag 300 patients in GHL with foundation-cohort-2026 This is the trigger. Without the tag, the workflow doesn't fire.
May 23 Film Foundation Cohort Touch 2 video (90 sec) — Fort Myers home office Email sent May 27 needs this. Rough is fine — intimacy beats polish.
May 24 Send Touch 1 manually OR confirm workflow fired at 10 AM ET Don't trust automation on Day 1 without sanity check.

High-leverage but flexible

Nice-to-have


🟡 CHRISTIANE — needs your push to start

Critical for content velocity post-launch


⚙️ AUTOMATION — I can do these (just need your green-light)

Priority Task Time
HIGH Wire AI agent system prompt into GHL PV subaccount (paste GHL_AGENT_SPEC.md) Browser is unstable for GHL drives — better to give you a copy-paste guide
HIGH Build GHL Workflow 2 (Slot Decision Webhook) Code endpoints already live; just needs the GHL workflow side, same fragility issue
HIGH Build GHL Workflow 3 (Conversion Hook) Same as Workflow 2 — needs GHL side wiring
MEDIUM Set up a synthetic uptime check on posture.vision/dailycheck — cron pings the page every 5 min, fires Pushover if it stops loading or scan stream fails 30 min build
MEDIUM Pre-populate 7 days of Pending Posts before June 1 — fire all the crons manually with a --lookahead=7 flag 15 min — already have the cron logic
MEDIUM Wire Foundation Cohort conversion → Pushover with patient name + count (per Workflow 3 design) 20 min, ties to my brand mention monitor pattern
MEDIUM Tighten the Foundation Cohort landing page copy — needs final headline + CTA. Want me to draft? 1 hour
LOW Build "launch day runbook" — every alert that fires, every dashboard to watch, every backup plan 1 hour, fully written doc
LOW Audit all 8 PV email sequences for legal claims that need RTBs cited per Christiane's deck Section 14 1 hour

🚨 RISK CHECK — what I'm worried about

#1: Foundation Cohort fires but signups stall

Scenario: 300 emails go out May 24. Click-through is fine but Stripe routing is broken — customers see $19.99 instead of $9.99. They abandon. Trust damage compounds.

Why I'm worried: Stripe routing has not been verified end-to-end. You said "Stripe is wired" but the lock-in price is a NEW behavior, not the standard checkout.

Fix: Today or tomorrow — apply tag foundation-cohort-2026 to your own contact record, then visit your signup URL. If it doesn't show $9.99/mo, debug NOW not on launch day.

#2: Scan flow regression on launch day

Scenario: A code merge between now and June 1 breaks scan baseline-lock or scoring. Three days into launch you realize half your signups never completed their first scan.

Why I'm worried: Scan flow has 5 phases (BUFFERING → BASELINE_LOCK → READING → SCORING → REVEAL). Each adds failure surface.

Fix: Run the scan once a day on production. Set a calendar reminder. 60 sec each.

#3: Brian gets buried in DMs

Scenario: 300-patient outreach triggers a DM avalanche. Without the AI agent live, you respond to each one. Investor demos slip because you're stuck in inbox.

Why I'm worried: AI agent prompt is written (GHL_AGENT_SPEC.md) but not deployed.

Fix: Paste it into the PV GHL subaccount AI agent settings TODAY. 15 min of work, saves 15 hours during launch week.

#4: Content engine drafts something off-brand

Scenario: Engine ships an Instagram post during launch week that uses one of the forbidden phrases ("cure your pain", "transform your life", "doctors hate this") because a voice profile drift wasn't caught.

Why I'm worried: New persona profiles just deployed. Theoretically tested, not battle-tested.

Fix: Approve EVERY post manually in the Weekly Review tab during launch week. The engine drafts; you approve. Auto-publish after June 8.


What's truly done (so we know the floor)

Don't underestimate what's shipped. Inventory:

If everything else falls apart and we just ship these, you have a real launch. The remaining work makes it a GOOD launch instead of just a real one.


Honest priority order if I had to pick 5 things this week

  1. Verify Stripe Foundation Cohort price routing — single highest risk point
  2. Film Atlanta boardroom block — non-recoverable opportunity
  3. Finish GHL Workflow 1 (22 actions) — Foundation Cohort launches without it
  4. Paste AI agent system prompt into GHL PV — DM avalanche protection
  5. Daily scan-flow test on production — catches regressions before customers do

Everything else is gravy.