Short answer: when a Python pipeline sends podcast transcripts to a vector index, store speaker , start_time , and episode_id beside every chunk, and never let a chunk cross a speaker-turn boundary. That gives retrieval enough structure to answer “what did Maya say?”, gives the player a precise timestamp at which to resume, and lets an ingest worker replace one episode without disturbing the rest of the corpus. Treat chunking as an operational contract, not a tokenizer setting. The decid...