Home / Ops / More in this area

Affirmology Lost-Chat Recovery - Name Flags + Wave 1 Email (and the 7/13-7/14 app build run)

Updated Jul 18, 2026 · Affirmology_LostChat_Recovery_NameFlagsWave1Email_v1.md

Affirmology Lost-Chat Recovery - Name Flags + Wave 1 Email (and the 7/13-7/14 app build run)

Recovered from the DATA/engine Cowork chat transcript 1c05f00c-29d8-4daf-949b-b25ef5afb7c7.jsonl (dated 2026-07-14, ~2018 messages), which vanished after a desktop app update. This is a self-contained catch-up so a fresh chat needs no prior history. Weighted to how the session actually ended.

1) CONTEXT

This was the DATA/engine chat (running as the "Fable" persona in the sync log). It opened at "ok what's up next?" and covered two threads that ran together:

• The named topic: the name_flag accuracy alignment and the deferred Wave 1 daily email, tracked in Affirmology_CoworkHandoff_NameFlags_Wave1Email_v1.md. This is the front half of the session.
• What the session actually spent most of its time on: a long TestFlight app-build run (builds 32 through 36) shipping the Wheel/Explore, the Sophia and Hermes/Thoth avatars, the Chiron / deep Understanding chart fix, and the entire T1-T14 app feature batch (credit ledger, birth-time write-back, terminology migration, real-time pace dial, Aries v2 rewards).

The three parties in play: DATA/engine (this chat), Cowork (the routing/front-of-house chat), and CODE (engine/render infra). Cross-chat handoffs move as copy-paste blocks Jeff relays by hand.

2) WHERE IT WAS LEFT

• Session ended right after build 36 was submitted to Apple and processing ("the brief-accurate version"; Jeff was told 35 and 36 may land together and 36 is the one to install). Jeff had said he needed to reboot soon. No open question was left hanging to DATA.
• name_flag alignment: DONE and DEPLOYED. Not open.
• Wave 1 daily email: DEFERRED by Jeff to Aug 13. Cowork was explicitly told to stop spending cycles on it. Not open.
• T1-T14 app batch: fully built, unit-tested, committed, studio deployed, and reconciled to Jeff's corrected GLOBAL CONFIG brief (which arrived truncated the first paste, complete the second). Everything logged to _CHAT_SYNC.md and Affirmology_PROJECT_STATE.md.

3) KEY DECISIONS (concrete)

