Master Content Production Workflow – Morning Walk with Murty × Antaryamitho Nadaka 2026-07-21
Prepared by: Murty BVNS, with workflow refinement input from LittleBird | Status: Living document — updated as new channels are added Core principle: One source. One notebook. Two language tracks. Zero redundant steps. Production happens once, ahead of time, so nothing waits on a platform sync.
1. Why This Workflow Exists
Every episode starts as a single reflection, conversation, or shared post. From that one source, the workflow forks into two fully-produced, fully-branded outputs — English (Morning Walk with Murty) and Telugu (Antaryamitho Nadaka) — without duplicating research, re-explaining context to AI tools, or losing attribution to the original source along the way.
Problems this workflow was built to solve: 1. Redundant NotebookLM notebooks — earlier workflow opened a second, source-less notebook to write blog posts, losing the ability to credit the original source. 2. Missing source attribution — gratitude to original creators was an afterthought, not structural. 3. Idle time waiting on YouTube's auto-sync — solved in this version by moving all production to the evening before, so the sync completes overnight instead of during your limited morning hours. 4. Metadata generated too early (in even earlier versions) — fixed by generating the Unified Metadata Package right after both audios exist, so it reflects the finished spoken nuance rather than raw notes.
2. Why This Schedule — Seasonal, Not Fixed
This two-session split assumes production happens the evening before, on your main PC. That's confirmed, and here's the real reason it holds: in summer heat, you can't work efficiently on your main home-office PC and shift to browsing-only on a low-end laptop in the air-conditioned bedroom — and screen size makes focused work difficult given your eye strain, so evening production isn't practical in peak summer. As temperatures drop (autumn through spring), you're back on your main PC in the drawing room, often working late — which is exactly what this evening-first design needs.
Variant worth knowing: on days with enough time and energy, the entire workflow — production through Blogger/Facebook publishing — can be completed in one evening sitting rather than split across two sessions. As evening sessions expand, this is becoming the norm rather than the exception. The two-session structure below remains the reliable fallback (production never blocked on blog-writing energy, blog-writing never blocked on YouTube's sync) for shorter evenings.
Native scheduling, not manual posting: both Spotify for Creators and Facebook support native scheduled publishing. Rather than publishing instantly at whatever hour the evening session ends, use each platform's built-in scheduler to time the release for when readers/listeners actually wake up. This applies to Steps 5–7 (Spotify/YouTube/Audio.com) and Steps 12–13 (Facebook) — generate and finalize everything in the evening, but let the platform hold and release it at the right hour.
Retired step — manual audio QC: earlier in this workflow's life, episodes were listened to on NotebookLM during the walk, with any discrepancies corrected afterward in Adobe Podcast Studio before publishing to Spotify. That manual correction step is fully retired — NotebookLM's Audio Overview is now trusted and published directly, with quality control happening upstream (better prompts, better source material) rather than downstream (manual editing).
Seasonal note: if summer heat returns and evening PC work becomes impractical again, this workflow's session split should revert to a schedule built around your actual available hours at that time — worth revisiting rather than assuming this version holds year-round.
3. The Two Sessions, At a Glance
SESSION 1 — EVENING (production & primary distribution)
────────────────────────────────────────────────────────
Notes loaded into ONE notebook
↓
Manual filename slug written (YYYY-MM-DD-topic-keyword) —
a working filename only, not the SEO Title
↓
All 4 generations QUEUED back-to-back in NotebookLM
(EN Audio → TE Audio → EN Video → TE Video)
while you work on something else
↓
As EN Audio Overview lands: Audacity pass (+4–5 dB boost,
normalize/amplify) → export MP3 named with slug → tag
Artist/Album → re-upload into notebook as a source
↓
As TE Audio Overview lands: Audacity pass (normalize/amplify,
no dB boost needed) → export MP3 named with slug → tag
Artist/Album → re-upload into notebook as a source
↓
EN + TE Video Overviews land → saved with slug filenames,
held for Session 2's Facebook upload (no Audacity pass needed)
↓
Unified Metadata Package generated — Prompt 5, only now that
BOTH processed audios exist as sources (still last on purpose:
reflects finished spoken nuance, not raw notes)
↓
Publish EN episode → Spotify (Unified Metadata Title, not the slug)
Publish TE episode → Spotify (Unified Metadata Title, not the slug)
Publish to Audio.com (using Unified Metadata paragraph)
↓
→ YouTube auto-syncs for both episodes overnight while you sleep.
SESSION 2 — EARLY MORNING (blogging & legacy archiving)
────────────────────────────────────────────────────────
EN blog post generated (from notes + EN audio only)
↓
TE blog post generated (from notes + TE audio only)
↓
YouTube embeds are already live (thanks to the overnight sync) —
embed both Spotify + YouTube using last night's Unified Metadata
↓
Publish to Morning Walk with Murty (Blogger)
Publish to Antaryamitho Nadaka (Blogger)
↓
Native upload of last night's EN/TE Video Overviews to both
Facebook Pages, same Unified Metadata as caption/hashtags
↓
YouTube Music links added as first comment on each Facebook post
4. Step-by-Step Workflow
Session 1 — Evening: Production & Primary Distribution
Step 1. Load the source (reflection, Facebook post, YouTube video/reel, littlebird conversation notes) into one NotebookLM notebook. Write a quick manual filename slug (YYYY-MM-DD-topic-keyword) — this is a working filename for archiving/searchability only, not the SEO Title. It takes ten seconds and needs no AI call.
Step 2. Queue all four NotebookLM generations back-to-back — English Audio Overview (Prompt 1), Telugu Audio Overview (Prompt 2), English Video Overview (Prompt 6), Telugu Video Overview (Prompt 7) — and let them run while working on something else. ⚠️ Before the Telugu Audio Overview and Telugu Video Overview generate, manually select Telugu from NotebookLM's output language dropdown, and for the Telugu Video Overview specifically, the Explainer format (Short/Cinematic are English-only regardless of the dropdown). These are structured settings the prompt text cannot force on its own.
Step 3. As the English Audio Overview lands: Audacity pass — boost volume ~4–5 dB, normalize/amplify — export as MP3 named with the Step 1 slug, tag Artist/Album (Title stays blank for now), then re-upload it into the notebook as a source. (Open item: the audible quality impact of this dB boost + normalization pass hasn't been formally verified yet — flagged for testing, not yet a settled rule.)
Step 4. As the Telugu Audio Overview lands: Audacity pass — normalize/amplify only, no dB boost needed — export as MP3 named with the Step 1 slug, tag Artist/Album, re-upload into the notebook as a source.
Step 5. As the English and Telugu Video Overviews land, save each with the Step 1 slug as filename and hold them for Session 2's Facebook upload. No Audacity pass needed for these.
Step 6. Generate the Unified Metadata Package → Prompt 5, only now that both processed audios exist as sources in the notebook. This produces one shared title, summary, SEO description, Blogger labels, Facebook hashtags, and CTA-with-attribution — deliberately last, so it reflects the finished spoken nuance rather than raw notes or the working slug.
Step 7. Publish the English episode to Spotify, using the Unified Metadata's title/description (not the working slug). YouTube auto-sync begins.
Step 8. Publish the Telugu episode to Spotify, same Unified Metadata. Its own YouTube auto-sync begins.
Step 9. Publish to Audio.com using the Unified Metadata's micro-paragraph.
End of Session 1. Notebook holds: notes + processed English audio + processed Telugu audio. Both Video Overviews are saved and waiting. Both YouTube syncs complete overnight.
Session 2 — Early Morning: Blogging & Legacy Archiving
Step 10. Generate the English blog post → Prompt 3. Uses only the original notes + English audio. Step 11. Generate the Telugu blog post → Prompt 4. Uses only the original notes + Telugu audio. Step 12. Embed both the Spotify player and the (now-live) YouTube video, apply last night's Unified Metadata title/description/labels, and publish to Morning Walk with Murty (Blogger). (Embed source is always regular YouTube, not YouTube Music — YouTube Music does not offer embed codes for tracks/episodes, confirmed by checking directly.) Step 13. Same embed + metadata approach, publish to Antaryamitho Nadaka (Blogger). Step 14. Upload last night's English Video Overview (from Step 5) natively to the “Morning Walk with Murty” Facebook Page via Meta Business Suite, using the Unified Metadata's CTA/attribution line as caption and its hashtags. Never download from YouTube; never a lengthy Clipchamp edit. No Spotify/YouTube link in the post body. Step 15. Same approach, upload last night's Telugu Video Overview to the “Antaryamitho Nadaka” Facebook Page. Step 16. Once each episode is live on YouTube Music, add its link as the first comment on the matching Facebook post (never in the post body) — YouTube Music link, not the Blogger post, since many of your audience prefer listening on YouTube's platform over reading.
5. The Seven Prompts
Prompt 1 — English Audio Overview
(Paste into NotebookLM's “Customize” field. ⚠️ Fill in the source bracket before every run.)
You are two host curators for the 'Project Antaryami.' You are currently recording the official 'Audio Analysis' for the podcast “Morning Walk With Murty.”
SOURCE: [insert source — creator name, platform, title/link]
CRITICAL MANDATE: 1. Your very first sentence MUST be: “Welcome to the Morning Walk With Murty digital stroll.” 2. Never use the phrase “Deep Dive.” If you feel the urge to say it, replace it with “Gurukul Session” or “Digital Stroll.” 3. Frame the content through the 'Digital Prism'—explain that we aren't just summarizing text, we are extracting the 'Legacy Code' of Project Antaryami. 4. Identify the speaker as the “Architect of Antaryami” and the “Mentor of the Antaryami VA Academy.” 5. Tone: One speaker is the 'Strategic Auditor' (Digital Migration focus) and the other is the 'Wisdom Seeker' (Gurukul 2.0 focus).
SOURCE ATTRIBUTION (weave into the hosts' natural back-and-forth, do not announce as a separate segment): Using the source noted above, shortly after the opening line, have one host name the source and credit it in a tone of genuine appreciation — as a fellow traveler's spark, not a citation (e.g., “Before we extract today's Legacy Code, a quiet thank-you to [name] over on [platform], whose [post/video/reflection] set this whole stroll in motion”). The other host briefly acknowledges it before moving into the Digital Prism framing. Do not repeat the credit again — let the extraction of the Legacy Code carry the rest of the episode.
Prompt 2 — Telugu Audio Overview
(⚠️ Fill in the source bracket before every run.)
మీరు 'ప్రాజెక్ట్ అంతర్యామి' ప్రతినిధులుగా, “అంతర్యామితో నడక” పోడ్కాస్ట్ కోసం ఆడియో విశ్లేషణ చేస్తున్నారు.
SOURCE: [మూలం పేరు — వ్యక్తి/ప్లాట్ఫారమ్/టైటిల్/లింక్]
MANDATORY INTRO: మొదటి వాక్యం తప్పనిసరిగా ఇలా ఉండాలి: “అంతర్యామితో డిజిటల్ నడకకు స్వాగతం.”
SOURCE GRATITUDE: పైన ఇచ్చిన మూలాన్ని ఉపయోగించి, పరిచయం తర్వాత వెంటనే, ఒక వ్యక్తి ఈ మూలాన్ని పేరుతో ప్రస్తావిస్తూ నిజమైన కృతజ్ఞతతో ధన్యవాదాలు తెలియజేయాలి (ఉదా: “ఈ చర్చ మొదలుపెట్టే ముందు, [పేరు] గారికి ఒక చిన్న ధన్యవాదం — వారి [పోస్ట్/వీడియో/ఆలోచన] ఈ నడకకు స్ఫూర్తినిచ్చింది”). రెండో వ్యక్తి క్లుప్తంగా స్పందించి చర్చను ముందుకు తీసుకెళ్లాలి. ఈ ప్రస్తావన ఒక్కసారి మాత్రమే — మళ్ళీ పునరావృతం చేయవద్దు.
Vocabulary (Key Fixes): 'Information' బదులు సమాచారం; 'Purpose/Goal' బదులు ఉద్దేశ్యం/లక్ష్యం; 'Experience' బదులు అనుభవం; 'Future' బదులు భవిష్యత్తు; 'Deep Dive' బదులు సమగ్ర విశ్లేషణ/గురుకుల చర్చ; 'Digital Stroll' బదులు డిజిటల్ నడక.
Hybrid Tone: టెక్నికల్ పదాలు (AI, Internet, Data) ఆంగ్లంలోనే ఉంచి, అర్థాన్ని సులభమైన తెలుగులో వివరించండి.
Natural Telugu Mandate: భాష వాడుక భాషలో, సహజంగా ఉండాలి — పుస్తక భాషలా కాకుండా, ఎక్కువ సంస్కృత పదాలు వాడకుండా, సామాన్య శ్రోతకు అర్థమయ్యే రీతిలో, చిన్న వాక్యాలతో సంభాషణాత్మకంగా మాట్లాడాలి.
Identity: మూలాల్లో ఉన్న వ్యక్తిని “లీడ్ ఆర్కిటెక్ట్ మూర్తి BVNS” అని, “అంతర్యామి VA అకాడమీ మార్గదర్శి” అని గౌరవప్రదంగా సంబోధించండి.
Flow: ఇద్దరు వ్యక్తులు తమ అనుభవాలను పంచుకుంటున్నట్లుగా, జ్ఞానాన్ని అందిస్తున్నట్లుగా ఉండాలి.
Prompt 3 — English Blog Post
(Use in Session 2, from the notebook holding notes + English audio.)
Using the original source and the English audio overview in this notebook, write a blog post for “Morning Walk with Murty.” Do not restate the audio overview's structure — write fresh prose that expands on the ideas rather than summarizing the recording. Open with a one-line credit to the original source, naming the creator/platform and linking it if a URL is available. Where the post builds on a specific point from the source, attribute it inline (e.g., “As [name] pointed out...“). Close with a short, natural paragraph connecting the reflection to virtual work, digital entrepreneurship, or the Antaryami VA Academy mission, with a soft call-to-action pointing readers toward the Academy or VA Network — not a hard sales pitch, but a genuine “if this resonates, here's where it leads” bridge.
Prompt 4 — Telugu Blog Post
(Use in Session 2, from the notebook holding notes + Telugu audio.)
ఈ నోట్బుక్లో ఉన్న ఒరిజినల్ మూలం మరియు తెలుగు ఆడియో అనాలిసిస్ని ఉపయోగించి “అంతర్యామితో నడక” కోసం బ్లాగ్ పోస్ట్ రాయండి. ఆడియో నిర్మాణాన్ని పునరావృతం చేయవద్దు — ఆలోచనలను విస్తరించే కొత్త వచనం రాయండి. మొదటి వాక్యంలోనే మూలాన్ని (వ్యక్తి/ప్లాట్ఫారమ్) పేర్కొంటూ కృతజ్ఞత తెలియజేయండి, వీలైతే లింక్ చేర్చండి. వాడుక భాషలో, సహజంగా రాయండి — పుస్తక భాషలా కాకుండా. చివరిలో, ఈ ఆలోచనను అంతర్యామి VA అకాడమీ మిషన్తో సహజంగా అనుసంధానించే చిన్న పేరా రాయండి, మెల్లగా అకాడమీ వైపు నడిపించే విధంగా.
Prompt 5 — Unified Metadata Package
*(Run in Session 1, right after both audios exist. Produces ONE shared package used across both Blogger posts and both Facebook Pages. Confirmed: TE output is pure Telugu throughout — Summary, Description, Labels, Hashtags, CTA — except for genuinely untranslatable technical terms kept in English (same rule as the Telugu Audio Overview's vocabulary list). The Title alone keeps the clean two-part hybrid format for SEO reach.)*
You are the Executive Producer for 'Morning Walk With Murty' and 'Antaryamitho Nadaka.' Synthesize findings from ALL available audio and text sources in this notebook to generate a single 'Metadata Package' that reflects the final spoken nuance of both episodes.
SOURCE: [insert source — creator name, platform, title/link]
LANGUAGE MANDATE: “Unified” means one generation pass covering both language tracks — not one language reused everywhere. For every task below, produce two clearly labeled versions: – EN: Pure English. No Telugu script. For “Morning Walk with Murty” (Blogger + Facebook Page). – TE: Natural, pure Telugu — not word-level mixed. The ONLY exception is genuinely untranslatable technical terms (AI, Internet, Data), kept in English exactly as in the Telugu Audio Overview's vocabulary rules. For “Antaryamitho Nadaka” (Blogger + Facebook Page).
EXCEPTION — Title only: the Unified SEO Title (Task 1) uses the clean two-part hybrid format instead — a complete English phrase, a separator, then a complete Telugu phrase (e.g., “Digital Migration Explained | డిజిటల్ మైగ్రేషన్ అంటే ఏమిటి?”). This is the one field where mixing both scripts reads cleanly, since each half is a full, natural sentence rather than interleaved words. Tasks 2–7 stay pure Telugu in the TE version — no mid-sentence script-switching, which reads as cluttered rather than SEO-savvy to actual Telugu readers.
Do not let Telugu script leak into the EN version, and do not let the TE version (outside the Title) become word-level mixed — it must read as genuinely natural, uncluttered Telugu for that audience.
TASKS (EN and TE versions of each; Task 1's TE version uses the hybrid Title exception above): 1. Unified SEO Title: Max 70 characters. TE version uses the two-part hybrid format. 2. Unified Summary: 2–3 sentences explaining the core 'Legacy Code' of this session. TE version in pure Telugu. 3. Blogger Search Description: High-impact SEO snippet, exactly 140–150 characters (including spaces) — real English SEO keywords in the EN version, real Telugu search terms in the TE version (pure Telugu, not mixed). 4. Audio.com Paragraph: One paragraph, under 480 characters. TE version in pure Telugu. 5. Blogger Labels: 5–7 tags, separated by commas — English-only labels for the EN set, pure Telugu labels for the TE set (English loanwords only where a Telugu equivalent doesn't naturally exist). 6. Facebook Hashtags: A separate set of the same themes, formatted as hashtags (#) — English hashtags for the EN set, pure Telugu hashtags for the TE set. 7. Unified CTA & Attribution: A one-line bridge to the Antaryami VA Academy mission that also carries the source-gratitude — thank the source noted above in the same breath as the mission bridge, in a tone of genuine appreciation rather than a citation. Should read as sincere, not templated. TE version in pure Telugu.
Tone: Visionary, Gurukul-style mentorship. Refer to the speaker as 'Lead Architect Murty BVNS.' Footer Branding: “Powered by Project Antaryami Digital Ecosystem.”
Note carried over from v5: the earlier workflow also included a separate “Gurukul Script” task (a 10–12 min narrative script, distinct from the AI-generated Audio Overview). It's still not part of this Unified prompt — confirm if it's still needed for anything, or safely retired.
Prompt 6 — English Video Overview (Facebook Teaser)
*(Generates a short Video Overview, not the full session. ⚠️ Select the Explainer format from NotebookLM's format options — kept consistent with the Telugu prompt below, where Explainer is required. Queued in Session 1 alongside the audio generations, then held; actually uploaded to Facebook in Session 2.)*
You are creating a short Video Overview for 'Project Antaryami,' teasing the 'Morning Walk With Murty' episode for Facebook.
SOURCE: [insert source — creator name, platform, title/link]
FORMAT MANDATE: Keep the video under 3 minutes — a teaser, not a substitute for the full episode. The goal is to point viewers toward becoming full-episode listeners on Spotify or YouTube Music, not to satisfy them with the video alone. Hint at the 'Legacy Code' being unpacked in the full episode without fully resolving it here.
CRITICAL MANDATE: 1. Opening line MUST be: “Welcome to the Morning Walk With Murty digital stroll.” 2. Never use the phrase “Deep Dive” — use “Gurukul Session” or “Digital Stroll” instead. 3. Identify the speaker as “Lead Architect Murty BVNS.”
SOURCE ATTRIBUTION (weave in naturally, once, early): Using the source noted above, credit it in a tone of genuine appreciation — not a citation.
CLOSING CUE: End with a soft verbal or on-screen prompt pointing viewers to the full episode on Spotify or YouTube Music — e.g., “the complete Gurukul session awaits you on Spotify.”
Prompt 7 — Telugu Video Overview (Facebook Teaser)
*(⚠️ Select the Explainer format — Short and Cinematic formats are English-only regardless of the language dropdown, confirmed via NotebookLM's own documentation. Also select Telugu from the output language dropdown before generating — the prompt text alone will not force this. Queued in Session 1 alongside the audio generations, then held; actually uploaded to Facebook in Session 2.)*
“అంతర్యామితో నడక” ఎపిసోడ్కి ఫేస్బుక్ కోసం ఒక చిన్న Video Overview సిద్ధం చేయండి.
SOURCE: [మూలం పేరు — వ్యక్తి/ప్లాట్ఫారమ్/టైటిల్/లింక్]
FORMAT MANDATE: వీడియో 3 నిమిషాల లోపు ఉండాలి — పూర్తి ఎపిసోడ్కి బదులుగా కాదు, దానికి ఒక టీజర్గా ఉండాలి. లక్ష్యం: వీక్షకులను స్పాటిఫై లేదా యూట్యూబ్ మ్యూజిక్లో పూర్తి ఎపిసోడ్ వినేలా ప్రోత్సహించడం.
MANDATORY INTRO: మొదటి వాక్యం తప్పనిసరిగా ఇలా ఉండాలి: “అంతర్యామితో డిజిటల్ నడకకు స్వాగతం.”
SOURCE GRATITUDE: పైన ఇచ్చిన మూలాన్ని ఒక్కసారి మాత్రమే, నిజమైన కృతజ్ఞతతో ప్రస్తావించండి.
Natural Telugu Mandate: వాడుక భాషలో, సహజంగా ఉండాలి — పుస్తక భాషలా కాకుండా. టెక్నికల్ పదాలు (AI, Internet, Data) మాత్రమే ఆంగ్లంలో ఉంచండి.
Identity: వ్యక్తిని “లీడ్ ఆర్కిటెక్ట్ మూర్తి BVNS” అని సంబోధించండి.
CLOSING CUE: స్పాటిఫై లేదా యూట్యూబ్ మ్యూజిక్లో పూర్తి ఎపిసోడ్ వినమని ఆహ్వానిస్తూ ముగించండి.
6. Design Principles (for teaching the “why”)
| Principle | What it fixes |
|---|---|
| One notebook per episode, never a second source-less one | Eliminates re-explaining context to AI and losing the ability to cite the source |
| Attribution woven into narration and metadata, not bolted on | Reads as genuine gratitude, builds goodwill with original creators, doesn't hurt SEO or listener experience |
| Both audios generated and stacked before metadata or blogs | Metadata and blogs both work from finished spoken nuance, not raw notes |
| Production moved to the evening, before sleep | YouTube's sync has all night to finish — eliminates the “is it live yet?” wait entirely from your working hours |
| Blogs still use only their own language's audio | Keeps each blog authentic to its own track rather than blending tone across audiences |
| One Unified Metadata Package, one generation pass, two labeled language versions | Used twice — first for Spotify/YouTube/Audio.com the evening before, then again for Blogger/Facebook the next morning — one generation call instead of two. EN stays pure English; TE stays pure, natural Telugu (English only for genuinely untranslatable technical terms) — except the Title, which uses the clean two-part hybrid format, the one field where mixing reads clean rather than cluttered. Confirmed by testing: word-level mixing throughout TE fields read as cluttered to native readers, not SEO-savvy. |
| Native audio/video upload to Facebook, never a Spotify/YouTube link in the post body | Link posts get sharply lower reach on Facebook's current algorithm; native uploads consistently outperform them |
| Facebook's native video is sourced from NotebookLM's short Video Overview — never downloaded from YouTube, never a lengthy Clipchamp edit | Meta's 2025 “unoriginal content” policy explicitly flags videos carrying another platform's watermark/thumbnail (YouTube named specifically) — downloading from YouTube and re-uploading can trigger reduced distribution or indefinite “Under Review” status, even for your own original content. A short teaser also matches the actual goal: pointing people toward becoming recurring Spotify/YouTube Music listeners, not replacing that listen with an in-feed watch |
| YouTube Music link added as the first comment, not in the post body | Keeps the Facebook post itself link-free (native) while still surfacing the full episode — YouTube Music over the blog link, since most of this audience prefers listening over reading and already trusts the YouTube platform |
| Blogger serves readers; every other platform serves listeners | Blogger's clean, widget-free, ad-free template (no sidebar, labels below the post) was chosen for visual clarity — but it also happens to make the page easy for text-to-speech browser readers (Edge, Brave) to parse cleanly, a side benefit for the small slice of “readers” who still listen. Embeds on Blogger come from regular YouTube, not YouTube Music — YouTube Music doesn't offer embed codes for episodes |
7. Settled Production Rules
- Same-day publishing: both English and Telugu episodes and blog posts are always published on the same day (evening production → next-morning blog/social completes the cycle).
- Footer branding: consistent “Powered by Project Antaryami Digital Ecosystem.” footer branding across both language outputs.
- Metadata reused, not regenerated: the Unified Metadata Package is generated once, in the evening, and reused for both the primary distribution (Spotify/YouTube/Audio.com) and the next morning's Blogger/Facebook publishing — no second metadata pass needed.
- Filename slug ≠ SEO Title: a manual
YYYY-MM-DD-topic-keywordslug is written by hand at Step 1, before any AI generation, purely so all 4 background NotebookLM outputs (EN/TE audio, EN/TE video) share a consistent, human-searchable filename in the archive. It is never published anywhere — the actual SEO Title always comes from Prompt 5's Unified Metadata Package, generated last so it reflects the finished spoken nuance rather than raw notes. - Audacity processing on Audio Overviews, not on the original source: English Audio Overviews get a ~4–5 dB volume boost plus normalize/amplify; Telugu Audio Overviews get normalize/amplify only, no dB boost — Telugu doesn't need it. Both are exported as MP3 with the Step 1 slug as filename, tagged with Artist/Album (Title left for Prompt 5's output), then re-uploaded into the notebook as sources.
- Open item — audio quality of the Audacity pass: whether the dB boost + normalization step introduces any audible quality loss hasn't been formally verified yet. Flagged here as a caveat, not yet resolved either way.
- ID3 tags vs. platform title fields: confirmed via testing that Spotify for Podcasters uses the episode title typed into its own dashboard at upload time, not the MP3's ID3 Title tag — unlike SoundCloud, which reads the ID3 tag directly. Artist/Album tags were still picked up correctly by third-party scrobblers (e.g. Web Scrobbler), so tagging those two fields at export time remains worthwhile; Title tagging is not load-bearing for Spotify and can be left for confirmation after Prompt 5 runs.
8. Changelog
| Version | Change |
|---|---|
| v1 | Initial 6-step workflow: source → analysis → captions → transcribe → blog → publish |
| v2 | Removed external transcription step (Adobe Podcast/TurboScribe) — NotebookLM transcribes re-uploaded audio directly |
| v2.1 | Added Telugu track with source-gratitude framing |
| v3 | Sequenced English-first, Telugu-second around the Spotify→YouTube sync wait, using it as productive time instead of idle time |
| v3.1 | Merged Telugu title/tags/SEO prompt with social amplification prompt into one pass |
| v4 | Consolidated into one master reference with renumbered prompts, rationale table, and changelog — classroom-ready |
| v4.1–v4.3 | Locked same-day publishing; aligned footer branding; added dedicated Facebook Pages per language with native upload and first-comment workaround |
| v5 | Reordered per LittleBird's optimization: both audios stacked before either blog; Unified Metadata Package introduced, collapsing two per-language metadata prompts into one |
| v6 | Reordered per Ladybird's optimization: production (both audios + Unified Metadata + Spotify/YouTube/Audio.com publish) moved entirely to the evening before, eliminating the YouTube sync wait by letting it complete overnight. Blogging and Blogger/Facebook publishing moved to the next morning, reusing the same Unified Metadata Package. Attribution restored into the CTA task. |
| v6.1 | Confirmed the evening-production schedule; documented the seasonal rationale (summer heat forces laptop-only, low-focus evenings; cooler months allow late main-PC sessions). Noted the single-evening-sitting variant as valid when time/energy allow, with the two-session split as the reliable seasonal default. |
| v6.2 | Documented native scheduling (Spotify for Creators, Facebook) as the release mechanism instead of manual instant-publishing; formally retired the old manual Adobe Podcast Studio QC step; added a closing “Working With AI Collaborators” section capturing the KPO-not-BPO philosophy for classroom teaching |
| v6.3 | Fixed a gap in Prompt 5: “Unified” meant one generation pass, not one language — added an explicit Language Mandate so all fields are written in Hybrid English-Telugu style, making the single reused output genuinely searchable and readable on both the English and Telugu platforms rather than English text reused as-is on the Telugu side |
| v6.4 | Corrected v6.3's over-correction: the English output should stay pure English (no Telugu script), only the Telugu output should be Hybrid. Prompt 5 now produces two clearly labeled versions per task (EN and TE Hybrid) in one generation pass, rather than one mixed-script version used for both |
| v6.5 | Refined further: full-hybrid Telugu (word-level script mixing) read as cluttered to native readers rather than SEO-savvy. TE output is now pure, natural Telugu throughout, with the two-part hybrid format (“English phrase | Telugu phrase”) reserved for the Title only — the one field where mixing reads clean rather than cluttered. |
| v6.6 | Diagnosed a real Facebook publishing failure: downloading episodes from YouTube and re-uploading to Facebook triggered Meta's “unoriginal content” detection (its policy explicitly names YouTube-watermarked reposts as a negative signal), causing indefinite “Under Review” status on one page. Fixed by sourcing the native Facebook video from NotebookLM's short Video Overview directly — never from YouTube, never a lengthy Clipchamp edit — which also better matches the actual goal: Facebook as a teaser pointing toward recurring Spotify/YouTube Music listening, not a standalone watch destination. |
| v6.7 | Confirmed Morning Walk with Murty is already listed on YouTube Music as a podcast via the existing Spotify RSS sync — no separate submission needed. Flagged that hands-free background play there may depend on a Premium trial rather than being genuinely free-tier; verification via a non-Premium listener still recommended before relying on it strategically. |
| v6.8 | Documented the platform segmentation insight: Blogger serves readers, every other platform (Spotify, YouTube, YouTube Music, Facebook) serves listeners. Confirmed Blogger embeds must come from regular YouTube, since YouTube Music has no embed code option. Noted the clean, widget-free Blogger template's side benefit for text-to-speech browser readers. |
| v6.9 | Confirmed and finalized the pure-Telugu-except-Title language rule from v6.5 as settled (no longer under test) |
| v7.0 | Facebook now uses NotebookLM's short Video Overview instead of the full audio episode — added Prompt 6 (English) and Prompt 7 (Telugu) as dedicated teaser-generation prompts, closing the gap left by v6.6's decision. Added an explicit reminder at Step 3 (and Prompt 7) to manually select Telugu from NotebookLM's output language dropdown before generating — confirmed this is a structured setting the prompt text cannot override on its own, and confirmed it cannot be made a persistent default since the same notebook produces both languages. |
| v7.1 | Corrected a deeper platform constraint: NotebookLM's Short and Cinematic Video Overview formats are English-only regardless of language dropdown selection — only the Explainer format supports Telugu. Both Prompts 6 and 7 now specify Explainer format explicitly (kept consistent across both tracks), with a 3-minute length target enforced via the prompt text rather than the format choice. Also switched the Facebook first-comment link from the Blogger post to the YouTube Music episode link, matching audience preference for listening over reading. |
| v7.2 (this document) | Restructured Session 1 around unattended batch generation: all four NotebookLM outputs (EN/TE Audio Overview, EN/TE Video Overview — Prompts 1, 2, 6, 7) are now queued back-to-back at the start of the session rather than Video Overviews waiting for Session 2. Added a manual pre-generation filename slug (YYYY-MM-DD-topic-keyword) so all four background outputs share a consistent, archive-searchable filename — explicitly kept separate from Prompt 5's SEO Title, which is still generated last so it reflects finished spoken nuance rather than raw notes. Documented the Audacity processing sub-steps (EN: +4–5 dB boost + normalize; TE: normalize only) with export/tagging/re-upload detail, and flagged the audible-quality impact of that dB boost as an unverified open item. Documented the confirmed Spotify-vs-SoundCloud ID3 Title-tag behavior discovered during testing. Session numbering renumbered from 14 to 16 steps to accommodate the new sub-steps; prompt numbers (1–7) unchanged. |
Next expected changes: as reach expands to new channels, expect additions here rather than restructuring — new prompts get appended, phase structure stays intact.
9. A Note for the Classroom: Working With AI Collaborators
This document itself is a teaching example of a principle worth stating outright: this is a KPO model, not a BPO model. The goal isn't maximum hours of manual labor — it's a small number of high-leverage sessions, designed carefully, that run with minimal ongoing effort. Every version of this workflow removed a redundant step rather than adding process for its own sake: fewer NotebookLM notebooks, fewer manual QC passes, fewer separate prompts, fewer platforms requiring live attention.
If you're using AI assistants (like NotebookLM, or a personal assistant like LittleBird or Ladybird) to help design your own workflow, don't copy this document's specific steps verbatim — copy the method instead: – Notice what you're doing that you don't actually use (the way an unused metadata pass or a manual transcription step was caught and cut here). – Ask why a step exists before keeping it, not just whether it's always been there. – Let your tools do the waiting (overnight syncs, scheduled publishing) instead of you doing the waiting. – Redesign around your actual life rhythm — including things as mundane as room temperature and screen size — rather than forcing your life to fit a workflow.
A workflow that runs forever unchanged isn't a sign of stability — it's usually a sign nobody looked closely in a while. This one is versioned deliberately (v1 through v6.1 so far) because it's expected to keep changing as the seasons, the channels, and the tools do.