The Spellweaver
A Spell gives one station its action. The Spellweaver keeps the Scroll through motion, pause, and return.
An Agent call, Gate, tool, effect, wait, or delegation may warrant an independently named semantic
action: a Spell. One Scroll-local station places that Spell's exact contract. The whole
immutable Pattern revision is its Scroll. Spellweaver is LychD's singular logical workflow
jurisdiction: it validates Scrolls and admits their casting through execution, pause, return, and
ending. Weaver remains the short name used by code and existing paths.
Future packages may contribute Spell contracts and Scroll declarations through separate Spellweaver-shaped stores. Executable implementations and adapters remain separate Extension or effect-owner registrations; publication and activation are not implied by contribution. The Core office retains workflow authority. Spellweaver never inherits the policy or physical control of the offices it sequences. ADR 28 owns the complete contract.
From Product to performance
These identities keep packaging, domain truth, score, performance, and ledger distinct:
- Product names the professional or market package and its supported use cases; it grants no member authority.
- Composition owns reusable application records, judgment, policy, effects, and outcomes.
- Pattern is one named executable-score lineage owned by that Composition; one immutable revision is a Scroll.
- Spell is one independently named semantic action contract; a station places it in that Scroll.
- Invocation opens one bounded Circle.
- Casting performs the exact Scroll inside that Invocation.
- Run is the durable execution and ledger identity of that Invocation.
Graph is the typed topology that advances Scroll state among Spell placements. The Loom is a read-only projection of its declared truth. The current fixed registry has no independent Spell catalogue or teaching surface.
The current registry is fixed and source-defined:
bridge_chat@1
WeaveContext → Converse → AwaitConsent? → ProjectReply → End
delegated_rite@1
DispatchDelegate ⇢ ProjectDelegatedReply → End
Admission chooses once. The registered workflow name and exact manifest snapshot are committed with the Run; resume looks up that stored choice and never routes the Intent again.
The registry is executable substrate, not a general workflow platform. delegated_rite@1
exercises only the deterministic reference adapter; it delivers no foreign runtime or execution
plane.
Progressive craft without a mutable score
A future media Scroll shows how exact stations can compose without making an engine graph or one model canonical:
commission + sources + language policy + finish boundary
→ Prism Image candidates
→ exact Magus review Gate
├─ requested still reached → VisualAssetBundle@1 → terminal
└─ continue in the pinned score
→ Prism Video i2v or first_last
→ motion review and visual package → terminal
Qwen Image, another local model, or a Portal may implement the image Spell; LTX, Wan, or another eligible profile may implement the video Spell. A ComfyUI graph is the immutable engine preset behind one implementation, never this Scroll. The receiver-owned Resolution Lock binds each placement to its exact local or Portal implementation before casting.
The finish boundary answers “how far this Invocation should go.” Stopping at an admitted still is completion, not an indefinite pause. A review, hardware transition, or remote wait may enter Stasis while the same casting remains live. Continuing a terminal still into motion starts a new Invocation over its immutable artifact. Optional music starts a Riffmaw Invocation. Synchronized audio returned by a video model remains a compound candidate whose declared role routes musical material to Riffmaw, timed-language material to Language Edition, and picture-bound effects or ambience to Broadcast while retaining the shared Prism attempt and provenance parent. Final audiovisual relation belongs to Broadcast, and live cross-Composition coordination is a Suite.
An A2A peer can request the public task while the receiver privately chooses this decomposition, or send a portable Scroll as an inert candidate. Neither path imports a Comfy graph, model, custom node, credential, or authority. The same Scroll may accept different prompts, languages, source frames, target profiles, and finish boundaries; changing its stations or contracts creates a new revision.
The present score
Topology-A local runs and the Pydantic AI 1.25.1 adapter are Available. Graph Stasis, delegated execution, extension activation, and Loom remain Partial.
Pattern contribution and durable publication, scheduling, durable parallelism, compatibility and migration, editing, authorship attestation, and protected-region admission remain undelivered. Architectural treatment is not operational evidence.
Follow the Scroll
Choose the route that matches the question:
- Pattern lifecycle covers identity, manifests, admission, contribution, authorship protection, and revision continuity.
- Crucible covers two-round adversarial formation: declared biased Postures, independent first claims, attributed rebuttal, dissent-preserving synthesis, and the Magus Gate.
- Scheduling and service classes covers foreground, deadline-windowed, and spare-capacity admission, schedule time law, overlap, and explicit misses.
- Stasis and return covers Live and Durable Stasis, checkpoints, re-admission, terminal cleanup, and recovery limits.
- Execution roads covers the layered choice among native/local work, Portal-backed cognition, sovereign A2A tasks, delegated coding runtimes, and operator seats.
- Anonymization, taint, and egress covers the local Privacy Cut, information-flow labels, Portal admission, quarantined return, and the boundary that makes subsidized remote reasoning usable.
- Delegated agents covers the typed delegated station,
AgentJobboundary, containment, and the present deterministic, no-network, effect-free reference adapter.
Repository coding-agent choreography is separate: the tracked workflow playbooks own contributor procedure only, never Spellweaver or Pattern law.