View
Switch to “New” to see where the first-time-fix rule and the silent-drop watcher land.
● First-time fix
Serious mistakes (wrong fact, wrong executor, brand or privacy slip, anything client-facing that’s incorrect) get turned into a standing rule the first time, not the second. Applies to the four phases that send something to the outside world.
● Watcher needed
A check that runs on its own and pings Anne the moment a step quietly drops. Mapped onto the three known silent-drop spots — Phase 2 confirmation DMs, Phase 9 fleet-dependent emails, Phase 8 and 10 social distribution (the April 4 hole).
🆕 NEW!!! Content Longevity & Legacy Section — scroll to Phase 10
She Leads AI

Social Saturday Process and KPIs

Full workflow from speaker booking through post-event follow-up and content longevity. 6 Rube recipes active, 3 skill folders updated, every phase addressed. Roles refreshed May 27, 2026 for the relaunch — Jen and Beth host, Kate books and runs events, Don on systems and post-production, Anne stays the approver.

CURRENT STATE May 27, 2026
Upcoming sessions
  • May 16 — Niki Weiss
  • May 23 — Canceled for Memorial Day weekend
  • May 30 — “Before You Ship” panel pending confirmations from Mary Carol Mazza (anchor), Alenka Znidarsic, Golddy Kaur, and Tosin Oguzie
  • Jun 6 — AI Governance CoP
  • Jun 13 — Layla Townsend + Michelle Muncy-Silva co-present (pending their confirmation)
Hosting
  • Jen Schwartz and Beth Lyons host the Social Saturday relaunch
  • The earlier three-facilitator rotation is retired
  • SOW still pending from Jen and Beth, which gates the sub-brand lock
  • Jasmine has moved to Community Manager — off cohosting, promotes events in Mighty Networks
Sub-brand status
  • Pop-Art Commit is the leading direction but not yet locked
  • Bucket A color rule confirmed (exact SLAI hex codes, never shifted hue)
  • Anne is iterating in Claude Design from ss-claude-design-briefing.md
  • Final lock blocked on Beth and Jen SOW
Sticking points still open
  • Speaker calendar event — create and verify receipt (Phase 1 and 2)
  • Speaker sign-up — rebuild as form-first, date-offered (Phase 1)
  • Companion guide — move Zoom link to the top (Phase 6)
  • SS attendance and conversion analysis is overdue from May 9
  • Stanley to pick up SS KPIs as the first BI pass
The Social Saturday Speakers Google Sheet is the only data source this entire system requires.
Every phase — booking, prep, promo, coordination, follow-up — draws from the Social Saturday Speakers Google Sheet. If the information isn’t in the Social Saturday Speakers Google Sheet, the pipeline cannot function. Everything comes back to the Social Saturday Speakers Google Sheet.
64
Total Steps
41
Automated
17
Human Action
6
Data Movement
3
Skill Folders
10
Phases Mapped
Progress Scorecard
Last updated May 17, 2026

54 problem points identified across the Social Saturday pipeline. 42 solved. May 17 status — host handoff to Beth and Jen is active, sub-brand is WIP (Pop-Art Commit direction, blocked on SOW), May 23 canceled, May 30 panel pending confirmations. Recipes simplified, Mighty Networks confirmed manual, brand enforcement gaps flagged, cohost guide links need audit, CRM connection parked. Agent reliability remains the one structural barrier.

Overall resolution progress 78%
42 Solved 6 Minor Blockers 5 Queued 1 Remaining
54
Problems Identified
42
Solved
6
Minor Blockers
5
Queued
1
Barrier Remaining
The one real barrier — agent reliability. The pipeline is built and the agents are running, but they still need supervision. Not fully autonomous yet. About 70% of the way there. The goal is a system that runs without Anne having to watch over it.
SS Pipeline Build — Complete
April 2026

The full Social Saturday pipeline was mapped, built, and automated. 6 Rube recipes active (2 pending auth), 3 skill folders built and updated, a Notion Sessions DB created, and the Social Saturday Speakers Google Sheet as the single source of truth for the entire system.

