audio.cpp
Consider audio.cpp when a bounded local audio operation needs an inference engine. A pinned server or worker may justify a Soulstone and local Animator. The meaning of its output still belongs to the consuming owner: Echo for speech mechanics, Riffmaw for music, or another application according to the admitted operation and semantic role.
The candidate study concerns music, separation, and speech families supported by an exact pinned runtime profile; it does not admit arbitrary model execution merely because the runtime is Apache-2.0. Model weights, dependencies, family support, input/output bytes, and license terms remain separate profile facts.
To admit an audio.cpp Soulstone, first pin how it will run: runtime revision, model family,
worker or server shape, queue and lifecycle behavior, and device topology. Then establish the
audio formats, cancellation boundary, output custody, and measured receipt. If a library or
one-shot CLI needs no independently managed lifecycle, keep it in a bounded ToolProfile
instead.
The music candidate is recorded in Riffmaw Studio; speech law and Language Edition's use of exact STT/TTS operations remain in the Audio covenant and Language Edition. Audio admission remains separate from the generic Soulstone engine catalog.
See audio.cpp and the owning Echo, Riffmaw, and role-specific application contracts.