Get card
Download
deep-reasoner@1.0.0.yamlClone
npx -y darkprint clone deep-reasoner@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.
Answer a question that needs more than one step, and answer it again when the critic sends it back.
used in 1 blueprint
Specification
128 words · handed to the agentAnswer the question in front of you. Work the problem through rather than reaching for the first plausible answer: where two readings of the question are both defensible, say which one you took and why, and where an intermediate result decides the rest, get that result right before going on. When a set of notes arrives on rework, treat it as the whole of what is being asked and answer again addressing exactly what it names, rather than starting over from nothing. Emit the answer on answer with no commentary about the process attached. This node is the expensive one in the graph; a run that lands here because nothing routed it is answering an unclassified question, which is a correct thing to do and a costly one.
Interfaces
2 in · 1 outInputs
2Outputs
1| Name | Data type | Description |
|---|---|---|
| answer | markdown | The worked answer, with nothing attached to it. |
Dependencies
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
- deep-reasoner
- name
- Deep Reasoner
- type
- agent
- phases
- Implementation
What it does, and the prose the agent is handed when the graph runs.
- action19 words
- Answer a question that needs more than one step, and answer it again when the critic sends it back.
- spec128 words
- Answer the question in front of you. Work the problem through rather than reaching for the first plausible answer: where two readings of the question are both defensible, say which one you took and why, and where an intermediate result decides the rest, get that result right before going on. When a set of notes arrives on
rework, treat it as the whole of what is being asked and answer again addressing exactly what it names, rather than starting over from nothing. Emit the answer onanswerwith no commentary about the process attached. This node is the expensive one in the graph; a run that lands here because nothing routed it is answering an unclassified question, which is a correct thing to do and a costly one.in full above - model
- claude-opus-5
- agent
- Answerer
- skill
- not named
- tools
- none
- mcp
- none
- params
- none
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- question : text, rework : report
- outputs
- answer : markdown
- dependencies
- complexity-router, route-critic
- cannot
- no type is refused
- will_not
- restart from nothing when it was handed notes on a previous answer
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- autogen/budget-overrun
- notes
- none
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- deep-reasoner@1.0.0currentsha256:9aec11acbc3d92ca645ed61e17d10c256349b8a1e54768285d45c911508b842d
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.