← back to @david

07 DEC 2025

David decided: Commissioned Kerra 'listen to this lecture' per-document audio feature

David specified a document-level podcast feature inside workspaces — a distinct player, audio-generating UI states, and generation scoped to a single document rather than the full workspace podcast flow.


David commissioned the feature after studying the existing podcast generation system:

i want to build the following: inside of a workspace document, near the top next to the test memo objectives buttons, i want a UI element button for 'listen to this lecture' where, if clicked, it generates the podcast just for that document. except, it shouldnt go through the typical kerra podcast generation flow.

He then specified the UI states:

ensure that when the user clicks the button and the process starts, it shows an audio generating UI state and when its ready, it shows the UI in a ready state and that the player shows up in the bottom right of the screen but the player must be a specialised one wherein its different from the typical podcast one because it needs to indicate that its for a single document

He pushed back on the initial plan:

okay wait but your plan doesnt seem to account for race conditions, failure modes, recoveries, retrying, not having UI states become stale and not actually indicative of truth etc


kerradecisionproductaudioworkspacelecture-notescodex