Home / Ops / More in this area

Affirmology Audio Possibilities Map v2 (the Beta Action Map)

Updated Jul 11, 2026 · Affirmology_AudioPossibilities_Map_v2.md

Affirmology Audio Possibilities Map v2 (the Beta Action Map)

Built 2026-07-11. Supersedes v1 as the WORKING map. v1 (Affirmology_AudioPossibilities_Map_v1.md) remains the deep palette reference for the nine building-block families and the full S1-S19 idea bank detail; this v2 adds what Jeff asked for today: the ranked build order for beta, the new 7/11 corpus findings, the Habit Engine (the app UX layer that makes this habit-forming, ethically), the Assimilation Engine (how all knowledge keeps compounding), the concrete testing kit, and the now/next/later roadmap.

Standing rules unchanged and non-negotiable: everything chart-driven; structures are named templates, content always from the person's chart; style shared, content never shared; all audio through our engine with QC; no em dashes; never name Joe Dispenza; felt-experience claims only; block surfacing stays gentle.

0. THE SORT: ranked build order for beta (do these in this order)

v1 asked a sorting session for exactly this output: ranked order, what each item needs, who builds it, which metric it answers. Here it is, grounded in what actually exists today (Origin Soul Song live, The Mirror structure live, Understandings for all 35 profiles, /render-verbatim, /api/compose with cost brakes, craft menu wired into generation, app build 26 on TestFlight with library ingest and Sophia chat).

Wave 1: the First Week journey, minimum shippable (this weekend)

Sequencing note: items 1 and 6 are the floor. If only two things ship before testers arrive, ship the Daily Pair and the feedback taps. The deep arc (2-4) can enter on day 2-3 of a tester's week; renders are per-person and can trail the journey by a day.

Wave 2: weeks 2-3 of beta

Wave 3: post-beta and roadmap

The Walking Incantation (S12) when movement-slot demand shows, Threshold Reading (S15) wired to the transit engine, The Twelve Rooms series (S16) as the months-2-3 spine, Dream Incubation (S10), The Belief Surgery deep session (S20, below), Wealth Codes Journey (S18) on explicit demand, Relationship Mirror (S19), TMR sleep layer (the true differentiator, needs research batch 3 from v1 section 7).

1. NEW FINDINGS 2026-07-11 (from the Wisdom Corpus briefing)

New structure ideas

S20. The Belief Surgery (deep session, week 2+, extends S1) The full three-teacher sequence the corpus now supports: a gentle affect-bridge descent (follow the feeling back toward where it was installed; corpus confidence 0.72, so gated to week 2+ and the Gentle-Arc exclusion applies) > memory reconsolidation pairing at the source (Ecker: reactivate, contradict with felt lived experience in the same moment, repeat 2-3 times) > identity seal (Ericksonian embedded install + become-not-get framing anchored to a chart signature). Slot: scheduled deep session, eyes closed, never a daily. Test: block intensity delta plus a qualitative "where did it take you" voice note. Guardrail: trauma-history testers get the Gentle Arc, never this.

S21. The Identity Gym (Maltz + McColl daily pairing, an upgrade path for S11) Morning: vivid first-person sensory rehearsal of ONE chart-derived scene (Maltz self-image rehearsal, 60-90 seconds inside the Morning Claim) that hands the listener ONE tiny chart-derived micro-action for the day (McColl: identity reorganizes through small consistent action, Fogg-tiny). Evening: the Night Install's opening line acknowledges the action ("and today, when you [action], you cast a vote"). The audio pair becomes a daily identity voting machine: rehearse, act, celebrate, install. Test: self-reported did-the-action rate vs plain Morning Claim arm.

New standing rules for structures

1. Deliberate induction selection. Hypnotic inductions are the single highest-confidence entry in the corpus (0.95: progressive, rapid, eye-fixation, Elman, fractionation). Every named structure declares WHICH induction it uses and why, instead of defaulting to progressive relaxation. Night structures descend, morning structures brighten, deep sessions may fractionate. This is a template field from now on.
2. The reconsolidation order is law for rewire audios. Reactivate gently, contradict in felt first person while the old feeling is still present, repeat the pairing. Contradiction WITHOUT reactivation is just a nice affirmation; the corpus is unambiguous on the sequence.

Corpus operations finding (important)

