Run on Claude, weekly.

Create four visible outcomes from Anand's session(s):

1. Insight (big, useful, surprising) the audience remembers
2. Real-world attempts they can try
3. Evidence-rich replies Anand gets
4. Reusable connections or assets for Anand

Analyze and create two outputs:

1. A helpful and useful attendee message.
2. A private aftercare record where the compounding happens. (Never mix the two.)

The aim is a learning-transfer loop, not just a message: session -> they remember -> try it -> report -> I learn -> next session (for them or others).

Use these skills where available to do the thinking:

- talks-workshops: learning transfer: surprise, practice, recall LATER, apply ELSEWHERE, explain WHY, know when WRONG.
- anand-writing-style: voice.
- blind-spot: for the aftercare record (unclosed loops, adoption friction, escaped assets).
- anand-objectives: what's worth preserving and pursuing.
- verification-gate: names, claims, links, before finalizing.
- evidence-provenance: only when the message asserts external facts or updated AI claims (mainly month/quarter touches).

Steps:

1. **Mine the transcript(s).** Extract: the BIG idea, the USEFUL habit, the SURPRISING insight (max 3 total - use just these - never summarize everything); each attendee's stated commitments and questions; anything Anand promised. Speaker names may be wrong - verify against the people list or calendar (gws), or drop the name. Never misname. For a series, synthesize progression and open items across sessions.

2. **Classify the audience** - it sets tone and asks:
   - Client team: business-outcome framing; confirm with the account owner before sending.
   - Community / alumni / students: curiosity, shareability, next-session invite; often the host should send.
   - Internal: tie to live projects; ask for demos back.
   - Government / institutional: formal register, public value, longer horizon.

3. **Decide when & whether to send.** Default cadence: day 1, day 10-14, quarter.
   Add a 1-month touch only for cohorts with a real project or commitment.
   Recurring series (weekly/monthly): per-session, only a short retrieval nudge + next-session teaser. Run month/quarter touches once per series.
   If the timing adds no distinct value, output SKIP with one line of reasoning.
   Before month/quarter touches, check recent transcripts and calendar for contact with the same people; if the relationship is already active, SKIP or fold into the live thread.

4. **Draft the touch.** Each has ONE job:
   - **Day 1 - make it stick.** The takeaways, one line each; each attendee's own next step ("You said you'd..."); secure one implementation intention: "When X happens, I'll do Y."
   - **Day 10-14 - retrieval before reminder.** Ask them to recall first; then one <=10-minute practice on their real work. Ask what worked and what broke.
   - **Month 1 - diagnose transfer.** What transferred, failed, or got blocked; suggest one next experiment; share (anonymized) wins from replies - social proof that closes the loop.
   - **Quarter - reopen the relationship.** What changed since - new capabilities, and what Anand got wrong or updated (this earns trust). Ask what they're working on; anchor on one useful problem or collaboration, not a pitch.

5. **Message contract.**
   - 120-220 words, plain text. Subject names a concrete moment ("That hallucination trick from Saturday").
   - Exactly one tiny action and one low-friction reply ask, like: "I tried .... and it [failed / worked / I got stuck / ...]". Explicitly welcome failures, disagreements, and corrections.
   - Where natural, invite an anonymizable prompt, example, dataset, or case that could help the cohort.
   - Never invent quotes, reactions, or results. No resource dumps. Don't repeat earlier touches (check the aftercare record).
   - Alternate containers when they fit better: WhatsApp/Teams nudge (2-3 sentences) if the group lives there; one session page (/data-story comic or HTML) linked from day 1; a 3-question quiz as the day-14 retrieval.

6. **Write the private aftercare record** Anand can append to `~/Dropbox/notes/followup-<session>.md` dataset:
   - Send plan: dates, channel, recipients, owner (Anand or host).
   - Per-person: commitments, questions, relationship notes. Also mention updating `~/Dropbox/notes/about/*.md` for people worth tracking.
   - Candidate assets: prompts, examples, benchmarks, blog/TIL seeds; corrections to the workshop itself.
   - When replies arrive, append a table: Person | Attempt | Result | Blocker | What this corrects or teaches | Asset offered | Next follow-up. Then the top 3 workshop insights and people to reconnect with.
   - Track: reply rate per touch. Under ~10%? Sharpen the ask, not the summary.

Output: the message(s) (subject + body, personalized where the transcript supports it) or SKIP, plus the aftercare record. Create Gmail drafts via gws only if asked.