Claim Verifier

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

id

claim-verifier

name

Claim Verifier

type

validation

phases

Testing

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

action32 words

Check every claim in the draft against the passages it cites, release only the ones that hold, and return the rest as a gap list the synthesizer can answer on another pass.

spec169 words

For each asserted sentence in the document on draft, open the source its citation points at and decide one thing only: whether that source, read on its own, carries that sentence. Do not weigh how plausible the sentence is, and do not go looking for a different source that would rescue it. Emit on grounded the same document reduced to the sentences that survived, their citations untouched. Emit on gaps one entry per sentence that failed, quoting the sentence and stating exactly why it failed, the source says something narrower, the source contradicts it, the source does not mention it, or there was no citation at all. Never edit a sentence to make it pass and never supply a citation of your own; your output is a verdict with the evidence behind it, and the rewriting belongs to someone else. After the third pass over the same document, release whatever is grounded and carry the outstanding gaps into the report as stated gaps rather than sending it round again.in full above

model

claude-opus-5

agent

Fact-checker

skill

skills/claim-verifier.md

tools

none

mcp

none

params

max_retries: 2, min_citations_per_claim: 1

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

inputs

draft : report

outputs

grounded : report, gaps : status

dependencies

evidence-synthesizer

cannot

no type is refused

will_not

edit a sentence to make it pass, supply a citation of its own

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

risk_markers

none

notes103 words

max_retries: 2 is what bounds the synthesize/verify loop: two passes beyond the first, three in all, which is the third pass the spec above stops on. After it the run ships whatever is grounded, with the remaining gaps stated rather than quietly dropped. Engine spec §2.6 counts the attempts that follow the initial execution, so the number that reads as three passes is written as two, and the key is spelled the way Attractor spells it. It is the only declared iteration cap on the cycle synth -> factcheck -> synth, so removing it fires the inferred unbounded-loop marker on the whole blueprint.

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

version

1.1.0

author

autogen

provenance

not stated