A spell engine composes explicit runic graphs over the same magical semantics used by live casting. Enchanting and Wands binds effect graphs into persistent artifacts. Exact automation control-flow structure remains prototype work rather than silently becoming a third source language.
Automation follows the same authority as manual work. It cannot create matter, ignore custody, reach through a missing route, perform an unknown practice, or repair an invalid output after the fact. A manual action, scheduled process, imported blueprint, and background continuation all use the same commit primitive.
Progression
Early automation repeats one demonstrated operation. Later systems sense conditions, select admitted substitutions, route outputs, coordinate facilities, pause on unsafe state, and publish useful signals. Complexity buys expressive capability, not exemption from material constraints.
The interface exposes inputs, outputs, capacity, ownership, current step, failure state, and provenance. Players should be able to understand why a machine is waiting without reading a private implementation log. Exact rune catalogues, quantitative operator semantics, and simulation granularity remain prototype work.