Home / Ops / The Locked Demo

Affirmology End-to-End Demo Plan v2 (the two-hour sprint)

Updated Jun 13, 2026 · Affirmology_EndToEndDemo_Plan_v2.md

Affirmology End-to-End Demo Plan v2 (the two-hour sprint)

Date: 2026-06-13. Supersedes v1. Reflects the pivot: no Higgsfield. The "video while the audio loads" becomes a web-native animated experience I build directly on the page, scored to the Lily trailer VO plus a music bed. The page itself is the demo video.

What changed from v1

• No Higgsfield, no external video tool. The loading sequence is animation and text I render on the page, in your locked cosmic palette, reusing the index1 opening style and the Gene Keys and Human Design SVG work.
• Soundtrack already exists: the Lily trailer VO. The 5 percent music version runs about 109 seconds and already has a bed under it, so it lands with zero extra production. You can swap in a richer Suno bed later as a one-file change.
• Downloads come first, email is a bonus. After the audio plays, the visitor gets on-page buttons to download their MP3 and their full PDF report, so they always leave with everything even if email never turns on.
• Hero copy stays pithy on the soul-song theme. "Subconscious Operating System" moves to the educational outro at the end, where it has earned its context.
• Lead capture stays light. Any simple record of what people enter is enough. If Go High Level fights us, we skip it and capture to a simple store instead.

The full visitor experience (the spine)

1. Cinematic intro plays (the opening you liked from index1).
2. Short NDA gate, confidential early access, name carries into the form.
3. They fill the form and submit.
4. The teaser experience plays: about two minutes of on-page animation and timed text in the cosmic palette, scored by the Lily VO and music bed, while their real audio renders in the background. This is the "demo video," made entirely on the page.
5. A ritual cue: find stillness, close your eyes, give it your full attention. One button: play my audio.
6. Their real personalized audio plays in the custom player.
7. Educational outro after it ends: this was a taste, imagine it for your relationships, your path, your business, we built the architecture for far more, stay tuned. A partial reveal of their report shows the placements that shaped the script (not the whole report). Then buttons: download your audio, download your full report, and optionally email me everything.

Who does what

I build (front end, on the page, now)

• Pithy hero copy fix on index.html.
• The teaser experience inside result.html: animation, timed text beats to the Lily VO, music bed, reusing the cosmic canvas and the chart SVG language.
• The ritual cue screen.
• The educational outro with the partial report reveal and the download buttons for MP3 and PDF.
• Wire the page to consume a real backend status when present, and fall back to a self-contained demo timeline when the backend is not reachable yet, so it always lands.

You handle

• Tailscale and backend connection from this laptop (you said you will optimize this in the other chat). The agent already renders real MP3 and PDF for strangers, so this is connection, not building.
• ElevenLabs: the Lily teaser voice is already rendered; the personal audio uses Charlotte in the agent. No action unless you want a new voice.
• Suno or other music bed under the teaser, optional upgrade. The current 5 percent version already works.
• Go High Level: only if it is easy. Otherwise we skip it and I capture form entries to a simple store.

We do together

• Repoint the form from the polished mock to the real API once your backend is reachable.
• One real end-to-end test submission.

Backend pieces (small, mostly code I write, you run)

• Add a status endpoint to the Mac server so the page can poll progress and receive the blueprint and the file URLs. [I write, you run]
• Serve the MP3 and PDF with public URLs over Tailscale Funnel so the download buttons and the email links work from anywhere. [you run, I prep commands]
• Deploy the Worker with its secrets. [together]
• Turn on email in Resend later, in parallel. Not required for the demo to land. [optional]

The two-hour target

• Hour 1: I ship the front-end experience end to end on the page, running on the self-contained demo timeline with the real teaser audio and a placeholder personal track, plus the partial report and download buttons. You can see and feel the whole thing live.
• Hour 2: we connect the real backend so the personal audio and the real report and downloads are the visitor's actual results. If the connection is not ready, the experience still lands on the demo timeline and we finish the wiring next.