Why simply saving conversations wasn't enough for me

In VoxBase I was solving the problem of what happens after a conversation.

A recording becomes text, the text is saved as Markdown, and the important information stays in project memory. You can come back to a conversation a day or a month later without trying to reconstruct it from recollection.

But another problem showed up fairly quickly.

Sometimes context isn’t needed after the call. It’s needed right now.

During a conversation someone may ask about something discussed a week ago. A new objection may come up, the topic may shift, or a specific project fact may be needed.

And the information already exists: it sits in Obsidian, in documents, in project rules, in past conversations.

The only problem is that searching for it by hand while the other person waits for an answer is almost pointless.

That’s how LiveContext appeared.

Its job is broader than ordinary transcription. The system has to receive the conversation practically in real time, understand what is happening now, and connect what’s happening to the context of a specific project.

Roughly:

conversation
↓
transcription
↓
current state of the conversation
↓
project context
↓
the information needed

So VoxBase saves a conversation into memory.

And LiveContext tries to make that memory work before the conversation has even ended

In the next posts I’ll go through how I put this together: from two independent audio streams and local transcription to Obsidian and finding the right context during a call.