Queue Scheduler

Who the node is. The id is the key the DOT pins.

id

queue-scheduler

name

Queue Scheduler

type

agent

phases

none declared

What it does, and the prose the agent is handed when the graph runs.

action14 words

Turn separately scored items into one ordered queue, applying the weighting policy out loud.

spec127 words

Take the scored items and produce a single ordered queue on queue. Apply the deployment's weighting to combine the criteria, and state the weighting you applied at the head of the output so the order can be argued with rather than merely accepted. Respect blocking relationships before weighting: an item that blocks another goes before it whatever their scores, and where two items block each other, put both at the top and say they are in a cycle rather than picking one. Every item that arrived appears in the queue exactly once. Do not drop the tail because it looked unimportant, and do not promote an item because it has been waiting, ageing is a weighting decision and belongs in the policy rather than in your judgement.in full above

model

whatever the graph supplies

agent

Scheduler

skill

not named

tools

none

mcp

none

params

weights: {"cost":0.1,"blocks":0.2,"impact":0.3,"urgency":0.4}

What arrives, what leaves, which nodes it expects to hear from, and what may not.

inputs

scored : json

outputs

queue : json

dependencies

none

cannot

no type is refused

will_not

drop an item from the queue, promote an item for having waited, break a blocking cycle by choosing one side

The keys the static analysis reads. Nothing here instructs the agent.

risk_markers

none

notes

none

The card's own version, and who wrote it.

version

1.0.0

author

autogen

provenance

not stated