Home / Ops / More in this area

Affirmology Lost-Chat Recovery: Name Pronunciation, QC Audit, Identity Intake

Updated Jul 18, 2026 · Affirmology_LostChat_Recovery_NamePronunciationQC_v1.md

Summary. Recovered from a Cowork/DATA chat lost to a desktop update. Source transcript on disk: ~/.claude/projects/-Users-jeffreyparker-CLAUDE-AFFIRMOLOGY/66d1fae1-6d73-4e02-885a-123887e66f6e.jsonl (dated 7/12, ~2876 messages, opened "i'm back" during a Mercury-retrogr

Affirmology Lost-Chat Recovery: Name Pronunciation, QC Audit, Identity Intake

Recovered from a Cowork/DATA chat lost to a desktop update. Source transcript on disk: ~/.claude/projects/-Users-jeffreyparker-CLAUDE-AFFIRMOLOGY/66d1fae1-6d73-4e02-885a-123887e66f6e.jsonl (dated 7/12, ~2876 messages, opened "i'm back" during a Mercury-retrograde day of wifi/router drops). This file reconstructs it so a NEW chat can resume with zero context loss. Everything below was VERIFIED against the transcript and against files on disk.


1) CONTEXT

This was a long marathon DATA/backend session (the engine + affirmology-studio cloud side), running in parallel with a separate CODE/apps chat that was slowly rendering 33 "Mirror" readings all day (~25 min each). Jeff's laptop wifi kept dropping. Coordination between chats ran through _CHAT_SYNC.md. The session switched the model to Fable partway through (at Jeff's request, around the name-pronunciation build). It ended cleanly with Jeff saying "ok awesome. closeing this and restarting" and the assistant confirming everything was committed/deployed/documented and reboot-safe.

Four big threads ran in this chat, roughly in order: 1. Self-heal + demo-reserve spend cap (early). 2. The QC Audit and Plan (structural-drift quality control) - the "scared AF about quality" thread. 3. Naming session (audio/star names). 4. The 7/12 identity handoff: voice-note transcription, name pronunciation system, intake/identity fields, time-invariance filter, sung-name deduction, name review queue, and the chant runner. 5. Wheel art wiring + star-scrubbing the 12 zodiac figures (end).

All referenced docs exist on disk in the AFFIRMOLOGY root (verified): Affirmology_QC_Audit_and_Plan_v1.md, Affirmology_NamePronunciation_Spec_v1.md, Affirmology_IntakeForm_and_Identity_Spec_v1.md, Affirmology_AudioNaming_Registry_v1.md, Affirmology_AppExperience_MasterPlan_v1.md, Affirmology_FirstReading_Structure_v1.md. UI ref: CLAUDE OUTPUTS/Affirmology/Affirmology_NamePronunciation_UI_v1.html. Wheel art: CLAUDE OUTPUTS/Affirmology/WheelConcepts/.


2) WHERE IT WAS LEFT (end state at close)

The assistant's final message declared everything reboot-safe. Concrete standing state:

Nothing was left mid-edit or exposed. The only true OPEN decision at close was take-4-vs-take-2 for the chant (see Open/Next).


3) KEY DECISIONS (concrete)

QC Audit and Plan (Affirmology_QC_Audit_and_Plan_v1.md)

Self-heal + demo reserve

Identity handoff (5 items A-E) - all DEPLOYED live, verified against the running cloud

App pronunciation UX (front-end, built to match Affirmology_NamePronunciation_UI_v1.html)

