Home / Ops / Housekeeping and Process

Affirmology Session Notes: Mirror Audio Feedback (Structure and Tone)

Updated Jul 08, 2026 · Affirmology_MirrorAudioFeedback_SessionNotes_2026-07-05_v1.md

Summary. The new Mirror version does not land. Both Jeff's and Sol's audios repeat problems already flagged in prior feedback rounds. Sol: "I don't have any new feedback. This is all stuff you've already said."

Affirmology Session Notes: Mirror Audio Feedback (Structure and Tone)

The verdict

The new Mirror version does not land. Both Jeff's and Sol's audios repeat problems already flagged in prior feedback rounds. Sol: "I don't have any new feedback. This is all stuff you've already said."

What is wrong

  1. Intro is word salad. Vague, wasted words, no hook, no promise. Needs an epic opener in the spirit of "everything in your life has led to this one thing, and it will make all the difference for you right now."
  2. No open loops, no closed loops, no rehooks. It reads as a random list of chart elements, not a connected journey.
  3. Tone skews negative and doom-heavy. Both audios surfaced a negative early (Jeff's tension point, Sol's "bad decisions" framing). Listeners come for empowerment, guidance, and positivity. Tension/drama is allowed as a MID-audio rehook, never the opener.
  4. Metaphors misapplied. One of Sol's earlier audios drowned in one giant overextended metaphor and lost the plot. Metaphors must be grounded, practical, and in service of the point (the Wealth Codes candle flame and water imagery is the benchmark).

What the audio must be

Open question raised

Does the Mirror need a defined context or purpose (like Wealth Codes had "wealth") to reduce generation guesswork? For example "purpose, wealth, and what your progression says right now." Explore proposals.

Explicit asks from Jeff

  1. Go back through all Wealth Codes notes and both Wealth reading transcripts (Affirmology_WealthReading_Transcript_Jeff_v1.md, Affirmology_WealthReading_Transcript_Sol_v1.md) and test the current Mirror methodology against them. Propose ways to close the gap.
  2. From now on, every test script email must include a technical background section: the structural decisions and choices made, the levers pulled and NOT pulled, and the chart content chosen and not chosen, so Jeff and Sol can diagnose, debug, and propose alternatives.