Home / Ops / More in this area

Affirmology PDF Report - working notes (current state + where we can take it)

Updated Jun 27, 2026 · Affirmology_PDFReport_Notes_v1.md

Summary. 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.

Affirmology PDF Report - working notes (current state + where we can take it)

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.

What the PDF is

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).

How it is built (architecture)

Canonical files (edit THESE - the top-level affirmology-agent/ is a stale copy)

The 5 pages (current structure, verified from the template)

  1. Cover - AFFIRMOLOGY brandmark, title "Your Personal Sacred Audio", italic subtitle naming the four systems, "For {Name}", birth line, then three short sections: What This Audio Is / How To Use It / The Purpose.
  2. Your Cosmic Blueprint - four pillars (Astrology; Gene Keys Activation Sequence; Human Design; Numerology), each a key/value list, then "The Throughlines" synthesis paragraph. 3-4. Your Sacred Audio · The Script - full script, broken into sections; each section has a Roman-numeral heading, an italic gold chart-source subhead (e.g. "Gene Key 50.2 (Life's Work) · Sun in Libra 12th House · Soul Urge 2"), then the verbatim first-person lines.
  3. How This Was Built From Your Blueprint - five diamond bullets (the spine, body integration, closing anchor, walking anchors, voice and pacing), an italic centered closing blurb, and a heart flourish.

Current styling (the inline CSS, verified)

Gold standard reference

Known gaps / opportunities (candidate work for the Cowork session)

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.

Open questions for Jeff (decide in the Cowork session)

  1. Is the goal a VISUAL redesign (add chart wheel / bodygraph / cover art / brand font), a CONTENT upgrade (deeper data, better prose, more pages), or both?
  2. Keep WeasyPrint (HTML+CSS, easy to restyle, weak on complex graphics) or move to a layout engine that handles chart graphics better?
  3. Print-first (Letter PDF) or screen-first (the in-app reader)? Or both as two templates?
  4. Upgrade the fill model from Haiku to Opus for the prose sections?
  5. What exactly about the current PDF feels short of the Josh Parini gold standard?

How to render a test PDF (verify any change)

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.