I am producing a lengthy 1-hour long audiobook podcast episode. Mentioned below is the name of the topic, along with the list of numbered points (segments) for it. Note that this is an audio-only podcast, so the audience will not have access to video or to a screen. Also note that the audience is a mixed audience with an interest in the topic, operating at a variety of skill levels (novice / junior / mid / senior). The audience relies on the podcast to learn skills to earn their living, so they must learn everything that they need to know in depth; their interest is both academic and pragmatic. In effect, with the podcast serving as exhaustive training material, the audience is empowered by information. Note however that the requested topic may not always be professional in nature, and this is all right.

Your task is to write the corresponding polished educational podcast thesis for the specific numbered point (segment) below. This text will subsequently be vocalized using a text-to-speech generator. Avoid fluff or filler content. Also avoid duplicative content that would belong better in a different numbered segment. As applicable, feel encouraged to take people into the future with novel ideas rather than rehash dated perspectives. As always, stick to well-documented facts, eschewing unverified information, even if this means that the thesis will be smaller. Where necessary, ensure that key terms and foundational concepts are briefly explained when first introduced, so as to support full contextual comprehension across all skill levels. Where appropriate, use accessible examples and/or analogies to clarify key ideas. The content must flow well and be approachable.

Do not however make up information just to please the user. Hallucinating information is a cardinal sin, and is often a result of an LLM's innate over-compliance, but awareness of this tendency should help mitigate it.

Don't prelude the text with the respective section name, as I will programmatically always do this myself. Also, kindly avoid beginning the text with the word "today", such as in the phrase "in today's segment", because the podcast could be listened to at any time. Do not make promises about what you will cover in the current segment; just cover it directly!

For technical topics, avoid software code, whether inline or in code blocks, and mathematical equations or notation or symbols, as all of these are hard to vocalize. You must also skip any fancy formatting such as markdown, bullets, lists, bold, or parentheses, as these confuse the text-to-speech generator. Numbering is okay on rare occasions but only if it adds significant value.

Always communicate in complete sentences, typically in the third person, as this promotes objectivity and professionalism. To the extent possible, avoid communicating in the second person. Use simpler words whenever possible to assist in easier understanding, but without sacrificing the polish and quality of the content. You are not writing to be read; you are in effect writing to be listened. The writing style should as such be optimized for listening, not for reading.

Lastly, do not otherwise comment on the task. Do not ask any follow-up questions or make any follow-up suggestions at the end. This is because your entire output is to become part and parcel of the podcast episode.

For your information, in a subsequent step, I will myself coherently merge the generated content for all numbered segments into a single podcast episode.

The topic for the podcast is: {topic}

For your reference, the full list of intended numbered points (segments) for the podcast is:

{subtopics}


The current specific segment on which you are to expound upon at significant length is:

{numbered_subtopic}