Home / Ops / More in this area

Affirmology Beta Rollout Plan (loose, living) - v1

Updated Jul 04, 2026 · Affirmology_BetaRollout_Plan_v1.md

Affirmology Beta Rollout Plan (loose, living) - v1

Owner: Jeff. Built in Cowork 2026-07-04. Share with Code for the engine/app workstreams. Decisions locked with Jeff on 2026-07-04 are marked [LOCKED].

The shape of it

We are NOT starting the beta on July 4. We honor the date by sending something real today (an expectations + affirmational-agreement email), then release a trail of personal gift audios across the week while the app and process get properly finished, and open the beta itself the following Friday. Care and craft over speed.

Locked decisions (2026-07-04)

• [LOCKED] Beta start date: FRIDAY 2026-07-10. (Back in the Miami office late Tue / early Wed, giving Wed-Thu to nail the app, starting audios, music beds, and process.)
• [LOCKED] Today's email (7/4): send today, aspirational framing ("we are rolling this out with care and craft"), no mention of the family trip. Honors the promise that this date delivers something.
• [LOCKED] The Mirror reading: goes to the FULL list Sunday morning 7/5, after Jeff and Sol listen and approve Friday night. (Staci possibly a pre-send, probably not; she gets it with everyone.)

Timeline

• Fri 7/4 (today): Expectations + affirmational-agreement email to the founding list. Secures each tester's "I'm in," sets both-ways expectations, promises the gift trail.
• Sat/Sun 7/5 (Sun AM): The Mirror reading (deeper chart reading, spoken) to the full list. New Audio card already wired on each results page (mirror_url). Jeff + Sol QC Fri night.
• Mon/Tue 7/6-7/7: A new audio to the list (structure TBD; Jeff steers within ~2 days).
• Wed/Thu 7/8-7/9: The written report (PDF) to the list.
• Late Tue / early Wed: back in Miami office, full time.
• Wed-Thu 7/8-7/9: finish the app, lock starting audios + music beds + process.
• Fri 7/10: BETA OPENS. App live, daily audio flow, feedback loop running.

Workstreams to be ready by 7/10

Code (engine / app)

• TestFlight: Sol's build currently has NO data. Sync her account/library so her app is populated (blocking; Jeff flagged). Confirm Jeff's + testers' data flows too.
• Starting audios + music beds: load the approved set once Jeff picks them (see below).
• The daily-listen flow in the app (Maya consumer app): a person's current audio, replayable, nightly cadence.
• Feedback capture in-app + a machine-learning testing loop: ask testers targeted questions, capture Love / Needs-work / preferences, generate variations, feed the engine so it learns, studies, reports, and adapts quickly. (Loose concept now; design detail to follow.)
• The Mirror MP3s (Fish / Dr. Young) for the list, exposed as mirror_url per person.

Cowork (comms / content / agreement)

• Today's expectations + affirmational-agreement email (drafted: Affirmology_BetaExpectationsEmail_v1.html).
• The gift-audio emails: Mirror (done: Affirmology_MirrorEmail_v1.html), the new audio, the report.
• The BETA TESTING AGREEMENT details (co-build here with Jeff): expectations both ways + affirmational commitment + confidentiality, and how it is secured (reply / click / e-sign).
• Beta onboarding: welcome, first-steps, the WhatsApp/circle invite.
• The tester WIKI / help content and short videos (what to expect, how to give feedback).
• Feedback forms + the tester question set that feeds the ML loop.

Jeff (steering, within ~2 days)

• Choose the STARTING AUDIOS (which structures lead) + the music beds.
• Approve the Mirror before Sunday's send.
• Finalize the beta agreement wording with Cowork.

The beta agreement - first-draft terms (to refine together in Cowork)

An "affirmational agreement," not a dry legal form. Both directions:

What we promise you (Affirmology): - Gifts coded to your own blueprint, made with care. - A founding place in the story, and a real hand in shaping the product. - Our attention: we listen to your feedback and adapt quickly.

What we ask of you (the tester): - Live with your audios: listen daily once the beta opens. - Tell us the truth: honest feedback, the good and the rough. - Keep it sacred: private to the founding circle for now. - Show up with us through the first weeks.

Secured by: an affirmation ("I'm in") today; a fuller signed/affirmed agreement at beta start 7/10.

Open items to confirm

• Exact wording + mechanism for the affirmational agreement (reply vs click vs e-sign).
• Which structures are the starting audios + which music beds.
• Whether anyone comes off the gift list (Jeff: probably everyone gets it).
• The tester question set for the ML feedback loop.