Soulstone Engines
An engine is an upstream execution substrate that a Soulstone adapter can bind into a local Animator. It is not itself a Soulstone, a model, or a semantic extension.
engine + adapter + Rune + Quadlet + resources = one local Soulstone instance
The engine pages own runtime-specific launch shape, connector dialect, readiness and activation, resource placement, containment, and evidence. Choose an engine below for that adapter's requirements, then use the common Soulstone contract to bind its local instance, admit work through Dispatcher, and request Orchestrator transitions. Each engine page states its delivery boundary; an entry in this map does not establish a delivered adapter.
| Engine | Primary shape | Use |
|---|---|---|
| vLLM | resident OpenAI-compatible model server | Kinetic model serving |
| SGLang | resident OpenAI-compatible model server | Radix model serving |
| llama.cpp | single-model server or in-process router | Titan model serving and dynamic activation |
| ExLlamaV3 through TabbyAPI | dynamically activated model service | strict TabbyAPI-backed model serving |
| ComfyUI | queued graph/workflow engine | image, video, spatial, and exact audio-capable profiles |
| audio.cpp | audio inference with an independently managed service or worker lifecycle | bounded music, separation, and speech profiles |
The same engine may manifest several Soulstones with different model sets, graphs, GPUs, conflict
domains, and capability profiles. comfy-qwen, comfy-ltx, and comfy-music3, for example, may
use one ComfyUI image while remaining separate managed service instances.
Models and workflow graphs are not universal engine facts. An exact model, graph, node set, quantization, license, and hardware placement become a capability profile only after the selected engine adapter and the owning extension or Composition have admitted them.
Engine versus technical contract and semantic owner
The engine performs a bounded execution. Choose the technical contract and consuming owner for each returned facet:
| Returned facet | Continue to |
|---|---|
| image, video, visual observation, spatial form, or structured motion | Prism for the exact technical interface and Atelier or another named consuming Composition for adoption |
| speech transcription, synthesis, cloning, or delivery | Echo and the requesting owner |
| music, musical vocal, production effect, or musical cue map | Riffmaw |
| timed-language dialogue, narration, or caption edition | Language Edition, using its exact Echo and Translation operations |
| picture-bound effect, foley, room tone, or ambience | Broadcast |
| game-event, state, space, listener, or runtime sound | Foundry |
| final audiovisual assembly | Broadcast's pinned renderer and timeline |
Prism settles technical results, Core owns any ServiceJobAttempt@1, and each consuming owner
independently admits its facet. For model-native video with sound, follow
compound-facet admission before
selecting the profile.
An engine that can emit more than one modality does not absorb those domains. The exact Rune and capability profile determine which operations may execute; each application facet still needs its own semantic admission receipt.