Name flags (accuracy of the person's name in their audio)

• Accepted name_flag values on BOTH intake paths (/render-sacred-audio and /api/profile-capture), exactly: none | review | title | hold_vulgar | hold_impersonation.
• Mapping the form now posts: clean/OK name → none; ambiguous-but-real (e.g. Dick, Wang, Gay, Bush) → review; the "Use it anyway" button on a title/boast → title. BLOCK-tier names never submit, so no hold_* is sent client-side.
• Bug found and fixed: the form computed the verdict only to gate submit, then dropped it. It was wired into the /api/render payload in affirmology-site/index.html.
• Second, deeper bug found via Cowork's routing question: the demo Cloudflare Worker (affirmology-demo-site/worker) HAND-PICKED fields into the forwarded job, so name_called, name_birth, birth_time_known, and name_flag would have been silently dropped even with the form fix. Worker patched to forward all four verbatim. Deployed: worker version 38d762d2, site version 2a2bcfd0, both verified live on demo.affirmology.ai.
• Unknown birth time sends 12:00 as a computational stand-in with birth_time_known: false; the studio time-invariance gate handles that. Verified live.

Wave 1 daily email

• DEFERRED to Aug 13 (Jeff's call, 2026-07-12). No daily email work until then unless bandwidth frees earlier. Spec is preserved in the handoff doc for reactivation.
• When it activates: Wave 1 = library ingest plus the Daily Pair (one morning + one night audio per day). Sacred Register-1 names: First Light (morning) and The Night Tide (night). Cowork owns the email copy set (week one, per-day morning + night). Voice = sacred in the email even though the app UI uses the "software update / install" frame. Craft rules: definite, no wishy-washy, no em dashes, hope + power dominant, premium/on-brand.

Chart accuracy (came up mid-session)

• Sophia told Jeff he had "no Chiron," which meant the oracle was reading an OLD/shallow profile, not his deep Understanding. Fixed server-side so the oracle answers from the real chart and the deep Understanding; a deploy was polled until it served the deep_understanding field. This is live server-side, no app update needed to get the corrected answer.

App build run (builds 32-36)

• Build 32: Wheel with Tuner v3 FINAL alignment, 12 clean star-scrubbed figures hot-loaded from R2, all 5 name-pronunciation screens. Canon chant confirmed = take 4, byte-verified on R2.
• Constellation art cache bug: clean figures had been re-uploaded over the SAME R2 keys, so Cloudflare CDN kept serving stale cached bytes. Fixed by republishing all 12 under new v2_ keys and repointing alignment.json. Standing rule logged: never overwrite an art key on R2, always publish a new versioned key (same lesson as the corpus.db overwrite).
• Hermes/Thoth avatar (commit 1f78cbe): one being, two faces, changed under a puff of smoke (hidden, not a morph). Thoth is always full RIGHT profile, shoulders front, never front-faced. Wizard holds ~9s, poof once, Thoth holds ~7s, pre-reversed poof, repeat; muted; reduced-motion shows the still.
• Build 33: Sophia avatar activation animation + the Chiron/deep-Understanding fix surfaced.
• Build 34: full T1-T8 batch plus Sophia freeze fix, Hermes/Thoth shifter, wheel brightness base lift, native photo picker.
• Build 35: Part B / T9-T14 payload (credit ledger, pace dial, birth-time loop).
• Build 36: reconciliation to Jeff's complete GLOBAL CONFIG brief. Notable corrections:
• Config-first: all config values moved to app_config.py, env-overridable, exposed at /api/app/config; nothing hard-coded at point of use.
• Terminology: Blueprint = fixed cosmic base computed once. Context = umbrella only for everything beyond the Blueprint. Intention and Block are the two named home picks ("Toward:" / "Busting:"). "context" as a single-input name is retired.
• Intention/Block changes are free and unlimited; paid path is speed only ("APPLY NOW INSTEAD · 10 CREDITS", parked price); free path shows "updates on ".
• Pace dial = real-time playback time-stretch (player rate control, clamped 0.8-1.2, pitch unchanged, NO re-render). Family native paces: meditation/deep work 0.9, reading 1.0, motivation 1.1; the dial scales globally on top. The earlier render-side pace application was reverted so nothing double-applies.
• T9 credit ledger: three buckets per account (monthly resets on cycle with expiry flag; bought persistent, empty until SamCart; earned persistent). Spend order monthly then earned then bought. Regular tier pays 1.5x, premium/creator 1.0x. A Regular holding a reward-granted generation unlock consumes it instead of credits. Events balance_changed + monthly_expiring_soon. Clean unwired seam creditFromPurchase(bucket, amount, source) for the later SamCart/subscription webhooks. NO commerce built in this batch.
• T10 birth-time write-back: named directly-callable tool writeBirthTime(profileId, timeLocal, confidenceWindow, source); oracle marker path routes through it, writes rectified time to the canonical profile, then queues a fresh Origin generation.
• Aries v2: categories morning/action/reset/evening (legacy aliases keep already-published audios counting); rung one grants a spirit guide, never credits; guide changes gated on the first cleared challenge; grace is per rolling 7-day window; month close archives per-category totals into a lifetime record.
• Founding tier = 60 monthly credits, expires with the cycle (/api/app/credits). A context change after the first each month costs 1 credit.
• Explore/"The Sky": land on your Sun (Origin Soul Song + The Mirror inside it), swipe up to the ring of 12, swipe up again for stars + interface tray. Focused constellation named by what it REPRESENTS (Wealth) with the sign small (Taurus). Per-star listen counter (7 to fill; a star can hold multiple audios that all count). Manifest states: owned | available | testing | locked, plus per-constellation unlock (null | premium | prereq:aries).
• Wheel "feel" (rotation, swipe-down-to-Sun, bigger pre-rendered sky map) was logged as a design-first next iteration, NOT band-aided into the current v0/v1 wedge-list build.

4) OPEN / NEXT

• Three T-batch items were left intentionally switchable in config, not invented (Jeff must still decide): (a) the Aries day-counting rule, (b) the base art for the other constellations beyond Aries, (c) the reward-table contents.
• Confirm build 36 cleared Apple and install it (36, not 35). DATA said it would confirm when it clears.
• Wave 1 daily email copy stays parked until Aug 13 (Cowork owns it then).
• Nav icons: DATA was waiting on Jeff's examples to hand to Cowork.
• Wheel rotation/sky-map redesign is queued as design-first work (logged in _SHARED_CONTEXT and _CHAT_SYNC), not yet started.
• Nothing was left blocking on DATA at session end.

5) FILES & REFERENCES

• Affirmology_CoworkHandoff_NameFlags_Wave1Email_v1.md - the core handoff (name_flag values + deferred Wave 1 email spec + work split). In repo root.
• Affirmology_IntakeForm_and_Identity_Spec_v1.md - intake fields + identity system spec.
• Affirmology_NamePronunciation_Spec_v1.md - the pronunciation system.
• Affirmology_AudioPossibilities_Map_v2.md - Wave 1 owner split / Daily Pair.
• Affirmology_AppExperience_MasterPlan_v1.md - Monday v0 build table.
• affirmology-site/index.html - the intake form (name_flag posting wired here).
• affirmology-demo-site/worker - the demo Cloudflare Worker (patched to forward all 4 new fields; version 38d762d2).
• app_config.py - the new single config module (build 36); mirrored to the app via /api/app/config.
• _CHAT_SYNC.md and Affirmology_PROJECT_STATE.md - where every build and decision above was logged. Read the 2026-07-12 through 2026-07-14 blocks.
• Deployed versions to know: worker 38d762d2, site 2a2bcfd0. App builds 32-36 to TestFlight (36 is current). Endpoints touched: /api/render, /render-sacred-audio, /api/profile-capture, /api/name-review (+ /verdict), /api/app/config, /api/app/credits.

NOTE ON SECRETS: this session used the cloud Studio bearer token, the App Store Connect / Expo signing keys, and R2 credentials. Those exist and are already stored (see MEMORY: Expo token is permanent; agents bridge = affirmology-studio-api.onrender.com with Bearer CLOUD_STUDIO_AUTH_TOKEN). Do not print or paste secret values into any chat.