Get card
Download
dynamic-repriority@1.0.0.yamlClone
npx -y darkprint clone dynamic-repriority@1.0.0There is no repository and no history behind a card. Download hands you the document as it stands, and Clone fetches the same document by name.
Decide whether an arriving event is big enough to disturb the queue, and record the decision where a fork can read it.
used in 0 blueprints
Specification
143 words · handed to the agentAn event has arrived while a queue is already in flight. Decide whether it changes the order. Say reorder when the event makes something in the queue urgent that was not, when it blocks an item currently near the top, or when it makes an item pointless. Say hold for everything else, and mean it: a queue that is rebuilt on every event is not a queue, and the cost of reordering is paid by whatever was about to run. Emit the event on routed unchanged either way. Record the decision in your status file: put repriority in context_updates, set to the value you chose, so the fork downstream can branch on context.repriority. A run that leaves that key unwritten reads back as the empty string, so the arm that a silent run takes should be the one that leaves the queue alone.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| event | event | required | The event that arrived while a queue was already in flight. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| routed | event | The event passed on unchanged, whichever way the decision went. |
Dependencies
0None declared, no edge has to arrive for this node to run.
Card values
13 declaredWho the node is. The id is the key the DOT pins.
- id
- dynamic-repriority
- name
- Dynamic Repriority
- type
- decision
- phases
- none declared
What it does, and the prose the agent is handed when the graph runs.
- action22 words
- Decide whether an arriving event is big enough to disturb the queue, and record the decision where a fork can read it.
- spec143 words
- An event has arrived while a queue is already in flight. Decide whether it changes the order. Say
reorderwhen the event makes something in the queue urgent that was not, when it blocks an item currently near the top, or when it makes an item pointless. Sayholdfor everything else, and mean it: a queue that is rebuilt on every event is not a queue, and the cost of reordering is paid by whatever was about to run. Emit the event onroutedunchanged either way. Record the decision in your status file: putrepriorityincontext_updates, set to the value you chose, so the fork downstream can branch oncontext.repriority. A run that leaves that key unwritten reads back as the empty string, so the arm that a silent run takes should be the one that leaves the queue alone.in full above - model
- whatever the graph supplies
- agent
- Repriority
- skill
- not named
- tools
- none
- mcp
- none
- params
- default_decision: hold
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- event : event
- outputs
- routed : event
- dependencies
- none
- cannot
- no type is refused
- will_not
- reorder the queue itself, rebuild a queue on an event that changes nothing
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes35 words
- A
decisioncard runs as a no-op that writes no preferred label, so the fork reading this node must branch on the context key the spec sets. Put the negation arm on holding the queue.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- dynamic-repriority@1.0.0currentsha256:070b287ed47ad0647d3404640f1d762f7b6c63338215af3d6266f75d07c717e8
No blueprint pins this exact version.
A digest is a fingerprint (SHA-256) of the card's content, computed without the author and provenance fields. The same card from two people gets the same digest; any edit gets a new one.
First published version, so there is nothing to compare yet. Versions are never edited in place: the next change arrives as a new version, and the differences between the two documents are listed here.
Community notes (0)
No notes yet.
Nobody has posted about this node card yet.
Sign in to post a note.