All 5 surfaces committed (typecheck clean), entry = Explore -> Profile -> "Your name, said right.": 1. Chant confirm screen with a small "Not how I say it" link (proactive catch). 2. "Did we get it right?" [Yes, that's me] / [Not quite]. 3. Three fix paths, easiest first: (a) variant picker with real TTS previews, (b) say-it-yourself recording (the recording is KEPT), (c) respelling box with IPA behind an "advanced" toggle. NO bare IPA box anywhere. 4. Confirm + lock with a "hear it sung" preview (sung != spoken) and an OFFERED (never forced) Origin re-render. 5. Admin lexicon table (term / pronunciation / sung form / category, add + edit). Fire rules: confirming a pronunciation change AUTO-QUEUES the chant re-render; Origin remake is offered not forced.

Chant runner (POST /api/chant/run {person: <email>})

Naming session -> Affirmology_AudioNaming_Registry_v1.md

First-suite / app structure (from Jeff, line-level detail)

First constellation = at least 4 stars: Morning, Movement, Meditation (a category giving an EFT audio + a visualization + a new reading), Sleep. On entry the user is prompted for a weekly CONTEXT (selection box + optional type-or-voicenote) that shapes that week's audios and reading. Specialty pieces to start: a Chiron healing journey, a long hero's-journey audio. Other pieces greyed out / rolled out on discovery. The weekly-context prompt is the real engine unlock (chart + fresh current context, not chart-static) and slots into the Understanding's "context store."

Voice notes v1 (transcribe endpoint)

POST /api/app/transcribe (app auth pattern), multipart audio (m4a/caf/webm, cap ~3min/~10MB), transcribe via ElevenLabs Speech-to-Text (scribe_v1) using the existing key, return {"text":...}. TRANSCRIPT ONLY is a hard rule: raw audio never stored, temp file deleted in a finally block, log only person/duration/char-count. Backend was Jeff's/DATA lane; the composer mic button (RN, next to send) was the CODE/apps lane. Early mic-button attempts failed ("Transcription failed") until a NEW full-access ELEVENLABS_API_KEY was put in .env (does TTS + Music + STT), after which transcription worked. There is NO OpenAI key with credits (checked) - Scribe fallback to OpenAI Whisper is not available.

Olga birth-time rectification (recalled from Affirmology_Olga_Rectification_v1.md)

Resolved range ~9:20pm-9:55pm (Feb 25, 1966, Dubievka, Ukraine); working pin 9:35pm (21:35), the midpoint. Any time in that 35-min window gives the same chart. Q1 (Moon 8th->7th ~9:20, answer B = after 9:20) and Q2 (Mars+Mercury 6th->5th ~9:55, answer A = before 9:55) clamp the window; Q3 (MC Cancer->Leo ~10:30, answer A) confirms.

Wheel (end of session)

Wired SkyWheel to Affirmology_WheelAlignment_FINAL_v1.json (in WheelConcepts): render only included:true stars at normalized anchors with the 0..1 fill component; figure transforms (rotateDeg/flipX as negative scale/scale/dx/dy) in a 400x640 space scaled to the wedge; lines from linksEffective with brightness following fill; omitted stars stay in data (flip to enable later, no art/geometry change); figure opacity token = 1.0. Parity proven against the tuner's own render math (Product/WheelPreview/alignment_parity_check.png). Aries chain in day order: 41 Ari = First Light -> Hamal = The Forge -> Sheratan = The Stillness -> Mesarthim = The Night Tide. The painted figures existed ONLY on Higgsfield's ephemeral CDN and were RESCUED to R2 wheel/figures/. All 12 had baked-in tuning stars/numbers; removed via Higgsfield EDIT (not repaint, to preserve pixel-exact alignment); live on R2, originals in wheel/figures/original/, review sheet Product/WheelPreview/all_figures_clean_12up.png.


4) OPEN / NEXT (what a new chat should pick up)

  1. Chant take 4 vs take 2 (the one live open decision at close). Canonical = take 2, template unchanged, take 4 (build-and-converge) waiting on Jeff's ear. If take 4 wins: "make 4 canonical and update the template" -> also update the runner's prompt template so all future chants inherit the arc.
  2. Queue Sol's chant (POST /api/chant/run {person: solballard@gmail.com}) so both founders' chants can be reviewed before any member hears one. Not yet done at close.
  3. Flip the Mirror drift-gate from log-only to ENFORCE. Blueprint is approved; the one-fresh-founder-script proof (script only, no Fish) + a craft-judge sample check were the planned validation before enforce. Confirm markers strip clean (no leak into audio) first.
  4. Verify the 33 mirrors' LENGTHS before the Mirror emails go. Some early ones may predate the length-fix (25-29min overshoots); the last 3 are known-good (10-13min). CODE has the render manifest. Re-render only the long ones (pennies). This gates the Sunday-morning Mirror email send.
  5. Launch timeline (endorsed): Mirror emails Sunday ~10-11am (gift before ask), beta-join texts Sunday early afternoon, app teaser now framed "unlocks in a few days, likely Tuesday, sooner if ready," WhatsApp group Mon/Tue/Wed. Monday = buffer for live conversations + tightening (flip gate, hone beds, founder testing). NOTE: this timeline is from 7/12 and is almost certainly SUPERSEDED - the beta is now gated until launch (~7/26-8/1) and market launch is Aug 11 per memory. Treat these dates as historical.
  6. Site intake form deploy - backend is ready (item A won't drop a field); waiting on Cowork/CODE wrangler deploy.
  7. App build - pronunciation screens + wheel alignment are committed; ride the next TestFlight build on Jeff's "build it."
  8. Spec doc correction - fold the ~23h56m ascendant-return fix into the pronunciation/identity time-invariance spec.
  9. Beds - buy a small set of loopable/ambient beds by mood (gentle/calm/warm/charged) with first incoming money; these unlock the whole stretchable shelf cheaply. Jeff to hand a list of stretchable audios to wire.
  10. Optional: a to-the-minute pin inside Olga's 9:20-9:55 band via an oracle run through the agent (not required).

5) FILES and REFERENCES