The nightly research cron ran on 7/11 and researched a 42-entry batch (the somatic, attachment, and IFS-deep lane: breath protocols, Yoga Nidra, Ideal Parent Figure, Hakomi, vagal toning, interoception vocabulary and more), pushed its enriched corpus.db at ~09:05 UTC, and then a manual corpus.db upload at 09:36 UTC overwrote it. The entries are not lost as ideas: all 42 items sit in the backlog as pending (56 pending total, 35 in the identity/transformation lane) and will re-mine at the nightly batch rate, or one manual cloud-side research_lane run catches them up in a night.

New rule: never manually upload corpus/corpus.db to R2 without first pulling the current one and checking its LastModified against the last cron run. The cron pushes after ~09:00 UTC; any manual upload that morning must merge, not replace.

2. THE HABIT ENGINE (the app UX layer)

Goal as Jeff stated it: addicting and habit-forming as a one-stop shop for installing identity and aligning to best potential. The corpus gives us the mechanics; the brand gives us the frame; the ethics rule is fixed: retention through real felt value, never through anxiety, guilt, or doom loops.

2.1 The Update Install frame (our native habit UI, nobody else can copy it)

The Subconscious Operating System is already the core frame. Make it literal in the app:

• Every person has a visible SOS version number ("Your Subconscious OS: v1.3").
• Every audio is a patch: before playing, the app shows two-line patch notes generated from the build report's named techniques, humanized ("This update installs: the already-claim for your Leo Sun. Rewrites: the guard around being seen.").
• Playing the audio is installing the update; completion shows "installed" with a soft confirmation.
• The First Week is the v1.0 to v2.0 upgrade, day 7 completes the version bump with a week-in-review "release notes for the new you" (which doubles as the feedback ask, framed as the council asking how the install went).
• An update left unplayed shows as "1 update pending", our Zeigarnik loop, native to the brand, zero dark-pattern guilt language.

This single frame converts listening into completing an install. It is the retention mechanic AND the brand story in one object.

2.2 The daily loop (certain container, variable reveal)

• Cue: habit stacking set at onboarding with one question each for morning and night ("What do you already do every morning without fail?"). The Night Install attaches to the existing bedtime anchor (Fogg 0.92). Until push exists, the daily email carries the cue.
• Ritual: same opening chime, same first breath, same closing coda every day (container certainty). The middle varies daily (reveal novelty): each Morning Claim carries a different chart-derived micro-reveal (Eyal variable-ratio 0.85, done ethically: the container is safe and certain, only the gift inside varies).
• Vote: the S21 micro-action turns each day into an identity vote (Clear 0.92). The streak is named in identity language: not "7-day streak" but "7 days living as her" (their chart language), with one streak-protect grace per week so a missed day never collapses the story.
• Celebration: completion micro-moment after each audio and after each 2-tap rating (Fogg: celebration is what wires the habit).
• Open loop to tomorrow: every audio ends with a one-line teaser; the app shows tomorrow's audio as a locked card with that teaser line as its title. Loops open across days, every loop closes within the week (locked sequencing rule).

2.3 The carry system (what makes it one shop, not a playlist)

• Anchor Word (S8) is the spine: installed once in week one, re-fired inside later audios, in the daily email subject line, and eventually as a push notification that is nothing but the word. The state becomes reachable from a single word, and only our app knows the word.
• The Understanding grows: journaling prompts and chatbot conversations append to context_store, and later audios visibly know it ("the thing you wrote on Tuesday"). Being remembered is the deepest retention mechanic we have, and it is already built.
• Sophia is the between-audios thread: parts-work check-ins, Socratic loosening, and the week-in-review conversation all corpus-grounded via the council. The chatbot's context write-back (distill conversation into learned_info) is the open build item that completes this loop.

2.4 Ethics line (locked)

Variable reward keeps the container certain and only varies the gift. Streaks celebrate and never shame; a lapse gets a warm re-entry audio, not a broken-flame graphic. No infinite feeds, no engagement bait, no fear framing. The product's addictiveness must come from accurate self-recognition (prediction-error encoding, 0.82: the true thing they never articulated) because that is the one lever competitors without chart data cannot pull.

3. THE ASSIMILATION ENGINE (how all knowledge compounds)

The fresh way to assimilate everything we have and everything still coming. One closed loop, most of it already built:

