Confidently wrong: when silence is worse than an error

A denied permission didn’t throw an error. It returned silence — so the app confidently attributed a whole meeting to one person.

One of the worst bugs I have hit did not announce itself at all. That was the problem.

To record both sides of a call, Jiva needs permission to capture system audio. On one path, when that permission was effectively not granted, the system did not return an error. It returned silence — a valid, empty audio stream. So the app carried on happily, heard only my microphone, and attributed the entire two-person meeting to me. No crash, no warning. Just a confident, complete-looking transcript that was quietly half the conversation.

Note that this is the same disease as the four-speaker bug, in a different place. The machine was sure of itself and wrong, and its confidence gave me no signal that anything had failed. An error I can catch. Silence that looks like data, I cannot — unless I go looking for it.

The fix was not to make the transcript more accurate, rather to teach the app to notice the absence and say so. Jiva now detects a dead channel and tells you plainly that it only heard your side, instead of pretending it heard everything. The primary driver here is not cleverness, it is honesty: an assistant that says “I only got half of this” is far more useful than one that is smoothly, silently wrong.

I keep coming back to this because it is the whole game with a memory product. The value is trust, and trust does not come from being right every time — nothing is. It comes from being honest about the times it is not.

More soon.