Docs (AFFIRMOLOGY root, all verified present): - Affirmology_QC_Audit_and_Plan_v1.md - the audit + drift-gate plan + build status. - Affirmology_NamePronunciation_Spec_v1.md - pronunciation spec. - Affirmology_IntakeForm_and_Identity_Spec_v1.md - identity/intake spec. - Affirmology_AudioNaming_Registry_v1.md - locked names, two-register philosophy, unplaced palette, retired names. - Affirmology_AppExperience_MasterPlan_v1.md - Explore tab / Wheel master plan (build read sections 1,2,4,5,15.4,15.8b,16.8). - Affirmology_FirstReading_Structure_v1.md - the Mirror structure + 12 rules (source for the blueprint). - Affirmology_Olga_Rectification_v1.md - Olga birth-time range. - CLAUDE OUTPUTS/Affirmology/Affirmology_NamePronunciation_UI_v1.html - the pronunciation UI/UX reference the RN screens matched. - CLAUDE OUTPUTS/Affirmology/WheelConcepts/ - the 12 zodiac + Sun wheel art and Affirmology_WheelAlignment_FINAL_v1.json. - Coordination: _CHAT_SYNC.md (minute-to-minute), _SHARED_CONTEXT.md (durable shared brain). The naming registry + two-register system were posted to both, addressed to the Cowork app-experience chat to fold into the master plan.

Code (in affirmology-studio cloud repo unless noted; commits are from this 7/12 session): - api/identity.py - sung-name deduction (C) + name review queue (D). - pacing.py - word_band single source of truth for bed-aware length; existing pacing_gate/negation_gate. - structures.py (~lines 62-63) - free-text directive/overview (the drift risk the blueprint replaces). - compose() - gate-and-revise loop (Apollo/Orpheus); conformance gate slots in via additive structure_id. - The conformance engine module + Mirror/Origin blueprints + pytest (16/16), commit fd46119. - Self-heal orchestrator + SELF_HEAL_MAX_SPEND_USD cap, commit c98818f. - Existing gates in src/affirmology/: audio_qc.py, chart_guard.py, script_qc.py; orphaned verify_send.py. - App (affirmology-app / Maya): pronunciation screens + SkyWheel, commit 5f762fc and earlier. - Cloud deploy commit b99efbd (later health=ok).

Endpoints: - POST /api/app/transcribe (voice notes, transcript-only). - POST /api/chant/run {person:<email>}; chant queue is self-draining cloud-side. - /api/name-review/verdict and related (review queue). - Studio base (headless): https://affirmology-studio-api.onrender.com, Bearer STUDIO_AUTH_TOKEN / CLOUD_STUDIO_AUTH_TOKEN. Hermes: POST /api/hermes. Health: GET /api/health.

Secrets / keys - THEY EXIST, values NOT printed here: - A NEW full-access ELEVENLABS_API_KEY in affirmology-studio/.env (does TTS + Music/chant + Speech-to-Text). Old key is superseded. - STUDIO_AUTH_TOKEN / CLOUD_STUDIO_AUTH_TOKEN, EXPO_TOKEN (permanently stored per memory), Resend key. - No OpenAI key with credits exists (checked in-session). - Anthropic has no live balance API; billing/top-up: https://console.anthropic.com/settings/billing

Media URLs (public): canonical chant https://media.affirmology.ai/chants/<person>.mp3; takes at .../chants/<person>/takeN.mp3.


NOTE ON CONTEXT NOT VISIBLE HERE

This recovery is built ONLY from this one DATA/backend transcript. It cannot see the PARALLEL CODE/apps chat that rendered the 33 mirrors and built the RN app screens, nor the Cowork app-experience chat that owns the master plan and email/text copy - their side of these handoffs lived in _CHAT_SYNC.md and _SHARED_CONTEXT.md, which a new chat MUST read for the current cross-chat truth. It also predates later sessions: the 7/12 launch timeline here is superseded by the current gated-beta / Aug 11 market-launch plan in memory, and any commits marked "push held" or "awaiting build" may have shipped afterward. Verify live state via GET /api/health, the current _CHAT_SYNC.md date block, and Affirmology_PROJECT_STATE.md before acting on anything dated.