Get card
Download
resolution-composer@1.0.0.yamlClone
npx -y darkprint clone resolution-composer@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.
Draft a candidate resolution for the routed request, grounding every claim in the reference document when one was retrieved and marking the gap when it was not.
used in 2 blueprints
Specification
122 words · handed to the agentRead the routed request on request and write one candidate resolution for it. When a reference document arrives on reference, ground every factual claim you make in that document and name the passage each claim came from; when nothing arrives on reference, say in the draft which claims are unsupported instead of filling the gap from memory. Emit the draft on draft together with its citations and a confidence figure between 0 and 1 that reflects how well the reference actually covered the request, not how well the prose reads. Do not present the draft as approved, sent or applied, and do not act on it yourself, you are done the moment the draft, its citations and that figure are on draft.
Interfaces
2 in · 1 outInputs
2Outputs
1| Name | Data type | Description |
|---|---|---|
| draft | json | The proposed resolution, its citations, and a self-reported confidence. |
Dependencies
2- classify
- kb
The 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
17 declaredWho the node is. The id is the key the DOT pins.
- id
- resolution-composer
- name
- Resolution Composer
- type
- agent
- phases
- Implementation
What it does, and the prose the agent is handed when the graph runs.
- action27 words
- Draft a candidate resolution for the routed request, grounding every claim in the reference document when one was retrieved and marking the gap when it was not.
- spec122 words
- Read the routed request on
requestand write one candidate resolution for it. When a reference document arrives onreference, ground every factual claim you make in that document and name the passage each claim came from; when nothing arrives onreference, say in the draft which claims are unsupported instead of filling the gap from memory. Emit the draft ondrafttogether with its citations and a confidence figure between 0 and 1 that reflects how well the reference actually covered the request, not how well the prose reads. Do not present the draft as approved, sent or applied, and do not act on it yourself, you are done the moment the draft, its citations and that figure are ondraft.in full above - model
- claude-sonnet-5
- agent
- Resolver
- skill
- skills/resolution-composer.md
- tools
- none
- mcp
- none
- params
- max_tokens: 900, temperature: 0.3
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- request : json, reference : markdown
- outputs
- draft : json
- dependencies
- classify, kb
- cannot
- no type is refused
- will_not
- fill a gap from memory when no reference arrived, present its draft as approved
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes56 words
referenceis optional because the router sends the simple lane straight here without a lookup. A reply and a mitigation are the same operation over different corpora, which is what lets both support lines pin this card; nothing downstream should read the draft as approved, because that is the checking node's call and not this one's.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- resolution-composer@1.0.0currentsha256:622b724d517ae0ca73f5b1499e302b859ece8b74aba1540cd109812b26c57331
pinned byFrontline Triage
autogen/frontline-triage,Incident Commanderautogen/incident-commander
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.