Home / Ops / Housekeeping and Process

Affirmology Web Flow: Handoff to the Webpage-Building Chat

Updated Jun 13, 2026 · Affirmology_WebFlow_Handoff_v1.md

Summary. Copy-paste this into the chat that is building and updating the web pages. It aligns the live site with the video/marketing assets so the whole flow feels like one piece. Read AffirmologyPROJECTSTATE.md first; this is a supplement focused on the consumer web f

Affirmology Web Flow: Handoff to the Webpage-Building Chat

Copy-paste this into the chat that is building and updating the web pages. It aligns the live site with the video/marketing assets so the whole flow feels like one piece. Read Affirmology_PROJECT_STATE.md first; this is a supplement focused on the consumer web flow.

The consumer flow (in order)

  1. Intake page (demo-site-v1/index.html, live at demo.affirmology.ai): name + birth date/time/place + email. On submit, the real custom audio + PDF report begin rendering on the backend.
  2. Loading film / primer plays while the audio renders: Affirmology_Primer_v5.html. A cinematic cosmic trailer (Lily VO) that primes the listener. It ends on a "ready" hand-off with two buttons (see below).
  3. Results page (you already have this: CLAUDE OUTPUTS/Affirmology/demo-site-v2/result.html, per PROJECT_STATE section 5): the ~2 minute web-native teaser (Lily trailer VO + music bed), ritual cue, the personalized audio player, an educational outro, a partial report reveal, and the two download buttons (MP3 + PDF). This handoff is to ALIGN that page with the trailer/upsell assets and the locked look, not to rebuild it. It must always reflect the exact person and chart entered, never a stock example.
  4. Optional upsell / what's-in-store concept piece: Affirmology_WhatsInStore_v2.html (Lily VO, hammers the use cases). A marketing concept reel, not the results page. It now ends on the same two download boxes so the language matches.

What the two end-buttons must be (everywhere)

Not membership. The two actions are: - Download your audio (the rendered mp3 the user just heard) - Download your report (PDF) (the Sacred Audio Report)

In the primer and the upsell these are inert placeholders (commented /* wire to ... */). On the real results page, wire them to the rendered files returned by the backend (the /api/status/{job_id} response should carry the audio URL and the PDF URL). Status copy should read "ready," not "preparing," once the render is done.

Locked design system (match this exactly so it all feels like one brand)

Brand and copy rules (enforce on every page)

Voices (three different assets, on purpose)

Assets you can pull from (this chat built them)

Alignment checklist for the existing result.html

Since result.html already exists, the work is to make it match the trailer assets: - Same palette, fonts, and texture stack as above (so the teaser, audio player, and report reveal feel like one piece with the primer). - The teaser uses the Lily trailer VO; confirm it is the synced version and that the music bed sits under it. - Status copy reads "ready," not "preparing," once the render completes. - The two download buttons stay exactly: "Download your audio" and "Download your report (PDF)," wired to the real rendered files from /api/status/{job_id}. - Optionally lift visual components from Affirmology_Primer_v5.html: the lit-up Human Design bodygraph (centers and channels light in sequence), the audio-wave bridge (concentric sound rings + stacked waveforms), and the non-overlapping word-slot system, for the teaser and the report-reveal moments. - Two animation variants of the "video while audio loads" slot now exist (this chat's Affirmology_Primer_v5.html and the web-native teaser in result.html). Pick one as canonical so the flow is consistent; they share the look and the Lily VO.