"The first variant takes a complete audio transcript of a meeting and transcribes it and eventually returns an output. In our case, however, the output is not a summary. Instead, the output is a collection of saved items. It includes any items explicitly referenced during the conversation. It also includes any items from a user's collection of saved things that are meaningfully close to the topics of the discussion. Essentially, the audio is a token stream used to query a collection of saved items for similarly meaningful things.

The second builds on the first. But instead of a single capture-query-response-compile-surface loop, there's many. The audio is converted to a query in real-time, as it's being captured. The results are immediately surfaced to the user who leverages them however they please—perhaps sharing them, perhaps using them to inform part of their own dialogue or parse the ideas of another, perhaps marking them for deeper investigation later."

"The first variant takes a complete audio transcript of a meeting and transcribes it and eventually returns an output. In our case, however, the output is not a summary. Instead, the output is a collection of saved items. It includes any items explicitly referenced during the conversation. It also includes any items from a user's collection of saved things that are meaningfully close to the topics of the discussion. Essentially, the audio is a token stream used to query a collection of saved items for similarly meaningful things.

The second builds on the first. But instead of a single capture-query-response-compile-surface loop, there's many. The audio is converted to a query in real-time, as it's being captured. The results are immediately surfaced to the user who leverages them however they please—perhaps sharing them, perhaps using them to inform part of their own dialogue or parse the ideas of another, perhaps marking them for deeper investigation later."
https://paragraph.xyz/@subset/my-archivist