Evidence Synthesizer

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

id

evidence-synthesizer

name

Evidence Synthesizer

type

agent

phases

Implementation, Debugging

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

action29 words

Draft a single answer from the fanned-in passages, citing the passage behind every claim, and on a return pass rewrite only the claims the fact-checker sent back as unsupported.

spec156 words

You receive on passages one pool of retrieved text, fanned in from several corpora, where each entry carries its own identifier, a URL, a document id, or a repository path and commit. Write a single continuous answer to the research question drawing only on that pool, and attach an inline citation to the identifier of the specific entry behind every sentence that asserts something; if the pool will not carry a statement, leave the statement out rather than hedging it into the text. Emit the finished answer on draft. On a second entry you will also receive gaps, which names individual claims from your previous draft and what was found wrong with each, rewrite exactly those claims against the same pool and leave every other sentence of the draft untouched. You are done when every asserted sentence in draft carries a citation into the pool and nothing named in gaps has been left as it was.in full above

model

claude-opus-5

agent

Synthesizer

skill

skills/evidence-synthesizer.md

tools

none

mcp

none

params

max_tokens: 2000, temperature: 0.3, citation_style: inline

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

inputs

passages : json, gaps : status

outputs

draft : report

dependencies

web-retriever, vector-recall, code-index-search, claim-verifier

cannot

no type is refused

will_not

read the rule the fact-checker judges its citations by, assert anything the retrieved pool will not carry

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

risk_markers

none

notes81 words

gaps is optional because the first pass has none, the node is written to be entered twice, once cold and once with the verifier's complaints in hand, and a rewrite pass touches only the claims named in gaps so the grounded parts of the draft stay stable across iterations. What comes back is failure evidence, not the rule the verifier judges by: the spec deliberately does not restate how a citation is tested, so the synthesizer cannot write to the test.

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

version

1.0.0

author

autogen

provenance

not stated