Discovery and router delegation

Discovery answers where to look next: which scope holds the relevant owners, which workflow fits the operation, and which exact score can be considered for execution. Within Spellweaver, these routes help a coordinating Agent find the material needed to frame a bounded task.

In the inner instrument, Call gives this opening its address: relevant parts of the work become reachable. Blade judges which material can support the next act. A route can widen the question before a method narrows it.

This is one part of discernment within exploration: finding a source may reveal a better question, while a decisive distinction may redirect the search. Creation Inquiry carries that exchange through bounded probes, independent sufficiency review, and Crucible.

Documentation topology owns scope routing; Workflow owns Pattern selection and task handoff. This page follows those boundaries in use.

How routers fan out

A router is an entry map with task triggers and explicit destinations. Some links end at an owning document; others enter another scope tree whose router exposes more specialized branches. The parent names when to enter that branch, while the destination maintains its deeper routes. A branch and its downstream links form a discoverable subgraph of the documentation map.

Each route makes its purpose and destination legible:

Fan-out makes several branches available. The task determines which branches are read and in what order. Enter another scope when the task crosses its boundary; leave unrelated branches unloaded. A link to a workflow does not start it, and a link to a Pattern does not register or authorize its casting.

Follow a repository route

The repository already provides a concrete example:

1. AGENTS.md routes a browser task to the Frontend scope.
2. Frontend routes a component or reactivity task onward to the Svelte scope. It also exposes the backend scope when the change crosses the browser projection boundary.
3. The selected scope leads to the canonical owner and the smallest source and test slice needed to establish behavior.
4. If the task edits source, the root's workflow route exposes the editing playbook. That playbook routes onward to an applicable file-type card; Svelte-specific work continues through its scope's required workflow.

The root keeps Frontend discoverable; Frontend keeps its specialist routes discoverable; the editing index keeps its procedure cards discoverable. Their contents remain with their owners. When adding or moving a branch, maintain its parent link, task trigger, and destination together. A missing prerequisite calls for a targeted probe or bounded request for the missing input.

From discovery to a task handoff

Once the relevant owners and procedure are known, the coordinator can frame the task and select the scope routes for its recipient. Under the designed scoped context handoff, those routes travel with the task, acceptance target, operator constraints, allowed inputs and effects, exact revisions, dependencies, and unresolved unknowns. The recipient then discovers further material within that admitted boundary.

Opening another scope in the current conversation retains the material already loaded. A new Agent handoff requires its own Context assembly. The parent keeps the wider purpose and assesses the returned candidate and verification evidence; the bounded-task example follows that exchange.

Discovering an executable score

For execution, use Pattern lifecycle to inspect the registered exact revision and its activation policy. Admission pins the selected score; resume uses that stored choice. A discovery link cannot redirect an admitted Run or splice a newly found branch into its immutable Scroll.

The current Loom browses the fixed Pattern registry. Scope routes and playbook links are repository navigation; they do not establish a runtime discovery service or executable subgraph composition. General parallel fan-out and joins retain the Graph design boundary, and scoped Agent handoff remains Designed.