Home / Ops / More in this area
Updated Jun 27, 2026 · Affirmology_PDFReport_Notes_v1.md
Logged 2026-06-27. This is the single notes file for the per-person Sacred Audio PDF report (the printed/downloadable "blueprint" that ships with every audio). Read this before touching the PDF. No em dashes anywhere in output.
A 5-page, print-quality PDF that accompanies each person's Sacred Audio. It explains, in warm precise prose, what the audio is, the person's cosmic blueprint across the four systems, the full script with chart-source labels, and how the script was built from their chart. The gold-standard target is the Josh Parini reference PDF (see below).
pango cairo gdk-pixbuf libffi; the pipeline sets DYLD_FALLBACK_LIBRARY_PATH to find them.claude-haiku-4-5-20251001, max 8000 tokens) takes the birth data + chart JSON + the finished script, and returns ONE structured JSON object (cover paragraphs, four pillar key/value lists, throughlines paragraph, script sections with chart-source subheads, five build-note bullets, closing blurb). Override the model with env ANTHROPIC_PDF_MODEL (or ANTHROPIC_MODEL_PDF).affirmology-agent/ is a stale copy)affirmology-studio/affirmology-agent/src/affirmology/agents/sacred_audio_report.pyclaude-haiku-4-5-20251001)affirmology-studio/affirmology-agent/templates/sacred_audio_report.html (307 lines; all styling is the inline <style> block, lines 6-231)affirmology-studio/affirmology-agent/src/affirmology/cli.py lines ~820-836 (fires on --audio when a mixed MP3 exists and --no-pdf is not set; failure is non-fatal, audio still ships)affirmology-studio/api/pipeline.py lines ~225-301 (PDF produced in the audio phase, progress marker "Sacred Audio Report PDF" at 90%)affirmology-studio/api/storage.py (local dir or R2 upload, content-type application/pdf)affirmology-studio/api/jobs.py lines ~801-808 (save to R2) and ~818-890 (email includes "Open your PDF report" link)#1a1410, soft gray #555048, burgundy #5b1c20 (headings), gold #b08a3e (accents), rule #c9a85a (dividers).Affirmology_JoshParini_SacredAudio_v1.pdf (project root, also in baselines/). The Haiku prompt is explicitly told to match its warmth and precision.These are observations, NOT decisions. Jeff drives which to pursue: - No visuals. No chart wheel, no Human Design bodygraph, no cover image, no per-pillar glyphs. Pure text. Biggest visual-impact lever. - No embedded fonts / brand identity. Falls back to system serifs. A real brand typeface (embedded) would lift it from "document" to "artifact." - Fixed length / density. Same 5-page skeleton regardless of how rich the chart or how long the script. Long scripts can overflow pages 3-4 awkwardly. - Model is Haiku. Fine for structured extraction, but the prose synthesis (throughlines, build notes, cover paragraphs) is where a stronger model (Opus 4.8) could noticeably raise the writing quality. One call, so cost impact is small. - No cover art / dedication page. A first-impression page (image + name + a single line) before the brandmark cover could feel more like a gift. - Print vs screen. Currently print-first (Letter, serif). A screen/mobile-optimized variant (the app opens it in player.html) may want a different layout. - Charts data depth. The pillars show top-line placements. Could include more (all gates, defined channels, full numerology stack) or a fold-out "full data appendix" page.
From affirmology-studio/affirmology-agent/, the CLI --audio path produces the PDF next to the MP3 as {FirstLast}_Affirmology_Demo_v{N}_SacredAudioReport.pdf, with the intermediate HTML + Claude payload saved under out/{job}/backend/ for inspection. The fastest visual iteration loop is editing the template HTML and re-rendering that saved backend HTML through WeasyPrint directly, without re-calling Claude.