Home / Ops / More in this area
Updated Jul 12, 2026 · Affirmology_CoworkHandoff_NameFlags_Wave1Email_v1.md
CONTEXT: The entire identity backend from the 2026-07-12 handoff is BUILT AND LIVE on the cloud
studio (items A-E: identity fields persisted, time-invariance filter, sung-name deduction, name
review queue, pronunciation system, plus the self-draining chant runner). The new intake form
Cowork built in affirmology-site/index.html is ready to deploy (backend accepts all new fields).
Two things remain on Cowork's side before the form ships and Wave 1 starts.
REFERENCES: _CHAT_SYNC.md blocks dated 2026-07-12 (identity backend B+C+D, chant runner,
COWORK/DATA front-end block) · Affirmology_IntakeForm_and_Identity_Spec_v1.md ·
Affirmology_NamePronunciation_Spec_v1.md · Affirmology_AudioPossibilities_Map_v2.md (Wave 1
owner split) · Affirmology_AppExperience_MasterPlan_v1.md (Monday v0 build table).
The backend now accepts name_flag on BOTH intake paths (/render-sacred-audio +
/api/profile-capture). Accepted values, exactly:
none | review | title | hold_vulgar | hold_impersonation
Your 3-tier classifier already produces flags (review, title). Please confirm the form posts
exactly the values above (an OK name posts none, an ambiguous-but-real name posts review, the
"Use it anyway" button posts title). BLOCK-tier names never submit, so no hold_* mapping is
needed client-side unless you decide a blocked category should submit held instead. If your labels
differ, reply with the exact strings and DATA will map them server-side.
Jeff's call: there will be NO daily email until Aug 13 unless bandwidth frees up earlier. Do not spend cycles on email copy now. The spec below stays for when it activates.
Wave 1 delivery = library ingest + a daily email per the Daily Pair (morning + night audios, sacred register-1 names: First Light / The Night Tide). Cowork owns the daily email copy. Needed: the copy set for week one (per-day morning + night sends), on-brand, premium, matching the Update Install frame in the app UI layer but SACRED naming in the email voice. Reading craft rules apply (no wishy-washy, no em dashes, hope + power dominant).
GET /api/name-review, POST /api/name-review/verdict), pronunciation system end to end,
chant runner (take 4 = Jeff's canon chant, verified), app screens (riding the TestFlight build
going out tonight), backend persistence for every new form field.index.html,
(2) the Wave 1 daily email copy set.npx wrangler deploy) the moment Request 1 is confirmed.