When you need more control.

For normal gameplay, keep a Sound Manager in the scene and use SoundBus with your generated Sounds keys. You do not need a custom service to make any of the ten demos.

These pages are for a custom host, a test harness, dynamic content registration, or an editor diagnostic tool. They explain the same runtime used by the scene component.

Task	Reference	Existing example to understand first
Register or remove content and drive updates	Service lifecycle and catalogue	Manager setup and keys
Provide timing or another audio implementation	Clock and voice backend	Bee following a moving source
Inspect a running graph without issuing commands	Definitions, states, and traces	Arcade limits
Read parameter declarations and allowed assets	Parameter records	Jukebox allowed tracks

All service integration belongs on Unity’s main thread. A handle is tied to the service session that created it. A backend owns voices; it does not replace the graph scheduler’s ownership, concurrency, signal, and notification rules.

The coverage inventory distinguishes documented integration APIs from editor/compiler implementation types. Public visibility alone does not make an internal compiler record a recommended gameplay API.