Home / Ops / More in this area
Updated Jun 26, 2026 · Affirmology_TechniqueToolkit_and_Ideas_Registry_v1.md
The single place we track: (1) the pipeline that turns Wisdom Corpus research into approved, rotating audio techniques, (2) techniques and their approval status, and (3) product ideas that are not yet built (audios, readings, interactive). This is the "list somewhere" Jeff keeps asking for. Updated 2026-06-26.
The problem: the corpus is growing fast (252 craft techniques and climbing). We need a way to surface "things we could try in an audio," test them, approve the good ones, and then ROTATE them across audios so a person is not hit with the same technique every single time.
The pipeline, five stages, each a status on a technique:
MINED. The nightly research cron extracts a technique into the corpus craft table (this already happens). Status: mined. The craft table already has the fields we need: method, why, when_to_use, how_to_apply, one_liner, scope, form, rule, confidence.
CANDIDATE. A surfacing pass (a new nightly or on-demand job) reads the corpus and writes a "Technique Candidate" list: each entry is a technique phrased as a concrete audio move, with a proposed slot (open / body / close / whole-arc), the structures it could fit, and its confidence. This is the "big-ass list" Jeff wants. It lives as a table the Council and the Studio can both read.
COUNCIL-PROPOSED. The agent Council reads the candidate list and assembles "listening ideas": small recipes that combine techniques into a testable audio (for example Permission + reconsolidation pairing + nightly incantation = Reconsolidation Breakthrough). Status: proposed. The Council is the creative director here, not the chat.
STUDIO-TESTED. A Studio creator (Jeff, Sol, Colin) renders a proposed recipe against real charts, listens, and rates it. Status moves to tested with notes. Failures go back to candidate with a reason.
APPROVED TOOLKIT. Techniques that pass become part of the approved toolkit, tagged with which slots and structures they are cleared for. Status: approved. From here a technique can either (a) become its own named structure, or (b) live in the toolkit as a rotatable slot ingredient.
ROTATION (the part Jeff specifically wants): once a technique is approved and slot-tagged, the generator picks from the pool of approved techniques for a given slot rather than always using the same one. Over weeks and months of nightly listening, a person's audios draw different approved techniques for the same slot (different somatic anchor, different breath induction, different reframe move), so the library stays fresh and non-repetitive while every technique is still vetted. Rotation can be weighted by confidence, by what the person responded to, and by recency (avoid repeating last night's pick).
KNOWING THE TOOLS AND SPRINKLING THEM (Jeff, 2026-06-26): the approved toolkit IS the answer to "how do we know what tools we have for transformation or identity and sprinkle different ones throughout." Once a technique is approved, it is tagged with its TYPE (identity or transformation), its SLOT (open / body / close / whole-arc), and the structures it is cleared for. That gives us a browsable, filterable list of vetted tools (e.g. all approved identity-open techniques, all approved transformation-body techniques). The generator sprinkles from that pool per audio; a human can browse the same list in the corpus-browser tab on resources.affirmology.ai (Part 2). "Self-as-Context Release" is the first example of a tool that lives in this toolkit as a transformation component rather than its own audio.
What to build, in order:
- A technique_status field (or a small technique_pipeline table keyed to craft id) holding the stage, slot tags, structure tags, and test notes. Cloud-side, alongside the corpus.
- The Candidate surfacing job (stage 2): a script that reads craft and emits the candidate list. Can be a nightly cron sibling to the research cron.
- A Council "assemble listening ideas" task (stage 3) that reads candidates and proposes recipes.
- A Studio surface to review candidates/recipes, render, rate, and approve (stages 4 and 5). This is the real new UI work.
- Generator rotation (the payoff): the slot-fill step picks from approved pools.
This is a real build. Recommend we scope stages 2 and 3 first (they are mostly corpus + Council work and give immediate value: a reviewable idea list), then the Studio review UI, then rotation last.
Decision (Jeff, 2026-06-26): the searchable Wisdom Corpus lives as a TAB on the existing internal hub at resources.affirmology.ai, not a separate site.
Context: resources.affirmology.ai is the Resource Hub (resource-hub/), a Cloudflare Pages site, gated by Cloudflare Access to jeff + Sol + Colin, generated by a Python generator from project docs and redeployed by a launchd cron every ~2 hours. Taxonomy is data-driven via resource-hub/clusters.json. It already does exactly the thing Jeff loves: clustered, searchable, clickable, with overviews.
The new tab: "Wisdom Corpus" (or "Research Library"). It renders the corpus the same way the hub renders docs:
- Browse the craft techniques by area (practitioners, reading_craft, breakthrough, meditation_hypnosis, neuroscience, audio_production, frequency_sound) and by tag, each as a clean card showing one_liner, method, why, how_to_apply, confidence, source.
- A client-side search across all craft (same search UX as the doc hub).
- A "Recently synthesized" / "Trending" section fed by the nightly growth reports and the morning briefings, so the latest mined ideas surface with links.
- Cross-links: a technique card links to the structures and candidate recipes that use it (ties this tab to Part 1).
How it fits the existing build: the corpus is cloud-only (R2), never stored on the Mac. Two clean options, recommend A:
- A (recommended): the hub's generator cron also pulls the corpus from R2 at build time, renders static corpus pages into the same dist/, and deploys them as the new tab. Fully static, no live DB, matches the current architecture, no new runtime. Refreshes every cron cycle.
- B: a small live API the tab queries (more work, live freshness, more moving parts). Only if we want real-time.
This is a resource-hub/ extension, decoupled from the studio. Needs its own build brief and Claude Code handoff when we are ready (similar to Affirmology_ResourceHub_BuildBrief_v1.md). Not started yet; logged here as the agreed direction.
Grounded in corpus: Sleep-Consolidation Dosing ("one listen is a thought; nightly for three weeks is a prior shift") and Repetition and the Dose ("eight weeks of daily listening consolidates belief change into identity"). See the elaboration in the chat. The product expression:
DECIDED (Jeff, 2026-06-26): the MONTHLY BAKED AUDIO model. You get ONE new sleep audio per month ("baked in" limit on the base tier). Before it bakes, the person selects a few inputs to shape it; then it is generated once, QC'd, and LOCKED for the cycle. They listen to that same baked audio nightly for the month. At the next new moon the slot reopens for a new bake.
Why it fits: one focus repeated nightly for a full month is exactly the consolidation window the corpus calls for (no novelty-seeking). Technique ROTATION moves month-to-month (each new monthly bake can draw different approved techniques) instead of night-to-night, which simplifies the pipeline. The "baked then locked" scarcity is a feature: it makes the monthly audio feel like an event, controls cost, and keeps people doing the nightly work instead of endlessly regenerating.
What every monthly bake draws on (three layers): (1) IDENTITY, always, but as GROUNDING, not a permanent base layer running throughout (Jeff, 2026-06-26: do not frame it as a constant underlying track). It grounds the audio and especially the opening via the Tier 1 recognition stack, then the audio moves into the month's focus; (2) the LUNAR MOMENT of that month (new moon / full moon themes and the month's transits), a light touch that gives each month a real, on-brand theme instead of an arbitrary one; (3) the person's chosen FOCUS, what they are working on.
Shaping inputs the person selects (kept minimal, Jeff 2026-06-26): at LAUNCH the only real shaping input is the ONE belief they are working on (the private working_through field, which holds exactly one belief at a time, replaceable, not a list). Some audios are shaped from it; the monthly bake may also lean on whatever is happening in the moon that month. Voice / tone selection is a FUTURE input (male/female voice and a few others), NOT at launch, because we do not yet have multiple voices. Identity grounding and lunar/transit theming stay automatic.
Lunar cadence (design choice): bake at the NEW MOON (intention-setting, the natural "begin a focus" beat), theme the audio to that lunation and the month's transits; the FULL MOON can be an optional mid-cycle touch (culmination / release). This also ties into the Hero's Transit "unlock" mechanic for bigger sky events.
NOTE: this supersedes the earlier "1 primary + optional add-on / identity built-in vs light tracking" framing, which was overcomplicated. The monthly-baked model already settles nightly delivery as one audio per night; daytime extras (morning activation, the delta drift-off variant) are separate optional pieces, not part of this core loop.
Baking mechanics: generate once through the engine, run audio_qc, store, lock for the cycle; slot reopens at the next new moon.
Delta / drift-off variant: NOT baked for everyone, and deprioritized. If we ever offer it, it is an opt-in extra, not a second nightly bake.
Identity placement under this model: the monthly baked audio is the ACTIVE nightly install; the Origin Soul Song stays the always-available FOUNDATIONAL identity piece; and the Tier 1 recognition stack still lives in the OPENING of every monthly bake, so identity is reinforced regardless of the month's focus. Identity = permanent base layer; monthly bake = active layer.
Tiering (DECIDED, Jeff 2026-06-26): NO extra nighttime bakes for anyone, including premium. Everyone gets the ONE monthly nighttime bake. Premium unlocks OTHER content, not more nighttime audios: additional constellations, journeys (e.g. Hero's Transit), and the depth pieces (Your Wound Is Your Gift, Possible Selves). The nighttime monthly audio is the universal base everyone gets.
Onboarding (DECIDED, Jeff): a brand-new user's FIRST WEEK of nightly sleep audio is identity-only (Origin Soul Song / The Recognition nightly) to land the "this gets me" hit. Only after that first week do they get the monthly shaping selection and their first monthly transformation bake.
What the corpus and sleep science say, and the resulting decision:
| Technique | Corpus area | Status | Where it lives / next step |
|---|---|---|---|
| Permission Narrative | breakthrough | APPROVED, in use | Opening act of Reconsolidation Breakthrough. Also a candidate for its own lighter standalone structure ("Permission") if Jeff wants it split out. Tracked per Jeff's request. |
| Memory reconsolidation pairing | breakthrough | APPROVED, in use | Middle of Reconsolidation Breakthrough and Three-Act Arc. |
| Three-Act Arc (Naming/Embodying/Becoming) | reading_craft | SPEC WRITTEN, build for testing | Affirmology_ThreeActArc_StudioSpec_v1.md |
| Reconsolidation Breakthrough (recipe) | breakthrough | SPEC WRITTEN, build now for testing | Affirmology_ReconsolidationBreakthrough_StudioSpec_v1.md |
| Tier 1 identity stack (self-relevance, recognition, I-am, mirroring, prediction-error) | neuroscience/reading_craft | APPROVED, in use | Core of every audio. See Affirmology_IdentityResearch_v1.md. |
| Emotional incantation close (nightly) | breakthrough | APPROVED | Close slot of transformation audios. |
| Prosodic safety / theta-slow delivery | neuroscience/frequency_sound | APPROVED (partly in C26) | Delivery rule, confirm fully wired into pacing. |
The idea: cast the person's current major transit as a 12-stage hero's journey (Vogler), positioning them as protagonist. Corpus: "Hero's Journey Script for Chart Transits" and "Saturn Return as Initiation Gate."
Jeff's questions, answered: - When is it useful, and how would I know if it is useful for me right now? It is useful whenever a person is inside a major slow-transit window, which is more often than people realize. The big ones: Saturn Return (~29, ~58, ~87), Saturn square/opposition to itself (the ~7-year checkpoints at roughly 7, 14, 21, 36, 44, 51), Pluto squares/oppositions (long, life-restructuring), Uranus opposition (the "midlife" awakening ~38 to 42), Chiron Return (~50), and major outer-planet transits to personal planets or angles. The engine already computes transits, so the right design is: the system detects whether the person is currently in (or near the edge of) a qualifying transit and only offers this audio when they are, with a one-line "why now" ("you are in your Saturn Return, the threshold this audio is built for"). That answers "how would I know" automatically: we tell them, because their chart told us. - Recent vs upcoming transit (the "could be 3 years" problem)? Three modes, and the system picks based on timing: (a) IN IT now -> cast the live transit (most powerful). (b) JUST FINISHED (within ~12 months) -> cast it as the integration/return leg of the journey (stages 10 to 12), the "here is what you just walked through and who you became." (c) APPROACHING (within ~12 months) -> cast it as the call to adventure (stages 1 to 5), preparation. If the nearest major transit is years away, do NOT offer this audio; offer a different structure instead. So it is never "cast a transit 3 years out as if it is now," it adapts the framing to where they actually are. - Status: LOVED, design-approved direction above. Build after the transformation structures are tested. Needs a "transit eligibility" detector spec.
THE "UNLOCK" MECHANIC (Jeff, 2026-06-26): Hero's Transit is not always-available. It is a bonus that LIGHTS UP and unlocks for you when the engine detects you have entered an eligible transit window. The experience: the audio sits dormant/locked, then the system notices you have crossed into (or are approaching, or just finished) a qualifying transit and surfaces it as a delight + re-engagement moment, e.g. a notification "Your Saturn Return just opened. A journey has unlocked for you." This turns the chart's own timing into a personalized unlock, which is both a retention hook and a proof-of-personalization moment (the app knew before you did). Applies the same three-mode framing (in-it / just-finished / approaching) to decide which journey unlocks. Design as: locked-state card in the library + an unlock event + a notification. This unlock pattern is reusable for OTHER time-gated content later (lunar returns, numerology pinnacle shifts, etc.).
Markus possible-selves (corpus 0.92) plus Benjamin Hardy future-self. A guided exercise (desired self, feared self, role-model self in first-person present) that maps onto the person's North Node and future-promise placements, rendered into a "future self" audio and/or an interactive reading. Jeff: premium tier. Status: LOGGED, premium, not scheduled. Good candidate for the interactive (not just audio) format.
Jeff's idea: take the highlight lines that hit most hypnotic and turn them into actual songs. Connects to the Sonic Anchor motif (idea 4 below). A song version of a person's core identity lines could be a high-retention, shareable artifact. Status: LOGGED, experimental. Note: per the hard rule, any audio still goes through our system; a "song" path would need to be designed within that constraint (our pipeline producing the musical render, not an outside generator).
Targeted Memory Reactivation Motif: a unique 2 to 3 second sonic signature placed on the core affirmation, later re-cued at very low volume during slow-wave sleep via a wearable. The v2 differentiation / moat idea. Jeff wants to experiment more. Status: LOGGED, experimental, mine TMR/sleep-learning research harder before any public claim. Connects to the songs idea (the motif could be the hook of the song).
Not everything is an audio. Track three formats: AUDIO (install/transformation), READING (teaching/recognition, the Mirror lane), INTERACTIVE (questionnaires, possible-selves exercises, the beliefs intake, transit "why now" prompts). Possible Selves and the beliefs intake are the first interactive pieces.
Affirmology_TheRecognition_StudioSpec_v1.md.