Audio events keep their identity after restart
Five saved events across two listener launches demonstrated distinct runtime-based event IDs.
Record date Oct 1, 2026 · Published
A sequence number by itself could not identify an audio event across listener restarts: every new process began again at one. The V1.6 listener now pairs a fresh runtime UUID with that local counter.
The updated listener compiled on the Pi. The first launch saved four identity-bearing events; a second launch saved another event with a different runtime UUID and sequence one. All five observed event IDs were distinct.
The test also preserved a long conversational thought as one event. Proper-name recognition remained imperfect, and the result does not establish general transcription accuracy.
This is a tested identity checkpoint across two process launches. Crash recovery, write-failure handling, durable power-loss storage, deduplication, and downstream cognition integration remain separate qualification work.