Skip to content

Animator

Follow the spark to where the iron answers.

A workflow may need a model to answer, a search service to find material, or a renderer to draw. The Animator gives LychD an addressable handle for discovering, probing, and invoking that service's typed capabilities. A model is one possible source of power; independently managed search, rendering, or speech services can supply others. The handle says where a capability can answer. The service's deployment manifest and the application's purpose belong elsewhere.

Two Sources of Power

Source What the operator declares What LychD can control
Soulstone, The Furnace of Animus Local Rune, rootless Podman/Quadlet service, models or profiles, devices, mounts, secrets, and lifecycle. Admitted local service and supported runtime-native transitions.
Portal, The Rift to the Remote Sky Remote endpoint, provider contract, explicit models or profiles, and credential reference. Its own admitted connection; no provider start, stop, repair, or local VRAM.

Portal Roads selects a remote custody and economic road. Audio hardware and host routes handles device attachments; a raw device or finite host helper does not become an Animator merely because its work uses audio.

The Holy Contract

Check what the service declares, what its bound surface has proved, and what is ready now. Capabilities keeps those records distinct: a probe may invalidate a declaration, but cannot invent a capability.

Adapters keep native protocols behind the stable surface requested by Graph or an extension. An Animator-backed web effect still needs Scout's separate grant, destination, budget, and receipt.

The Galvanic Arc

typed demand → declared eligible profile → current observation
  ├─ WARM and admitted → exact grant and lease → invocation → owned return
  └─ managed but cold → handle-free transition → readiness → dispatch again

If the service is ready and the request is admitted, Dispatcher supplies the grant and lease. If a managed service must change first, Orchestrator performs the admissible physical or runtime-native transition. The waiting Graph keeps neither Connector nor lease while readiness converges, then returns to dispatch. Current implementation performs this handshake for the narrower v1 family/model demand and chat-model/toolset compatibility grant.

Animus: the power answering

Animus names the power answering through an admitted, active capability. A loaded model—Gemma behind llama.cpp—is its clearest instance. The term creates no new runtime object. Orchestrator owns activation; the Animator is the address, the Connector its conduit, and the CapabilityGrant the exact permission and lease.

A Spell shapes that draw into a typed request. The return becomes candidate material for the Circle: Blade discriminates, Spirit carries it in Flux, and Answer binds the act locally. Inference alone supplies neither Persona, identity, memory, authority, nor operational Cognizance.

Capability and Readiness

Use Capabilities to name the required operation and interpret its grant or refusal. Use Connectors to bind its exact dialect. For compatible local groups, enter Coven; to inspect or request a change, follow Runtime transitions. State of Work owns what each route proves.

Contribute an Animator

To add a managed or remote capability source, register its typed Soulstone or Portal definition with the receiving store in ExtensionRegistrationContext. The built-in Animator registration and its runtime packages show how schemas and adapters are assembled. Test the declared profiles, connector behavior, and readiness and grant boundaries that the contribution implements; the Crypt vertical test traces a private contribution through adapter and Dispatcher contracts. Lifecycle covers selection and restart.

Keep observations with the contributed component. The registration context accepts bounded observation declarations and immutable inspection contributions; these stores do not themselves register execution. Oculus owns the common and external source contract.