Solo podcast source package: one excerpt, three linked files and an explicit lineage Inspect a real public podcast excerpt alongside its automatic transcript and VTT cues. The package illustrates source-to-derivative relationships without claiming three independent recordings. Inspect a real public podcast excerpt alongside its automatic transcript and VTT cues. The package illustrates source-to-derivative relationships without claiming three independent recordings. Underlying source One public solo excerpt Package roles MP3 + automatic TXT + VTT cues Archive inventory Not established by this reference The exact public reference and evidence state Inspect a real public podcast excerpt alongside its automatic transcript and VTT cues. The package illustrates source-to-derivative relationships without claiming three independent recordings. These files were already published on Fiund’s specialist websites as owner-authorized editorial media. This study documents the exact public reference and its limits. It does not advertise an accepted commercial training collection, grant downstream use rights or establish permissions for every person or contribution depicted. Use the [measured reference manifest](https://podcastdatasets.com/downloads/solo-podcast-source-package-manifest.json) to inspect the delivered filenames, measured properties and SHA-256 values. The manifest identifies this small public reference; it does not describe the size of an uninspected private archive. A package manifest preserves the relationship between files This public reference has three roles: the playable MP3 excerpt, a text transcript and timed display cues. The audio file is 162,360 bytes and measures 13.525333 seconds. Text and cues describe that same excerpt; they are not additional audio coverage. The public manifest records separate checksums for each role. That makes it possible to notice a changed transcript or a recompressed audio export without assuming all files still describe the same version. The same public excerpt studied by AIPodcast. It is one underlying recording reference, not new archive inventory. File role Public path Identity check jaeden-ai-chat-excerpt.mp3 /media/jaeden-ai-chat-excerpt.mp3 SHA-256 recorded in manifest public-solo-excerpt-transcript.txt /downloads/public-solo-excerpt-transcript.txt SHA-256 recorded in manifest public-solo-excerpt-cues.vtt /downloads/public-solo-excerpt-cues.vtt SHA-256 recorded in manifest An excerpt is not an episode, a session or an archive An archive can contain source sessions, edited episodes, short clips, alternate exports and transcript editions. The public reference covers one short excerpt only. It does not quantify how many full episodes exist, which source sessions they share or which originals retain separate microphone tracks. Counting transcript files as audio hours, treating a clip as a complete episode or adding multiple derivatives together would overstate unique material. Keep the source-session, episode and derivative levels visible when evaluating a larger podcast collection. What needs reconciliation in an actual archive selection For a real project, identify the selected episode edition, the source recording if available, and any removed or inserted material. Record which transcript corresponds to the edited audio and whether captions were generated automatically or reviewed. Host participation, guest contributions, music and other third-party material are separate evidence questions. The fact that an episode was publicly distributed does not itself establish AI-training permissions. The anonymous Swedish archive brief on this site illustrates why guest exclusions and buyer-specific approval belong in the source selection. Keep original sessions and published episode editions distinguishable. Do not label a public compressed mix as isolated participant tracks. Version transcript and cue files alongside the audio they describe. Reconcile permitted use and excluded contributions before a commercial delivery. From the reference to a real project A useful project request starts with the actual task and the evidence it needs. Ask which source units, permissions, annotations and review steps would be required for your application rather than assuming that a public example establishes inventory. The public manifest can be used to reconcile file identity. A matching checksum means the bytes match that reference; it does not establish source ownership, consent, completeness, annotation accuracy or fitness for a model task. Those questions need their own evidence. Contact Fiund with the desired source characteristics and the decision your model must make. Confirm sample access, source scope, preparation and commercial terms for the selected project before making a larger collection or delivery commitment. Is this an immediately licensable training dataset? No. This page documents a real public editorial reference. The public files and their measurements do not establish commercial training clearance or a larger available archive. What can the manifest establish? It records the published reference files and measured properties. Its SHA-256 values support byte-identity checks, while provenance, permissions, accepted scope and annotation decisions require separate evidence. Research method: Fiund research desk; public sources, explicit worked-example labels and project-specific availability review. Editorial contact: hello@fiund.com. Sources Measured public reference manifest: https://podcastdatasets.com/downloads/solo-podcast-source-package-manifest.json Podcast Studio AZ public recording context: https://www.podcaststudioaz.com/