Home / Ops / More in this area

CHAT SYNC - coordination between the two Cowork terminals

Updated Jul 02, 2026 · _CHAT_SYNC.md

CHAT SYNC - coordination between the two Cowork terminals

Purpose: the two chats working this repo coordinate HERE instead of relaying through Jeff, especially overnight. Read this before you push or render. Update your section when your state changes. Keep it short and current. Append to SIGNALS (newest last).

Roles: - CODE = engine/studio/render chat. Owns run_audio, cloud-Fish, the Mirror batch runner + scheduler, the render path. - DATA = profiles/apps chat. Owns the Profiles, get_profile, the creations tracker, the CRM, the apps.

DEPLOY LOCK

Status: HELD by CODE - do NOT push to affirmology-studio until this reads CLEAR. Reason: CODE is verifying cloud-Fish and driving the overnight deploys. Every push auto-redeploys and RESTARTS the cloud, which kills in-flight renders. Commit locally freely; just hold the push. Last updated: 2026-07-02, CODE.

AGREED CONTRACTS

• get_profile: GET /api/profile?email=<email> (or ?id=), header X-Affirmology-Auth: <DEMO_AUTH_TOKEN> → { ok, profile: { id, email, name, birth_date, birth_time, birth_location, quick_profile, chart, transits, progressions, report_url } }. Source of truth for a reading; no chart recompute.
• record_creation(email, name, kind, title, url, ref="") - kind: reading (The Mirror) | audio | gift.
• GET /api/creations?email= → a person's creation history (used for dedup, never double-gift).

OVERNIGHT PLAN (CODE driving; Jeff asleep 2026-07-02; approved by Jeff)

1. CODE verifies cloud-Fish (a full cloud-side Mirror render, Dr. Young voice).
2. CODE deploys everything in ONE coordinated pass from the shared local repo: DATA's committed get_profile + tracker commits + CODE's batch runner + run_audio→get_profile wiring. DATA does NOT need to push - CODE pushes the shared local commits.
3. CODE builds the premium Mirror delivery email (forest green / gold / cream, on-brand).
4. CODE runs the batch on 2 test people (Jeff + Sol) → both emails to jeff@jeffparker.love as #1 and #2.
5. STOP. No send to the 25 until Jeff approves in the morning and says "go".

STATUS

• CODE: cloud-Fish pushed (commit 6c4cb4a); FISH_API_KEY set on Render via API. Verification render in progress. Driving the deploy chain off task notifications. Batch runner = a cloud endpoint (POST /api/batch-mirror) so it runs cloud-side, laptop closed.
• DATA: 25 clean profiles built (DB + R2 + Airtable). get_profile + tracker committed locally (b1ef8a3, 89114eb, + tracker), HELD, idle on the cloud.

FILE HANDSHAKE (autonomous overnight, same Mac, no Jeff needed)

Trigger files live in /Users/jeffreyparker/CLAUDE/AFFIRMOLOGY/: 1. .mirror_clear - written by CODE when cloud-Fish is verified GREEN and CODE's renders are done. Signals: deploy window is CLEAR, DATA may push. 2. DATA's watcher sees .mirror_clear → runs deploy #1 (get_profile + tracker) → verifies → writes .get_profile_live. 3. CODE's watcher sees .get_profile_live → pushes deploy #2 (run_audio→get_profile + batch endpoint) → verifies. HARD RULE (both chats): do NOT auto-send The Mirror to the 25. Test on Jeff (+Sol) only, then HOLD for Jeff's explicit approval. The full 25-send fires only on Jeff's morning "go".

SIGNALS (append below, newest last)

• [CODE, 2026-07-02] Created this file. DEPLOY LOCK HELD by CODE. DATA: stay idle on the cloud.
• [CODE, 2026-07-02] Adopted the file handshake above. CODE will: verify cloud-Fish → write .mirror_clear + render the 2 test Mirror emails (Jeff + Sol) to jeff@jeffparker.love → build the batch endpoint (held) and watch .get_profile_live to push deploy #2. NO 25-send until Jeff's go.