Home / Ops / More in this area

Affirmology - Weekend Operating Plan (Fri 7/10 → Mon 7/13)

Updated Jul 10, 2026 · Affirmology_WeekendPlan_v1.md

Affirmology - Weekend Operating Plan (Fri 7/10 → Mon 7/13)

Written 2026-07-09 (evening) by the DATA/engine chat, from Jeff's direction. Operational companion to Affirmology_BetaRollout_Strategy_v1.md (the strategy). This doc is the day-by-day checklist with owners.

The frame (unchanged): email is dead for this group and they think they already said yes. Channel is a personal text. Reframe = "you're already in, make it official." Full launch is Sun/Mon, but we honor the promised date by texting the commit link Friday.

STATUS AS OF TONIGHT (what is DONE and verified)

• ✅ The commit form is LIVE and end-to-end verified. agreement.html was never deployed (returned 404) - deployed tonight (affirmology-site version c851baab). A real test commit landed in the backend as status: committed with all six commitments recorded, CRM updated, confirmation email fired.
• ✅ Tracked personal links live for all 17 people - https://demo.affirmology.ai/r/<code>?to=commit drops the identity cookie, logs the click, and routes to that person's commit form. Codes: alexcarper, alexdc, anthony, arezu, edith, elizabeth, jeanette, josh, kara, lauren, leandro, marcie, mio, norm, staci, taylor, tracie.
• ✅ Identity linking - text link, email link, and audio-email all resolve to one person.
• ✅ Engagement tracking - results_open / song_play / mission_film_play (+depth) / pdf_open / im_in_click, per person.
• ✅ Holds enforced - Amy Dholakia, Andrew Hague, Jenny Pruitt, Patrick Hilsbos, Mark Cleveland, Olga excluded.

NOT YET READY (the weekend's real work)

• ❌ The text copy for Friday (Cowork owns).
• ❌ The post-commit sequence (what happens the moment someone signs → TestFlight instructions).
• ❌ TestFlight onboarding flow + the app being ready for feedback (Code/app lane + Jeff & Sol).
• ❌ New music beds tested, the initial journey locked.
• ❌ Wiki, WhatsApp group, explainer video.
• ❌ Mirror + a few test audios rendered for the first cohort.

FRIDAY 7/10 - honor the date with a warm personal text

Goal: get the 17 to officially commit (sign the boxes), NOT full launch.

1. Cowork finalizes the commit-text copy - short, warm, "you're already one of us, this makes it official." Ends on the person's link: https://demo.affirmology.ai/r/<code>?to=commit.
2. Jeff (+ Sol) test the flow first using the founder test links (above) - click through, sign the boxes, confirm the confirmation email arrives and reads right.
3. Jeff texts the 17 by hand (small list, personal). Not a blast.
4. Watch commits land in real time: - Backend log: GET https://affirmology-studio-api.onrender.com/api/admin/beta-submissions (header Authorization: Bearer <studio token>). - Click/engagement: GET https://demo.affirmology.ai/api/admin/track?key=<TRACK_ADMIN_KEY>.

SATURDAY 7/11 - build the post-commit machine + content

1. Define the post-commit sequence (Cowork + Jeff): the moment someone signs → they get TestFlight instructions. Decide when (immediate vs staged), how (text vs email via /r/ link), and who sends.
2. TestFlight instructions written (Cowork copy) - download TestFlight, tap the invite, open the app. Maya invite: testflight.apple.com/join/nDJacr85 · Atlas: testflight.apple.com/join/nF94AdXC.
3. App ready for feedback (Jeff + Sol + Code lane): app updates in, initial journey locked, new beds tested. Sol and Jeff run the first-run experience themselves - that first moment is the one we cannot redo.
4. Render the first-cohort audios (DATA/engine): the Mirror + a few test audios, so committers have something waiting. Local Fish render for the Mirror; verify each with audio_qc before it ships.
5. Stand up onboarding assets (Cowork): wiki (content + home), WhatsApp broadcast channel + optional group, explainer video (script → record).

SUNDAY 7/12 - soft launch to committers

1. As commits land, send each committer their TestFlight instructions + welcome into the app.
2. Open the WhatsApp channel right before beta begins (per the agreement copy).
3. First cohort has the app in hand; daily journey begins; wiki + video live.

MONDAY 7/13 - real launch / widen

1. Confirm the first cohort is active and giving feedback.
2. Widen as ready; keep every future email/text linking through /r/<code> so identity stays connected.

OWNER SPLIT (this weekend)

• DATA/engine (this chat): site + links + tracking (DONE), render the Mirror + test audios, keep infra green.
• Code/app chat: TestFlight build + invites, app updates, initial journey, in-app library.
• Cowork: commit-text copy, post-commit sequence, TestFlight instruction copy, wiki, WhatsApp, explainer video.
• Jeff + Sol: test the commit flow, test the app first-run, send the personal texts, final go/no-go on launch.

THE ONE DECISION THAT GATES EVERYTHING

Post-commit → what happens next. Until that sequence is defined (TestFlight instructions: when/how/who), Friday's texts create commitments with no defined follow-through. Define it Saturday morning first.