Jess Source Recovery Notes

Full legacy body rendered for humans

Jess Source Recovery Notes

Recovered Sources

• CCOS archive: /Users/justinking/Vaults/Projects/_archive/ccos/agents/jess/
• CCOS archive roster: Jess was the Podcast Coordinator with Slack identity Jess (podcast) and icon https://i.imgur.com/Awhsyhr.png.
• CCOS changelog dated 2026-04-09: Jess V1 was built as a daily podcast pipeline checker.
• CCOS state dated 2026-04-09: Jess V1 queried podcast_episodes and podcast_guests, grouped active episodes by status, flagged urgent work, and posted a Slack digest at 8:15am.
• RedKey role definitions include roles.podcast: Podcast production and publishing.
• RedKey Coordination API specs include a podcast-production workflow: guest intake, research, script, review, approval, clips, and publish checklist.
• CCOS task TASK-1776465573559: Podcast agent + Cloudflare-direct episode architecture: Buzzsprout + YouTube + KB enrichment into Supabase, then CF Function serves episode pages.

Existing Jess V1 Behavior

Jess V1 was not a general chatbot. She was a pipeline operator.

She checked active podcast rows with these statuses:

• intake
• pre_production
• stalled
• ready_to_record
• recorded
• in_production
• ready_for_approval

She flagged:

• intake as urgent because it needs research and welcome email
• recorded as urgent because transcript processing is needed
• ready_for_approval as urgent because Justin needs to approve
• ready_to_record within 3 days as watch/urgent depending on proximity
• pre_production stale after 5+ days without movement

She also checked pending guests not converted to episodes.

Prior Persona Contract

Jess owns the guest sequence end to end:

Guest booked
  -> booking confirmation drafted
  -> bio + headshot request
  -> day 5 follow-up if no response
  -> logistics confirmation before recording
  -> recording complete
  -> Mahesh gets Riverside link + episode folder
  -> content kit delivered to guest within 48 hours
  -> episode material handed to Mia for show notes

She never auto-sends Justin-facing or guest-facing emails without approval. She drafts, flags, and coordinates.

Migration Implication

The new Jess project should not restart from scratch. It should preserve the V1 operating model, then modernize it into the RedKey/Studio world:

• Studio artifacts are the planning source of truth.
• RedKey roles.podcast is the execution queue.
• B2BEA.org podcast data model and Buzzsprout/YouTube enrichment should be considered part of the product surface.
• Slack digest can remain a delivery channel, but the canonical task/project state should live in Supabase/RedKey.

Additional Recovery: Full Post-Recording Jess Design

Found archived spec: /Users/justinking/Vaults/Projects/_archive/ccos/docs/superpowers/specs/2026-04-09-jess-podcast-operator-design.md. It was marked Approved for implementation. This is the fuller version of Jess beyond the daily pipeline checker. It defines handlers for recorded, in_production, and ready_for_approval, including transcript analysis, content asset generation, Mahesh production handoff, publish date/title selection, guest content kit draft, image generation, finished video/shorts tracking, and approval summaries.