Home / Archive / More in this area

Affirmology End-to-End Demo Plan v1

Archived version Updated Jun 13, 2026 · Affirmology_EndToEndDemo_Plan_v1.md

Affirmology End-to-End Demo Plan v1

Date: 2026-06-13. The plan to take the live demo from "looks finished" to "actually works for a real visitor," piece by piece.

The headline you should know first

End-to-end already works offline. On May 29 and June 2 the agent produced complete demos for two strangers, Alex Carper and Colin: a real mixed mp3 (Charlotte voice over the Heavenly Circuit bed) and a benchmarked Sacred Audio Report PDF, plus a backend payload that holds the exact cosmic blueprint that informed the script. The calculation engines, script generator, voice synthesis, music mix, and PDF report all run.

So this is not a build from scratch. It is a plumbing job: connect the pretty site to the working agent, expose the agent over the internet through your laptop, and turn on email. That is the whole gap.

What "end-to-end" means here (the visitor's path)

1. Visitor lands on the cinematic site at demo.affirmology.ai.
2. They agree to the short NDA, watch the intro, fill the form.
3. The form posts to the API. Your laptop receives it and starts rendering.
4. The visitor waits on a beautiful screen. If a trailer video exists, it plays during the wait. If not, the breathing wait screen carries it.
5. The laptop computes their chart, writes a personalized script, synthesizes the voice, mixes the music, and renders the PDF report.
6. The result page reveals: an audio player with their real audio, and below it the report showing the placements that shaped their script.
7. They also get an email with the audio link and the PDF, benchmarked to our prior examples.

The pieces, in build order

Ownership tags: [ME] I can do it in the files or the browser. [JEFF] runs on your Mac Terminal or your accounts. [BOTH] we do it together live.

Piece 0 - Get the pretty site live as a static page (today, low risk)

Purpose: guarantee the prettier animated version exists at demo.affirmology.ai right now, even before the backend is wired. The form still runs its polished mock until Piece 3 flips it to real.

• [JEFF] In Cloudflare dashboard, Workers and Pages, open the existing Pages project for demo.affirmology.ai. Use Create deployment, or drag-drop upload, and upload the three files from the demo-site-v2 folder: index.html, result.html, and the assets folder (heavenly-circuit.mp3). Confirm demo.affirmology.ai shows the new headline "One voice. One chart. One healing." and the NDA gate.
• Alternative if you prefer Terminal: cd "/Users/jeffreyparker/CLAUDE/AFFIRMOLOGY/CLAUDE OUTPUTS/Affirmology/demo-site-v2" && npx wrangler pages deploy . --project-name=affirmology-demo. Confirm the project name in the dashboard first so you do not create a duplicate.

Piece 1 - Prove a fresh render locally (today, the critical test)

Purpose: confirm the pipeline still runs green on this machine before we expose anything.

• [JEFF] In Terminal: cd "/Users/jeffreyparker/CLAUDE/AFFIRMOLOGY/affirmology-agent" source .venv/bin/activate # confirm the ElevenLabs key is set (voice synthesis needs it) echo $ELEVENLABS_API_KEY python -m affirmology.cli --name "Test Visitor" --date 1990-07-15 --time 14:20 --location "Miami, FL, USA" --audio --music "music/Heavenly Circuit.mp3" --voice-offset 8.0 --out out/smoke_test
• [BOTH] Send me the tail of the output. We confirm it produced an mp3 and a SacredAudioReport.pdf in out/smoke_test. If WeasyPrint or ElevenLabs errors, we fix that here. This is the single most important checkpoint; everything downstream assumes this is green.

Piece 2 - Add status and file serving to the Mac server [ME, then JEFF runs it]

The server already accepts the job and webhooks back. It needs two more things so the page can show results and play audio: - A GET /status/{job_id} endpoint that returns: state (pending, rendering, done, failed), the blueprint payload (the astrology, gene_keys, human_design, numerology arrays), and the public file URLs once done. - Static file serving of the out directory so the mp3 and PDF have real URLs. - [ME] I write these into server/api.py and adjust the Worker contract to match.

Piece 3 - Flip the front end from mock to real [ME]

• index.html: change the submit handler so it POSTs the form to /api/render and then routes to result.html with the returned job id.
• result.html: replace the simulated poller with a real poll of /api/status/{job_id} through the Worker. On done, set the audio player source to the real mp3, set the PDF download link, and render the report sections from the real payload. Add the conditional video: if a trailer URL is configured, play it during the wait; otherwise keep the breathing wait screen.

Piece 4 - Expose the laptop to the internet over Tailscale Funnel [JEFF, I prep the commands]

Purpose: the Cloudflare Worker and the visitor's browser must reach your laptop. Tailscale is already installed (machine macbook-pro-2, IP 100.98.80.60). Funnel makes one port publicly reachable with automatic TLS. - [JEFF] Run the FastAPI server, then open the funnel. Exact commands come after Piece 1 passes, but the shape is: cd "/Users/jeffreyparker/CLAUDE/AFFIRMOLOGY/affirmology-agent" source .venv/bin/activate PYTHONPATH=src AFFIRMOLOGY_AUTH_TOKEN=<shared-secret> uvicorn server.api:app --host 127.0.0.1 --port 8443 # in a second Terminal tab: tailscale funnel 8443 - The funnel gives a public https URL like https://macbook-pro-2.tailXXXX.ts.net. That becomes the Worker's MAC_MINI_URL.

Piece 5 - Deploy the Worker with secrets [BOTH]

• [JEFF] From the worker folder, set the secrets and deploy: cd "/Users/jeffreyparker/CLAUDE/AFFIRMOLOGY/affirmology-demo-site/worker" npx wrangler secret put MAC_MINI_URL # the funnel https URL from Piece 4 npx wrangler secret put MAC_MINI_AUTH_TOKEN # the same shared secret as the server npx wrangler secret put RESEND_API_KEY # from Piece 6 npx wrangler secret put FROM_EMAIL # hello@affirmology.ai npx wrangler deploy
• [BOTH] Hit demo.affirmology.ai/api/health to confirm the Worker is live, then run one real submission end to end.

Piece 6 - Turn on email [JEFF accounts, ME templates]

• [JEFF] In Resend, add and verify the affirmology.ai domain. That means adding the DNS records Resend gives you into Cloudflare DNS. Create an API key.
• [ME] The Worker already has confirmation and delivery email templates. I tune the copy and make sure the links point at the funnel URLs. Email is independent of the on-page result, so we can verify it in parallel without blocking the visit.

Piece 7 - Conditional video [BOTH, only if a trailer exists]

• If and when the Higgsfield trailer cut exists, drop the file in assets and set one variable. The wait screen plays it; if the variable is empty, nothing changes. Built to be a one-line switch so it never blocks the demo.

Decisions I need from you to move fast

1. ElevenLabs: is the API key already on this machine in the agent env, or do we set it in Piece 1? Voice is the one paid external call in the render.
2. File hosting: I recommend serving files straight from your laptop over Tailscale Funnel for the demo, so we need zero new infrastructure. Cloudflare R2 is the later upgrade for when the laptop should not be the host. Good to go with Funnel for now?
3. Email: do you have a Resend account, or should we use a different sender (the notes mention Go High Level)? This only gates Piece 6, not the on-page experience.

Today's realistic target

Pieces 0, 1, 2, 3 are achievable today and give you a real working visit on this network: submit the form, watch the wait, hear the real audio, see the blueprint. Pieces 4 and 5 make it reachable from anywhere over the internet. Piece 6, email, can follow in parallel. We go one piece at a time and confirm each before the next.