42
Problems Solved
6
Rube Recipes Active
3
Skill Folders Updated
10
Phases Mapped
6 Rube recipes active. Day-of Delivery Doc (Fridays 3pm), Speaker Offer via Sheila, Thank-You via Sheila, 3-Month Follow-Up via Sheila, Vault Reminder (daily 11am), Fireflies Landing Trigger (pending auth). Day-of Delivery Doc is LIVE; Thank-You and Follow-Up pending Gmail scheduler auth.
3 skill folders built to full spec. ss-content-processing (SKILL.md + example-output.md + downstream-skills.md), slai-effect-intro (SKILL.md + voice-dna.md + example-intros.md), ss-promo-generator (SKILL.md + example-promos.md + distribution-channels.md).
Speaker tracking via Google Sheet. Social Saturday Speakers Google Sheet is the single daily-updated source of truth. Application Heartbeat and Co-Host Heartbeat recipes retired — the sheet handles it without a recipe layer on top.
Cohost guide built and automated. Full document with run of show, speaker bio and credentials, announcements, chat drops, engagement prompts, continuity notes. Day-of Delivery Doc recipe produces and delivers it automatically every Friday.
Notion Sessions Database created. Social Saturday Sessions DB under SLAI Operations HQ. Needs manual Relation properties added.
Social Saturday Speakers Google Sheet mapped. Main Tracking, Speaker Outreach Pipeline, Host Roster with 10 co-hosts identified, per-date tabs, Archive, and Outreach Comms.
First-ever in-house promo design. Not Canva. Claude Code made the design itself. CREATE branding, real photo, SLAI logo, four formats.
Promo copy written and brand-enforced. Full Description and Web Teaser. 246-rule brand check passed before review.
Speaker confirmation email templates. 10-day and 2-day templates, written in Sheila’s voice from Anne’s Gmail.
Full announcements coaching analysis. Studied 6 transcripts. Identified Anne’s real patterns. Structure built and deployed.
Speaker follow-up SKILL.md. 8-step skill with membership decision tree, testimonials, brand enforcement gate.
Speaker guide template. One-pager for featured speakers with everything they need before going live.
Co-host model simplified. Volunteer roster dissolved. Three expert facilitators confirm through Sheila. Co-Host Heartbeat recipe and remote trigger retired — no longer needed.
Link QA Pre-Flight retired. Remote trigger removed. Manual QA via the master links registry when needed.
This process map. Scorecard, progress tracking, color-coded barriers. Updated to reflect both sessions.
Master links registry. 100+ links inventoried and verified. Broken links identified.
CRM prep workflow. Rule established and encoded: always pull People CRM before prepping Anne for any session.
CoP standing report-out + SLAI Effect callback. Both built into every week’s announcements permanently.
Solved (20)
6 Rube recipes wired. Day-of Delivery Doc, Fireflies Landing Trigger (not working — see blockers), Speaker Offer, Thank-You, 3-Month Follow-Up, Vault Reminder.
3 skill folders built. ss-content-processing, slai-effect-intro, ss-promo-generator. Each with SKILL.md and supporting files.
Social Saturday Speakers Google Sheet updated daily. Single source of truth for all speaker tracking. Application Heartbeat and Co-Host Heartbeat recipes removed — sheet handles it.
Notion Sessions DB created under SLAI Operations HQ.
Social Saturday Speakers Google Sheet mapped. Host Roster shows 10 co-hosts.
Cohost guide template built. Day-of Delivery Doc recipe produces and delivers it automatically every Friday.
Promo copy and first in-house design. Four formats. Brand-enforced.
Speaker confirmation email templates. 10-day and 2-day, Sheila voice.
10-minute announcements structure. 6 transcripts studied, coaching analysis done.
Speaker follow-up SKILL.md. 8-step skill with membership decision tree.
ss-content-processing skill. Full pipeline from transcript to atoms to guide to newsletter.
slai-effect-intro skill. Voice DNA, example intros, ready for Kate.
ss-promo-generator skill. Distribution channels documented.
Speaker guide template. One-pager for featured speakers.
Co-host confirmation goes through Sheila. Cohost Heartbeat recipe and remote trigger retired — not needed.
Master links registry. 100+ links inventoried and verified.
CRM prep workflow rule established and encoded
Member shoutouts — two candidate sources identified: program graduates (AI Academy, ACA, CoP pods) and the three women Kate features in each newsletter. Cannot be done by hand. Automated feed needed.
CoP standing report-out + SLAI Effect callback permanently in announcements
This process map. Updated to reflect both sessions.
Minor Blockers (3)
Fireflies auth. Landing Trigger recipe built but blocked on Fireflies API authentication.
Gmail scheduler auth. Thank-You and 3-Month Follow-Up recipes built but blocked on Gmail scheduler permissions.
Broken links. Some links in the registry still unverified. Kit not yet connected, Bitly not accessible.
Queued (4)
Blog magazine wall. Concept designed, runway item. Includes /social-saturday redirect on sheleadsai.ai.
Blotato / distribution automation. Not yet scoped. Distribution is the next phase to systematize.
LinkedIn auto-post via Blotato — unconfirmed. Mighty Networks stays manual permanently: requires a 16:9 thumbnail that must be generated separately from the LinkedIn 4:5.
Nurture campaign connection. The speaker relationship continues beyond the thank-you and 3-month follow-up — the ongoing nurture path is not yet built.
Brand Enforcement — Wider Coverage Needed

The 246-rule brand enforcement system currently runs on promo copy, speaker emails, the cohost guide, and skill outputs. That is not enough. Brand enforcement needs to run on every deliverable before Anne sees it — companion guides, newsletter intros, the cohost guide, speaker follow-up emails, thank-you drafts, and any content atom that gets published. Currently those stages are unguarded.

