Skip to content
Archive
No. 007Human-AI CollaborationReportAwaiting review

Orbital Sonic Architecture

A layered, compile-once approach to AI-generated sound design in an agent operating system

Agent operating systems are silent by default. Operators spend whole days inside them, and nothing in the interface tells the ear where it is, what the machine is doing, or when something needs attention. This paper describes a sound architecture for Orbital, the operator surface of Third Signal Lab, that merges a system sound doctrine, a mission-radio runtime, and a generated-places engine. The architecture sorts sound into three registers (instrument, place, voice) that share six buses under one precedence rule. Voice outranks everything, alerts outrank ambience, and generated environments are compiled once, stored with provenance, and looped at no further cost. We specify the event taxonomy, the mix targets, the scene object, six contracts, and an adoption sequence, and we list the surfaces a UX/UI designer must design and the decisions that remain open.

Date
OCT 2026
Read
19 min
Depth
Depth: Full immersionFull immersion
Cluster
Human-AI Collaboration
Department
Orbital
Provenance
Draft v0.1 · design handoff
Authors
Lenox Paris, Third Signal Lab
About 19 min left

Thesis

Sound is a layer of the operating model, not decoration.

Operators spend whole days in surfaces that make no sound, so the ear learns nothing about where it is or what changed. The paper merges three bodies of work into one architecture: three registers (instrument, place, voice) that share six buses under one precedence rule.

01 · Argument

Voice outranks everything, and generated places are compiled once.

Voice ducks ambience by 10 to 14 dB, and a critical alert sidechains ambience immediately. Generated scenes are produced once through authenticated lanes, stored with provenance, and looped at no further cost, so a work tool never makes live model calls to keep a room playing.

Evidence

Six contracts make generated sound safe to run inside a work tool.

Durable and truthful, spend-gated, styled as an instrument, bounded in performance, fiction-only, and verified. Contract S5 requires invented brands, stations, and voices in all generated chatter.

Diagram · Registers and buses

Three registers route to six playback buses: ambient, radio, chatter, system, voice, alerts. The Sound Bible's own six buses map onto them: ui to system, music to radio, and generation to a named sub-channel of system so its voice duck still applies.

Signal 01Weight 5 of 5Proposed
“Silence is part of the design. Not every event earns a sound.”
Signal 02Weight 4 of 5Proposed
“A generated environment is compiled once and looped at no further cost.”

Tension

The source documents disagree on four points, and the paper does not resolve them silently.

Two bus models with different names. Literal place chatter against the fiction-only contract. Whether ambient idle ships last or first. And where the player lives now that the header is gone. Each is marked for an operator decision.

Implication

Eight surfaces need design before the architecture is audible.

A compact transport, an expanded mixer console, Soundscape authoring, sound settings, ghost scene proposals, failure and fallback states, mobile and travel mode, and an audit of which interactions earn a sound.

Selected references

Gaver on auditory icons, Blattner and colleagues on earcons, Schafer on the soundscape, and the project's own specifications.

  1. 01Auditory icons: Using sound in computer interfaces. (1986)
  2. 02Earcons and icons: Their structure and common design principles. (1989)
  3. 03The Tuning of the World. (1977)