Get card
Download
route-critic@1.0.0.yamlClone
npx -y darkprint clone route-critic@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.
Grade the answer, and separately record whether the lane it came from was the right one.
used in 1 blueprint
Specification
154 words · handed to the agentYou are handed an answer. Decide whether it actually answers the question it was given: whether it is correct as far as you can tell, whether it is complete, and whether anything in it is asserted with more confidence than the working supports. When it holds, emit it unchanged on accepted, emit nothing on rework, and set your preferred label to accepted. When it does not, emit nothing on accepted, write on rework what is wrong and what a second attempt should do differently, and set your preferred label to anything else. Either way, say in one sentence on rework or accepted whether the lane that produced this answer was the right one for the question: a simple question answered by the expensive lane and a hard one answered by the fast lane are both routing faults, and they are the signal that the router's thresholds want moving. Do not rewrite the answer yourself.
Interfaces
1 in · 2 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| answer | markdown | required | The answer from whichever lane ran, with no indication of which one that was beyond its content. |
Outputs
2Dependencies
2The upstream nodes this card expects to receive from. Whenever a blueprint pins this card, each name is checked against a real edge in that graph. A name without a link is not a published card; it refers to a node inside some graph.
Card values
15 declaredWho the node is. The id is the key the DOT pins.
- id
- route-critic
- name
- Route Critic
- type
- validation
- phases
- Testing
What it does, and the prose the agent is handed when the graph runs.
- action16 words
- Grade the answer, and separately record whether the lane it came from was the right one.
- spec154 words
- You are handed an answer. Decide whether it actually answers the question it was given: whether it is correct as far as you can tell, whether it is complete, and whether anything in it is asserted with more confidence than the working supports. When it holds, emit it unchanged on
accepted, emit nothing onrework, and set your preferred label toaccepted. When it does not, emit nothing onaccepted, write onreworkwhat is wrong and what a second attempt should do differently, and set your preferred label to anything else. Either way, say in one sentence onreworkoracceptedwhether the lane that produced this answer was the right one for the question: a simple question answered by the expensive lane and a hard one answered by the fast lane are both routing faults, and they are the signal that the router's thresholds want moving. Do not rewrite the answer yourself.in full above - model
- whatever the graph supplies
- agent
- Critic
- skill
- not named
- tools
- none
- mcp
- none
- params
- max_retries: 1
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- answer : markdown
- outputs
- accepted : markdown, rework : report
- dependencies
- flash-answerer, deep-reasoner
- cannot
- no type is refused
- will_not
- rewrite the answer it judges, send a rejected answer back to the lane that produced it
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes44 words
- Both exits are guarded on
preferred_label, because this node completes whichever way it grades andoutcomewould read the same on both arms.max_retriesis 1: a second rejection means the question is harder than this graph, not that a third attempt will land.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- route-critic@1.0.0currentsha256:d3df0917901c9918aa76decc1ca5dbf4923f493b709076f2076253144dbdd840
pinned byBudget Aware Router
autogen/budget-aware-router
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.