Legend
Automation
Human Action
Data Movement
Remaining Barrier
Fixed
In Progress
Queued
Phase 1
Booking the Speaker and Cohost
10+ days before the event — MOSTLY SOLVED
1 4 4
Human Actions
Identify speaker from the SS 20 list or CREATE applicant poolKate
Speaker confirms their dateSpeaker
Jen and Beth host the relaunch — confirm the host pairing for the session, a guest cohost steps in only when one of them has a conflictKate
Hosts confirm through SheilaHosts
Automation
Sheila agent sends scheduling DM via SlackSheila Agent
Data at this stage
SourceSpeaker record Notion People CRM
ChannelScheduling DM Slack text
OutputConfirmed date Google Calendar event
QA referenceSocial Saturday Speakers Google Sheet source of truth for all QA
Barriers and Status
Hosting model updated. Jen Schwartz and Beth Lyons host the Social Saturday relaunch. The earlier three-facilitator rotation is retired and the Slack cohost channel stays closed. A guest cohost steps in only when Jen or Beth has a conflict. Hosts confirm through Sheila.
SOLVED Hosting model updated. Jen and Beth host the relaunch, replacing the three-facilitator rotation. Cohost channel closed. Confirmations go through Sheila.Cleaner, more reliable, and fully internalized in the system.
SOLVED Speaker Offer via Sheila. Manual-trigger Rube recipe is LIVE. Sheila can send speaker invitations on command.Sheila handles outreach so Anne doesn’t have to initiate manually.
QUEUED Inbound speaker requests route to Sheila — not yet built. When live, speakers reach Sheila first, not Anne directly.Everything routes through Sheila when built.
SIMPLIFIED Application Heartbeat recipe retired. Speaker tracking lives in the Social Saturday Speakers Google Sheet, updated daily. Simpler and sufficient.One sheet, not a recipe layer on top of it.
SOLVED T-10 speaker readiness check. If speaker info is not in the Social Saturday Speakers Sheet by T-10 days, the agent flags Anne. Anne reviews the situation and confirms the plan for that session.The system surfaces the timing. Anne makes the call.
Phase 2
Speaker and Cohost Preparation
10 days to 2 days before the event — MOSTLY SOLVED
Watcher · confirmation DMs
4 3
Human Actions
Review speaker and cohost guide for the week — update any announcements before guides are deliveredAnne
10-day-out confirmation via the email on the Social Saturday Speakers Google SheetSheila
2-day-out confirmation via the email on the Social Saturday Speakers Google SheetSheila
Automation
Speaker guide delivered to speaker via Sheila — includes run of show, branded Zoom backgrounds (2 options), bio, credentials, and everything needed before going liveSheila
Cohost guide delivered to cohost via Sheila — includes run of show, speaker bio and credentials, announcements, chat drops, engagement prompts, and continuity notesSheila
Data at this stage
Source of truthSocial Saturday Speakers Google Sheet all speaker + cohost data lives here
AssetsZoom backgrounds 2 options, delivered via Sheila in speaker guide
ChannelAll comms via speaker’s email from Social Saturday Speakers Google Sheet
QA referenceSocial Saturday Speakers Google Sheet source of truth for all QA
Barriers and Status — Nearly All Resolved
SOLVED Confirmation templates exist. 10-day and 2-day Slack DMs written by Sheila. Standardized.Templates are standardized and in Sheila’s hands.
SOLVED Day-of Delivery Doc recipe runs Fridays at 3pm PT. The Saturday prep delivery is now automated via Rube.The missing automation layer is now in place.
SOLVED Speaker guide and cohost guide both delivered via Sheila. Cohost model overhaul complete — both guides include run of show, Zoom backgrounds, bios, credentials, and all prep materials. Anne reviews and updates announcements for the week before delivery fires.Done.
Phase 3
Promo Creation
Tuesday, 5 days before the event — MOSTLY SOLVED
First-time fix · outward-facing
7 2 1 3
Automation — Claude Code + Claude Design
Pull speaker details from Social Saturday Speakers Google Sheet and People CRM — never ask AnneClaude Code
Build promo design using templates and skills — Claude Code / Claude Design, not CanvaClaude Code / Claude Design
Extract dominant color from design using Python/PILss-pipeline.py
Write promo copy — Full Description + Social Saturday teaser + Web Teaser with BiosClaude Code
Apply approved CTA pills from Content Vault onlyClaude Code
Hyperlink all named programs (Social Saturday, CREATE, ACA, She Leads AI, AI Academy)Claude Code
Run full brand enforcement — 206 banned words + structural rulesClaude Code
Generate all derivative sizes from one master design — 4:5 for LinkedIn/social, 16:9 for Mighty Networks (different platform, different requirement), Kit email header, blog thumbnail, companion guide heroClaude Code / Claude Design
Design Principle
One design per week, built once from templates, made gorgeous — all derivative pieces flow from itAnne / Claude
Data formats at handoff
InputSpeaker record Social Saturday Speakers Google Sheet, speaker bio + history Notion People CRM, copy blocks Content Vault, design templates Claude Code / Claude Design skills
ProcessingMaster design HTML/PNG, dominant color hex string from ss-pipeline.py, brand-enforced copy markdown
OutputFull Description HTML, Social Saturday teaser text, Web Teaser with Bios HTML, social promo PNG 4:5 — LinkedIn primary, MN thumbnail PNG 16:9 — Mighty Networks only, Kit header PNG, blog thumbnail PNG, companion guide hero PNG
QA referenceSocial Saturday Speakers Google Sheet source of truth for all QA
Barriers and Status
SOLVED Promo copy written and brand-enforced. 246-rule brand check passed before review.Done.
SOLVED Promo design built in-house via Claude Code and Claude Design. Four formats. No Canva.Design quality upgraded. This is the permanent workflow now.
SOLVED ss-promo-generator SKILL.md built with full folder. SKILL.md + example-promos.md + distribution-channels.md. The promo creation process is a documented, repeatable skill.Distribution channels documented in the skill folder.
Phase 4
Promo Distribution
Tuesday after Anne approves — LinkedIn native (tagging required), Mighty Networks always manual (16:9 thumbnail required)
First-time fix · outward-facing
2 6 1 3
Automation
Claude Code assembles all promo assetsClaude Code
Slack Anne with “ready for review” notificationClaude Code to Slack
Human Actions — Approval gate
Anne reviews promo in Slack and approvesAnne
Post to Mighty Networks — always manual. Requires a 16:9 thumbnail, not the 4:5 used for LinkedIn. Must be generated separately before posting.Manual
Automated Distribution
LinkedIn company page — Anne posts natively. Tagging speakers and cohosts requires native posting; Blotato cannot tag people.Anne
Anne’s LinkedIn personal — Anne posts natively. Tagging speakers and cohosts requires native posting; Blotato cannot tag people.Anne
Data formats at handoff
InputApproved promo copy HTML/text, promo image PNG
OutputLinkedIn post text + 4:5 PNG — Anne posts natively, MN post text + 16:9 PNG — manual upload
QA referenceSocial Saturday Speakers Google Sheet source of truth for all QA
Barriers and Status
SOLVED Distribution channels documented. The ss-promo-generator SKILL.md folder includes distribution-channels.md with every platform and its requirements.Done.
NOTED Mighty Networks is always manual and requires a 16:9 thumbnail. LinkedIn primary is 4:5. Two separate files must be ready before posting to MN. This cannot be automated — manual post every week.MN has its own format requirements. The 4:5 LinkedIn image does not work there.
PERMANENT MANUAL LinkedIn is always native — Anne posts both personal and company page herself. Blotato cannot tag people, and tagging speakers and cohosts is required for every SS post.Decision locked. Not a gap — intentional.
QUEUED Nurture campaign — the ongoing speaker relationship beyond the thank-you and 3-month follow-up. The path forward exists conceptually but the campaign itself is not yet built.The speaker follow-up skill defines where this should go. Building the campaign is the next step.
Phase 5
Weekly Coordination
Automated daily, Tuesday, Wednesday, Thursday, Friday — HEAVILY AUTOMATED
7 1 5
Automation — Rube Recipes
Wednesday 9am — Rube recipe DMs Anne with 6-week lookaheadRube rcp_gLOAmdxX7Cqo
Claude runs approved mode, flags Anne directly via Slack DMClaude Code
T-10 check — agent flags Anne if speaker info is not yet in the Speakers Sheet. Anne reviews and confirms the plan for that session.Agent
Friday 9am — Rube checks for missing items, escalates if cancellation riskRube rcp_csNhb48nPB5m
Human Actions
Anne reviews the lookahead and says “send it”Anne
Data at this stage
ChannelSlack DMs text — Anne DM: D046L2E62JZ
Routes toAnne DM D046L2E62JZ — all actionable items go directly to Anne
DashboardLocation unclear HTML/Manus — TBD
QA referenceSocial Saturday Speakers Google Sheet source of truth for all QA
Barriers and Status
SIMPLIFIED Application Heartbeat retired. Speaker tracking via Social Saturday Speakers Google Sheet, updated daily. No recipe needed.Simpler is better here.
RETIRED Co-Host Heartbeat retired. Cohosts now confirm directly through Sheila. The automated monitoring loop is no longer needed.The new cohost model is simpler and more reliable.
SOLVED Day-of Delivery Doc runs Fridays at 3pm PT. The Saturday prep package is now automated.LIVE.
SOLVED Vault Reminder runs daily at 11am PT. Ensures approved content gets pushed to the vault consistently.LIVE.
RETIRED SS Link QA Pre-Flight remote trigger removed. Manual check via master links registry when needed.Not needed as a scheduled recipe.
TO DO Full link audit on the cohost guide. ACA advanced to Module 6 — any links in the cohost guide pointing to earlier ACA modules or ACA-related content are now outdated and will send cohosts to the wrong place. Every URL in the guide needs to be verified before next Saturday.ACA curriculum moved. Links that were right in April are broken now.
Phase 6
The Cohost Guide — Saturday Working Document
Delivered Friday by Day-of Delivery Doc — Anne uses this on Saturday, not a separate packet
5
The Cohost Guide
The single working document Anne uses on Saturday. Not a separate Anne-only packet — the cohost guide is it. Contains the run of show (with speaker bio and credentials), chat drops, announcements outline, continuity notes, and everything else. Delivered automatically every Friday via the Day-of Delivery Doc Rube recipe.
Run of Show
Lives inside the cohost guide. Includes speaker bio, credentials, and all intro language — everything Anne needs to introduce the speaker without looking anything up.
In cohost guide
Speaker Bio and Credentials
Pulled from People CRM and speaker’s Google Form submission. Included in the run of show section of the cohost guide — not a separate document.
Inside run of show
Cohost
Host for the session — Jen or Beth, in the Social Saturday Speakers Google Sheet.
In the Speakers Sheet
Zoom Link and Setup
From Google Calendar event
In Calendar
Last-Minute Speaker Requests
From Slack — manual check required
No centralized inbox
Chat Engagement Prompts and Talking Points
Built and filled for April 11. Included in the Saturday packet.
Built April 7
Pre-loaded Chat Drops
Every link verified and staged in the packet, ready to copy and paste into chat
Built April 7
Full Announcements Outline
10-minute structure with CoP report-out, SLAI Effect callback, member shoutouts. Shoutout candidates: program graduates (AI Academy, ACA, CoP) or Kate’s three newsletter features. Cannot be manual — automated feed needed.
Template built · shoutout source unsolved
Previous Session Continuity Notes AND Future Session Preview
Filled for April 11 with last week’s recap and next week’s preview
Built April 7
Coaching Analysis of Anne’s Announcement Patterns
6 transcripts studied. Patterns identified. Recommended template deployed in this week’s packet.
Built April 7
Barriers and Status
SOLVED Cohost guide template built and automated. Day-of Delivery Doc Rube recipe produces and delivers it every Friday at 3pm PT. Anne uses the cohost guide on Saturday — run of show, speaker bio, credentials, chat drops, announcements, everything in one place.One document, delivered Friday, covers Saturday completely.
SOLVED Announcements structure modeled from 6 real transcripts. 10-minute template with CoP report-out, SLAI Effect callback, and member shoutouts built and deployed.This was one of the hardest problems. Built from real patterns, not a guess.
TBD Member shoutouts — source not solved. Cannot be done manually. Two candidate feeds identified: (1) program graduates — AI Academy cohorts, ACA completers, CoP pod finishes — these are datable events with names attached; (2) the three women Kate features in each SLAI Effect newsletter — that list already exists, just not piped anywhere. Either feed could trigger a shoutout record that the cohost guide pulls automatically.The data exists in two places. The pipeline connection from those sources into the cohost guide is what needs to be built.
SOLVED Communication gaps addressed via the Day-of Delivery Doc. Packet built and delivered automatically every Friday. Team has what they need before Saturday.The prep is built in, not scrambled.
SOLVED Continuity notes built into the packet template. Previous session recap and next week’s preview are standard sections.Week-to-week narrative continuity is structural, not optional.
Phase 7
Live Event
Saturday 10am to noon PT — MOSTLY SOLVED
3 6 2 1
Human Actions — the live performance
Chat drops are pre-staged in the cohost guide (delivered Thursday, reminder Friday) — confirmed ready before 10amKate
Resource list must be verified before the eventKate
Zoom opens, host welcomes and introduces speakerJen and Beth
Speaker presentsSpeaker
Real-time chat support during the event. A Chat Messenger steps in when we expect more than 50 people.Jen
Chat engagement — links and resources shared by attendeesCommunity
Automation — capture is automatic
Fireflies records the entire sessionFireflies
Zoom saves the chat file automaticallyZoom
Post-event link capture — everything shared in chat gets harvestedClaude Code
Data captured
RecordingFull session transcript Fireflies text (auto-saved)
ChatZoom chat file txt, saved to OneDrive Zoom folder
QA referenceSocial Saturday Speakers Google Sheet source of truth for all QA
Barriers and Status
RETIRED SS Link QA Pre-Flight remote trigger removed. Link QA is handled manually via the master links registry when needed — not as a scheduled recipe.Not needed as an automated routine.
BLOCKED Fireflies Landing Trigger (Saturdays 4:30am PT) is built as a Rube recipe but blocked on Fireflies API authentication. Transcript capture still works (Fireflies records automatically), but the automated trigger to start content processing does not fire yet.Auth issue needs to be resolved. The recipe is ready; the permission is not.
Phase 8
Content Processing
Post-event, starting Saturday afternoon or Monday — FLEET RESTART PENDING
First-time fix · outward-facing Watcher · guide-to-social handoff
13 1 2 4
Automation — the biggest cluster in the whole pipeline
Pull Fireflies transcriptClaude Code / ss-pipeline.py
Pull Zoom chat file from OneDrivess-pipeline.py find_zoom_chat()
Mine content atoms by speaker — themes, quotes, tools, frameworksClaude Code
Build companion guide HTML using templateClaude Code
Extract promo dominant color for guide palettess-pipeline.py
Title = pulled from the event promo draft (LinkedIn / Mighty Networks / social media) — that’s the source, not the calendarClaude Code
Deploy to WordPress via PlaywrightPlaywright script
Write SLAI Effect newsletter intro for KateClaude Code
Take companion guide and generate social media promo — 4×5 for LinkedIn / Mighty Networks and derivative sizesClaude Code / Claude Design
Mine content for testimonials and use cases — things people say, things people put in chat. Use those.Claude Code
Run full 246-rule brand enforcement sweep on companion guide, newsletter intro, and all content atoms before anything goes to Anne or publishesClaude Code
Human Actions — approval gate
Anne reviews the companion guide draft and approvesAnne
Data Movement
Present draft to Anne via Slack notificationClaude Code to Slack
Vault approved guide to NotionClaude Code to Notion
Data formats at each stage
InputFireflies transcript text/JSON, Zoom chat txt, event promo draft text — LinkedIn / Mighty Networks, People CRM Notion
ProcessingContent atoms markdown, testimonials + use cases markdown, session context JSON from ss-pipeline.py
OutputCompanion guide HTML to WordPress, social promo PNG 4×5, vault entry Notion, newsletter intro text for Kit
QA referenceSocial Saturday Speakers Google Sheet source of truth for all QA
Barriers and Status
Pipeline documented but agent fleet went dark Apr 8. Restart decided Apr 27 2026 — transcript → companion → SLAI Effect intro should fire automatically without Anne prodding. Companion piece moving to Claude Design. Skills and templates are all in place; the fleet restart is the only remaining action.
UPDATED SS content processing skills refreshed. ss-content-processing, slai-effect-intro, and ss-promo-generator all updated to reflect current pipeline decisions.Skills now match what the pipeline actually does.
SOLVED Processing skill built. ss-content-processing SKILL.md takes a Fireflies transcript and produces content atoms, companion guide, and newsletter intro as a single orchestrated skill.The missing orchestration layer is now in place.
SOLVED slai-effect-intro skill built. Dedicated skill for writing newsletter intros with voice DNA and example intros documented.Kate has a repeatable skill for her newsletter workflow.
SOLVED Companion guide pipeline updated. Companion piece moving to Claude Design — previous pain resolved. Template and WordPress deploy via Playwright remain in place for other outputs.Claude Design removes the production friction that was slowing companion creation.
~30 DAYS Blog magazine wall on sheleadsai.ai — concept is designed, on the roadmap for about a month out.On the list. Just haven’t had the time.
TO DO SS transcript processing skill must explicitly mine for testimonials AND use cases — not just quotes and frameworks. If it doesn’t have those two as discrete content atom categories, add them. Companion guide SKILL.md v3 Step 4 also needs this update.Testimonials and use cases are the proof layer. They belong in every guide.
ADDED Brand enforcement now runs on all Phase 8 outputs — companion guide, newsletter intro, and content atoms — before anything goes to Anne or publishes. 246-rule sweep is a named step in the pipeline.Nothing leaves this phase unguarded.
Phase 9
Speaker Follow-Up
Within 48 hours of the event — MOSTLY SOLVED
First-time fix · outward-facing Watcher · fleet-dependent emails
2 1 3 5 1
Automation — drafting and data
Draft personalized thank-you email — references specific moments from the session, includes the replay link and the companion guide link. Lands in Gmail Drafts for Kate to review before sending.Claude Code → Gmail Drafts
Run 246-rule brand enforcement on email draft before it reaches Gmail DraftsClaude Code
Decision tree — IF speaker is not yet a member: include a warm invitation to join + Anne’s 30-min scheduling link. IF speaker IS a member: thank and celebrate, scheduling link included if the relationship warrants a deeper connection. Kate reviews and adjusts before sending.Claude Code
Human Actions
Kate reviews and sends the email via GmailKate
Data Movement
Pull testimonials from Speaker Kudos formGoogle Form → Claude Code
Update People CRM with speaker record and session notesClaude Code → Notion
Email draft deposited in Gmail Drafts — Kate reviews and sendsClaude Code → Gmail Drafts
Data at this stage
InputContent atoms markdown, Kudos form responses Google Form, People CRM Notion, session replay link Fireflies or Zoom, companion guide URL WordPress, Anne’s 30-min scheduling link static — always the same
OutputEmail draft Gmail Drafts — Kate reviews, adjusts if needed, then sends, CRM update Notion
QA referenceSocial Saturday Speakers Google Sheet source of truth for all QA
Barriers and Status
SOLVED Speaker follow-up SKILL.md is done. 8-step skill with membership decision tree, testimonial pull, brand enforcement gate, and archive checklist.Done.
UPDATED Thank-you email spec updated. Includes: specific moments from chat, session replay link, companion guide link, and Anne’s 30-min scheduling link with invitation to connect. Draft lands in Gmail — Kate reviews, removes scheduling link if not appropriate, and sends.The email does real relationship work, not just a courtesy close.
SOLVED 3-Month Follow-Up via Sheila Rube recipe built. Fires 1st of each month. Keeps the speaker relationship alive long after the event.Fleet dark since Apr 8 — restart decided Apr 24. Blocked on Gmail scheduler auth, but the recipe is ready.
SOLVED Announcements coaching done. 6 transcripts studied. Speaker guide template built.Done.
SOLVED Notion Sessions Database created under SLAI Operations HQ. Session data now has a structured home.Needs manual Relation properties added.
BLOCKED Gmail scheduler auth. Thank-You and 3-Month Follow-Up recipes are built but cannot fire until Gmail scheduler permissions are resolved.The recipes exist. The auth does not. This is a permissions fix, not a build.
ADDED Brand enforcement now runs on thank-you email drafts before they reach Gmail Drafts. 246-rule sweep is a named step in the pipeline.Outbound speaker communications get the same brand check as promo copy.
PARKED Speaker data → CRM. Session data, speaker record, follow-up history all need to flow into the People CRM automatically. Scope is clear, execution is not happening yet. Parked until there is bandwidth.The data exists. The pipeline connection does not. Not urgent enough to block anything else right now.
Phase 10
Content Longevity & Legacy
Ongoing — what we do with the archive we are building
Watcher · longevity distribution
3 1 5
What we do now
Transcript → NotebookLM knowledge base. Every session feeds the KB. Used for data mining, research, and curriculum development.NotebookLM
Storytelling extraction — quotes, moments, speaker frameworks pulled into content atoms for downstream reuseClaude Code
Use cases and testimonials mined from transcript and chat — the proof layer for every downstream deliverableClaude Code
Archival system needs attention. Three asset types — all valuable, all currently hard to find.
Event Replays
Split across Zoom (OneDrive), Fathom, Fireflies, and Drive. Somewhat organized within each platform but no unified index across them. Finding a specific session replay requires knowing which platform captured it and when.
Transcripts
Live in Fireflies, organized by date. Not tagged by topic, speaker, program, or theme. Searchable in Fireflies only if you know what you’re looking for. No cross-session index. NotebookLM is the only real retrieval layer we have, and it’s manual to set up per-session.
Artifacts
Companion guides on WordPress. Content atoms in Notion Content Vault. Skills in Drive and GitHub. Cohost guides across multiple locations. No unified index or consistent naming convention across systems. A new team member cannot easily find everything built for a specific session. Don keeps the archive and builds the unified index as part of post-production.
We are building a historically significant archive of women at the start of the AI era and not treating it that way yet.
Opportunities — not built, worth scoping
What we could build
IDEA Private podcast — three formats from one session. Every SS recording becomes three cuts: a 10-minute learn (one concept, standalone), a 20-minute learn (the core teaching arc), and a 30-minute learn (full session highlight). Subscriber-only feed. Recordings already exist — just need editing and a distribution layer.Same source material, three different audiences and attention windows. SS content is already podcast-quality.
IDEA Learning journey — workshop library. SS sessions sequenced into a curriculum path by topic. Someone joins SLAI today and can move through years of curated sessions as a full AI education in workshop form.The content exists. The gap is sequencing and a discovery layer.
IDEA Opus Clips → dedicated social channel. A social account that is nothing but SLAI in clips. Every SS session processed through Opus Clips. TikTok, Reels, Shorts. Tag the speakers in every clip. Could hire someone to set up and run this workflow end-to-end — Anne doesn’t touch it.We have a lifetime of footage. The clips exist in raw form — just uncut and undistributed.
HIRE Opus Clips → TikTok workflow contractor. Someone who knows Opus Clips sets up the pipeline, handles clip selection, tags speakers, and manages the queue on a regular cadence. This is a real role, not a Claude task.The right hire turns this into an ongoing channel with almost no Anne involvement.
IDEA Coffee table book — “They Used to Call Us Nontechnical.” A document of what women were building at the start of the AI era. SS sessions, speaker portraits, community moments. For the legacy and founders audience. Something you can hold.This record exists. It just hasn’t been shaped into something permanent yet.
Archival — What Currently Happens After Approval
Companion guide → WordPress Session record → Notion Sessions DB Content atoms → Content Vault Speaker record updated → People CRM Blog index updated → sheleadsai.ai
Nothing archives until Anne approves. Kate and Don are tagged in Notion after the vault push.
What Is Not Archived — Replays, Transcripts, Artifacts
Three years of event replays, Fireflies transcripts, and session artifacts are important and valuable. They live across multiple systems with no unified index or consistent naming convention. Building a retrieval layer is the next priority for the archive.
Event replays → OneDrive (unnamed, unindexed) Transcripts → Fireflies (date only, no tags) Artifacts → scattered across 5+ systems
KPIs
Targets and measures for Social Saturday. Full demand and brand metrics to be built with Stanley and Don.
Operational Target
< 1 hr
of anyone’s time per week to run Social Saturday end-to-end
Attendance Target
50+
women per session
Metrics to Build — Stanley + Don
The following measures are not yet tracked. Anne, Stanley, and Don need to determine the right data sources and methodology before these go live.
Demand conversions — SS attendee → paid program Brand visibility and reach Speaker re-engagement rate Companion guide readership SLAI Effect open rate from SS intro
SLAI Matriarchal Agentic System — Agents and Skills Involved in This Document
Agentic Team
Sheila — Chief of Staff · weekly coordination DMs · all-routes entry point
Scout — Intel and research feed
Pepper — Content generation
Rena — Pipeline enforcement
Marie — Systems audit and Notion
Margaux — Skill health
Stanley — KPI and BI
Margot — Meeting prep
Romy — Relationships
Humans (HITL)
Anne Murphy — Vision, approvals and final sends, sponsorships and growth. Steps back from hosting and booking into founder presence.
Jen Schwartz and Beth Lyons — Hosts of the Social Saturday relaunch. Beth designs facilitation and trains the CoP, Jen runs comms, the inbox, and difficult attendees.
Kate Rivera — Speaker booking, event content, registration, member-facing event comms, companion guide review.
Don Wackerly — Systems behind events, post-production, archiving, and the tech check.
Jasmine Schwarz — Community Manager. At events, promotes them in Mighty Networks.
Skills — Updated May 2026
ss-content-processing — Transcript → content atoms → companion guide · mines testimonials + use cases
slai-effect-intro — Newsletter intro from session · voice DNA + example intros
ss-promo-generator — Promo creation · 4:5 LinkedIn + 16:9 MN · distribution channels documented
speaker-follow-up — Thank-you with replay link + companion guide + 30-min scheduling link · membership decision tree · 3-month nurture
companion-guide v3 — Guide template + WordPress deploy via Playwright
Automated Routines (Rube + Claude Code)
Day-of Delivery Doc — Fri 3pm PT Fireflies Landing Trigger — not working Vault Reminder — daily Thank-You via Sheila — Sun (restart pending) 3-Month Follow-Up via Sheila — monthly (restart pending)
SS Autonomy Roadmap
Built on Beth Lyons’ Process Mapping Methodology. Last updated May 2026.
Humans host, build relationships, and make creative decisions. Agents handle everything else.
Approval Lifecycle — Where Everything Should Land
Phase A
Active Review
Anne reads everything. Creative output, promo copy, speaker emails, companion guides.
HITL — Full
Anne reads, approves, and sends. Nothing leaves without her eyes on it.
Phase B
Rubber Stamp
Anne glances — brand enforcement catches everything. Weekly lookahead is here now.
HITL — Light
Anne glances but doesn’t dig in. Brand enforcement is the real check. She stops it only if something is obviously off.
Phase C
Exception Only
Agent ships. Anne notified. She intervenes only if something is wrong. Confirmation DMs and vault entries should move here.
HITL — Notification
Agent ships and pings Anne. She reads the ping, does nothing unless she flags it. Her brain is not the trigger.
Phase D
Silent
Agent ships. Anne never sees it unless she wants to. CRM updates, link QA belong here.
HITL — None
Agent ships silently. Anne opts in to see it. She is never the external environment for this work.
Current Automation Status
LIVEDay-of Delivery Doc — Friday 3pm PT. Cohost guide built and delivered automatically.
LIVEVault Reminder — daily 11am PT.
LIVESpeaker Offer via Sheila — manual trigger, Sheila sends invitation on command.
BLOCKEDFireflies Landing Trigger — recipe built, blocked on Fireflies API authentication.
BLOCKEDThank-You + 3-Month Follow-Up via Sheila — recipes built, blocked on Gmail scheduler permissions.
PERMANENT MANUALLinkedIn — Anne posts natively. Tagging speakers and cohosts is required; Blotato cannot tag people.
PERMANENT MANUALMighty Networks — always manual, requires 16:9 thumbnail generated separately. Not automatable.
PERMANENT MANUALKit email sending — Claude Code drafts, Kate reviews brand and assets, Kate sends. Always human-confirmed.
RETIREDApplication Heartbeat, Co-Host Heartbeat, Link QA Pre-Flight — removed. Google Sheet + simpler process replaces them.