The v2 archive adds a substantial voice-system blueprint dated around July 2026. It belongs in the Lab because it is not just speech-to-text plus text-to-speech. It is another attempt to turn local AI interaction into an operating environment with state, identity and timing.

01 – Purpose

The system is framed around real-time multi-speaker interaction.

The core problem is that ordinary voice assistants flatten conversation into a request/response exchange. A multi-speaker system needs to track who is speaking, who is being addressed, whether speech is partial or complete, and whether the assistant should interrupt, wait, revise or speak.

That makes it closely related to Omega's attention problem.

02 – Architecture

Recovered components include:

live audio input;
speech recognition;
speaker identity states;
thought assembly;
revision engine;
playback as a stateful object;
local inference/chat layer;
integration with broader local AI workstation tooling.

The interesting part is not any single component. It is the way they are treated as stateful parts of an ongoing interaction rather than one-shot function calls.

03 – Speaker Identity States

The system distinguishes speaker state instead of treating all audio as anonymous input.

That implies the assistant has to reason about:

current speaker;
possible speaker changes;
overlapping or interrupted turns;
conversational address;
whether a response is intended for one person or the room.

This moves the work toward a conversation operating system rather than a voice command layer.

04 – Thought Assembly And Revision

The recovered notes mention thought assembly and a revision engine.

That matters because live conversation is incremental. A system may begin forming a response before the full utterance is settled, then revise as more context arrives.

In a text chat, revision mostly happens before output. In voice, timing itself becomes part of the intelligence.

05 – Playback As State

Playback is treated as a stateful object, not just "say this string."

That allows questions like:

Is the system already speaking?
Can this output be interrupted?
Should speech be revised?
Should it pause, resume or abandon a response?
Does a new user turn outrank the current playback?

This is directly adjacent to attention and control policy.

06 – Current Status

The archive records this as a technical blueprint v0.1 with implementation status still to verify. The Lab should publish it as design archaeology unless code or demos are confirmed.

Source note: assembled from v2 section 31, "Real-Time Multi-Speaker Voice Interaction System." Implementation status should be checked before presenting it as built.