SAO wiki / How This All Works / Adrian & the voice channel
Drill-down ยท 01
How speech gets into the system โ and why talking to the house is the same as typing into a session.
Adrian is the home assistant. Adrian sits on top of the home stack and belongs to the house โ hard-placed, deliberately. Where the rest of the system treats every agent as movable across harnesses, Adrian is the exception: a fixed point that knows the home. What keeps that from becoming a silo is the other half of the design โ Adrian doesn't do the company's work, Adrian summons the ones who do, and it can summon a conductor on any harness.
Whole-house coverage comes from two small pieces of hardware: a DJI mic that travels with Scott and a belt speaker that answers back. That's the entire rig. There is no "voice mode" with a session timer on it, because there is no session: a raw transcription of the house runs 24/7, and the conductors parse it. Speech doesn't open a context window that later runs out โ it lands in a stream that is already flowing.
Routing is done by name, out loud:
So you don't have to know the org chart to talk to it. Address someone if you have someone in mind; otherwise the words go to whoever holds the watch.
The channel borrows CB-radio semantics because they solve the two hard problems of talking to a machine โ when have you finished a thought, and when have you finished a conversation:
Nothing special happens to speech once it's routed โ and that's the point. The conductor takes the conversation and does exactly what it does with anything else on its desk: it delegates the work to an existing supervisor, or spawns a new one. Voice enters the same lattice as text. A sentence said while walking down the hallway ends up in the same place as a typed instruction: with an agent that owns it, on the record, moving.
Up: How This All Works โ the human guide ยท Start: the SAO wiki