1. Mine (built): the nightly cron researches the backlog into confidence-scored craft entries (339 today, 56 pending including the re-mine of the lost 7/11 batch).
2. Offer (built): generation pulls a live offered-craft menu (n=12, map never full picture) so new craft reaches the writer within a day of being mined.
3. Name (built): every build report names which techniques were used and where.
4. Measure (Wave 1 build): the app's 2-tap rating and voice notes attach to the audio ID, which maps back through the build report to the specific craft entries used.
5. Update (small build, DATA): a feedback write-back script adjusts craft confidence scores and appends distinctions from tester language. Tester feedback literally re-weights what the engine reaches for next.
6. Synthesize (built): the morning Wisdom Corpus briefing chat is the human-facing layer: what grew, what it sparks, what to mine next. Jeff steers the backlog from that chat by naming teachers and topics.
7. Per person (built): the Understanding is the same loop at individual scale: computed once, appended forever, never recomputed.

What this replaces: reading research docs and hoping they influence scripts. The corpus IS the memory, the craft menu IS the recall, the build report IS the citation, and beta testers close the loop. The only missing links are steps 4 and 5, and both are small.

Next research batches (v1 section 7 priorities still stand, plus today): 1. let the 56 pending re-mine (somatic/attachment lane), 2. reconsolidation depth (Tori Olds, Unlocking the Emotional Brain casework), 3. sleep/TMR engineering (Paller, Rasch), 4. voice intimacy and parasocial audio (possibly the biggest retention lever, one entry today), 5. program design craft (Duolingo streak design, couch-to-5k psychology, retreat arcs) to sharpen Section 2 with evidence.

4. THE TESTING KIT (instruments, arms, and what answers what)

Instruments (build once, Wave 1)

• 2-tap per audio: landed / didn't. In app, immediately at audio end, with celebration.
• Block intensity 1-10: asked at intake (day 0) and at day 7, on the tester's own named block, in their words.
• Voice-note channel: reply-to on the daily email; transcribed into the corrections loop. Voice notes are gold.
• Behavioral (no asking needed): completion rate, replay count, share taps, streak length, time-of-day played, did-the-thing rate for S7/S21 (one-tap "did you do it?" card next morning).

The arms

• Journey level (week 2+): First Week default vs Gentle Arc vs Single-Thread Arc.
• Structure level: each structure's primary metric is in the Wave tables and v1's index.
• Craft level (one variable at a time, inside a locked structure): permission vs direct language; reactivation cycle 2 on/off; bed vs no bed on readings; anchor-word callback vs none; S21 micro-action vs plain Morning Claim.

The decision rule

A structure survives beta if its primary metric moves AND its 2-tap rate clears the fleet average. A craft variable adopts if it wins its A/B without hurting completion. Everything else returns to the idea bank with its data attached. Proof is in the pudding; we keep what works.

5. NOW / NEXT / LATER (the one-glance roadmap)

NOW (beta, weeks 1-3): Wave 1 six items, then Wave 2. The First Week journey for every founding tester. Feedback loop live. The Daily Pair is the product; everything else is the story around it.

NEXT (beta weeks 4-8): the 8-week dose is the real protocol; week one installs the habit, weeks 2-8 install the identity (our citable science line, and we tell testers honestly). Journey A/Bs, S20 Belief Surgery for consenting week-2+ testers, Threshold Readings on real transits, the assimilation write-back re-weighting craft from live feedback, craft confidence updated weekly.

LATER (post-beta): The Twelve Rooms as the membership series spine (readings never run out; transits, depth spirals, and combinations are infinite renewables). The sleep layer with TMR cues. The Relationship Mirror as the viral loop. The visual companion layer. Suggestibility-type calibration from chart signatures (Kappas types by element balance), the personalization axis nobody else can automate.

Housekeeping

• v1 stays as the palette and idea-bank reference; update the S-index there when a structure ships. This v2 is the action map; increment it when the sort materially changes.
• Affirmology_TechniquesLibrary_v1.md is engine-ingested (the corpus techniques tradition) and stays as is; new craft flows in through the corpus pipeline, not by editing that file. Its remaining to-dos (structure the research docs into the tradition, add Jeff's heart-coherence technique) still stand.
• The 7/11 corpus overwrite rule (Section 1) applies to every chat that touches R2.