Call

In plain words: Listen: receiving and routing requests

1 min read 4 glossary terms 14 connected pages
The short version written for the Snayu team

A conceptual page on the Listen function (Call): receiving a request and opening possible routes for it, without yet deciding which route is right. In practice this maps to workflow discovery and routing.

Why read it: Read this when working on request routing or discovery, to understand why routing proposals must still be checked before action.
  1. 1Listen opens candidate routes; Judge (Blade) decides which may proceed and Own it (Answer) takes responsibility.
  2. 2Small specialised routing models may propose a destination quickly, but a proposal still needs checking.
  3. 3Candidate creation and promotion are governed by Design Rule 16 (SDLC).

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

What is here, and what must answer it?

Before a movement can be judged, it must become reachable. Call, the Manas correspondence, receives present IntentRequest and routes it toward a bounded relation. The active Flux holds more movement than one act can carry. Giving a movement a destination opens a possible continuation without deciding that it should happen.

The word works at two scales. In the First Invocation, the MagusYou, the Operator’s outer Call establishes an address with a new center; inner Call distributes what that InvocationJob Request requires. The Called exists inside an address before it possesses an answer.

Call's opening takes concrete form within discovery: a question finds relevant scopes, owners, and possible routes through the work. Following a branch can reveal a witness or a constraint absent from the first account. What can be asked changes with what has become reachable. Manas meets the craft here through reception and address; Blade examines the relevance, sufficiency, and limits of what has been found. A missing premise can send Call outward again.

For a familiar request, a quick route proposal may be enough. A specialized decision model can suggest a destination and express uncertainty before a general reasoning model attempts the whole task. Specialized models for routing considers Jev and similar models as possible latency optimizations. Call and Blademind office name functions, so their distinction prescribes neither model size nor speed. Even a quick proposal still needs discernment before action.

Call may turn toward a Seed and invite Recall, or open several candidates. That is opening, not selection. Unchecked routing takes the Rajas image of activity into branching without consequence; the guṇa correspondence keeps that image beside its source. Its proper completion is the Blade, which decides whether a line may proceed; Answer later bears the attributable act.

ADR 16 — SDLC owns the creation and promotion of candidates. Call names the opening through which a possible movement becomes addressable.