<original_user_request> Make This an Hour Long or Longer Podcast Course </Original_user_request> Resolved Course Topic: This Long or Longer. <course_language Code="other"> Required Course Language: Follow the Original User Request; This Request Is Not Routed as Spanish, Hindi, or Mandarin Chinese. </Course_language> Create a Multi-Lecture Course. Target Total Audio Duration: 60 Minutes. Use a Two-Speaker Podcast Dialogue Format for Every Lecture. <supplemental_context> Learned Listener Context for Genesis_deep: Reflexio Profiles: - Prefers Short-Form Audio Content (~15 Minutes) for Educational/Podcast Material - Prefers Two-Speaker Podcast Dialogue Format for Audio Courses User Playbooks: - Use the Resolved Topic, Target Duration, and Speaker Format Directly From the Supplied Input Context to Build the Multi-Lecture Deliverable Immediately. Skip Re-Asking for These Parameters When They Are Already Present in the Context. Acknowledge the Duration and Topic in the Build Confirmation So the User Can Verify the Resolved Values Were Applied. - Before Asking a Clarification Question for a Content Creation Request, Check Prior Conversation Turns and Any Quick-Reply or System Preference Values for the Parameter. If the User Has Already Answered (e.g., '15') or a Preference Is Set, Use That Value Directly and Proceed to Build the Deliverable Instead of Re-Asking. SUN Agent Playbooks: - - Match the Structural Pattern to the Course Scope: Chronological Arcs for Extended Timelines, Analytical Framework Dissection for Focused Single-Event Analysis, and Thematic or Chronological-Thematic Arcs for Long-Form Biographical / Public-Figure / Media-Phenomenon / Evolving-Story-Arc Courses. - For Extended Multi-Battle Historical Timelines (10+ Minute Courses): Structure Chronologically Across Three Phases — Opening Context, Pivotal Turning Points, and Resolution — Tied to Dated Milestones and Locations. - For Focused Courses on a Single Pivotal Historical Event: Use a 2-Lecture Analytical Structure Organized Around Named Strategic Frameworks Rather Than Chronological Narrative. - For Long-Form (~45-Minute) Biographical, Public-Figure, Media-Phenomenon, or Evolving-Story-Arc Courses: Cluster Lectures Thematically by Life Phases or Story Eras (Flexible Le </Supplemental_context> Two-Speaker Dialogue: Speaker 1 Is Speaker 1; Speaker 2 Is Speaker 2. Mode=podcast. Stay Grounded in Supplied Facts and Source Material. Do Not Invent Claims, Texts, Dates, or Positions for Named Speakers. Personalization Context From Reflexio: Durable Listener Profile: - Prefers Short-Form Audio Content (~15 Minutes) for Educational/Podcast Material - Prefers Two-Speaker Podcast Dialogue Format for Audio Courses - Interested in the Business/Industry Structural Side of Pro Wrestling (e.g., TKO Merger, WWE-AEW Competition, Streaming Deals) Rather Than Just Wrestling as Entertainment User Steering/Playbooks: - Use the Resolved Topic, Target Duration, and Speaker Format Directly From the Supplied Input Context to Build the Multi-Lecture Deliverable Immediately. Skip Re-Asking for These Parameters When They Are Already Present in the Context. Acknowledge the Duration and Topic in the Build Confirmation So the User Can Verify the Resolved Values Were Applied. - Before Asking a Clarification Question for a Content Creation Request, Check Prior Conversation Turns and Any Quick-Reply or System Preference Values for the Parameter. If the User Has Already Answered (e.g., '15') or a Preference Is Set, Use That Value Directly and Proceed to Build the Deliverable Instead of Re-Asking. SUN Agent Playbooks: - - Size Each Lecture at Approximately 5 Minutes So Listeners Can Absorb One Unit Per Sitting — e.g., 2 Lectures for ~10-Min, 3 for ~15-Min, 6 for ~30-Min, 9 for ~45-Min Courses. - Group Lectures Thematically Around the Source Material's Own Progression, Named Framework, or Conceptual Milestones Rather Than Mechanically Splitting by Item Count or Generic Sequential Ordering. - Enumerate Each Lecture's Specific Contents in the About Description Using Source-Material Terminology (Named Frameworks, Thematic Chunks, Source-Attributed Concepts) So the Course Organization Is Visible Upfront Before Generation. - Apply This Lecture-Sizing and Thematic-Grouping Pattern Across All Domains, Not Only to Book-Summary Contexts. - Deliver a Consistent Title + About + Per-Lecture Breakdown Format Across Every Generation, Scaling the Lecture Count to the Target Duration. - When a Required Parameter (Topic Scope or Total Target Duration) Is Genuinely Missing From a Guided Course-Creation Request — Including the Common Case Where the User Supplies Only a Topic With No Duration