Coven

In plain words: Model Groups

Available 1 min read 5 glossary terms 7 connected pages
The short version written for the Snayu team

Explains Model Groups (Covens): a named systemd target for two or more compatible local model services. Grouping is a convenience; hardware conflicts are declared separately.

Why read it: Read this when grouping local models or debugging which models can run together.
  1. 1Membership comes from the groups field; conflicts come from conflict_domains.
  2. 2A group with internally conflicting members fails closed.
  3. 3Starting a group target directly bypasses the Stage Manager; reserve it for recovery.

Available Declared conflict topology and target switching are Available.

Words on this page, decoded click one for its card

Stage ManagerLocal ModelModel Group
Where it sits in LychD

Model Group Coven

A named group of local model servers you can start or stop together.

It's like: A light switch that controls a whole room.

Click a dot to open that part's card.

Glossary page In the network
The original text Underlined words open their plain-English card.

Under one name, the CovenModel Group gathers its fires.

Use a CovenModel Group to give compatible local services one operator name. When two or more Soulstones share a group, binding emits a named systemd target for them. A SoulstoneLocal Model requests membership through groups. It declares hardware incompatibility separately through [concurrency].conflict_domains; grouping services cannot decide which ones may coexist or be evicted.

One member emits no target. Different groups create no coexistence promise. Members' effective conflict sets must not overlap; an internally conflicting CovenModel Group fails closed. The current RuneService Config File schema has no alliances setting and rejects that field.

One RuneService Config File may participate in more than one formation:

name = "echo"
groups = ["conversation", "studio"]

That still names one service instance. Starting lychd-coven-conversation.target and lychd-coven-studio.target does not create two copies, and common membership does not prove the complete union fits. The compiled conflict graph remains the executable coexistence law.

The later capability and resource design would let a CapabilitySetRequest@1 use that name as an operator convenience. OrchestratorStage Manager would first expand it and validate every member against measured envelopes and placement profiles. Membership itself supplies no resources, routing, lease, or egress authority. Even a serialized convergence has non-atomic physical effects: partial change still needs compensation, restoration, and containment.

Operator break-glass surface

Starting or stopping a generated CovenModel Group target directly propagates through its compatible AnimatorModel Runtime targets. This bypasses OrchestratorStage Manager admission, lease drain, stale-world validation, readiness, and compensation. Reserve it for host administration or recovery.

For inspection, activation requests, priority, switching settings, and Reactor outcome recovery, continue to Runtime transitions. The old operation fragments remain here so existing links still find that passage.