A voice bot needs a good silence

Notebook principle 03: make the quiet parts of an AI system understandable.

I want the voice interface to communicate its state before it asks anyone to trust its answer. These are design principles and proposed checks, not completed Mosaico device results.

For the voice work in this notebook, I want to judge more than the answer. A voice bot has several jobs before it says anything useful. It must make clear whether the microphone is active, whether it heard the request, and whether a response is on its way. Those signals matter even more on a small desk device.

Name the states

Muted. Ready. Listening. Thinking. Speaking. Disconnected. These are different conditions, and a person should not have to infer them from a decorative animation. Colour can help, but text or a recognisable symbol should carry the meaning too.

Interruptions are normal

One check I want future voice build logs to document is an interrupted response. Does playback stop? Does the next request start cleanly? What happens if the connection drops during a sentence? These are proposed checks for the Mosaico voice path, not completed device results.

Make the quiet default legible

A muted microphone should stay visibly muted. A device that is waiting should not look as if it is secretly working. A slow answer should have a truthful status, and a failed request should have an obvious way to try again.

The goal is a small interface with very little mystery. The model can be complicated. The controls should not be.