Get card
Download
report-delivery@1.0.0.yamlClone
npx -y darkprint clone report-delivery@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.
Publish the grounded report to its reader with the citation trail intact, so every claim in it can be walked back to the passage that supports it.
used in 1 blueprint
Specification
130 words · handed to the agentPublish the verified document on report to the research-desk destination, addressed to the person whose question opened the run. Carry the citation trail across unchanged: every sentence keeps the inline citation it arrived with, and the reference list keeps each source's identifier URL, document id, or repository path and commit sha, together with the time it was retrieved, so a reader can walk any sentence back to the text behind it. Do not reorder, reword, shorten or reformat the content; you are delivering a verified artefact, not editing one. Publish exactly once, and only after the whole document and its reference list have arrived, once it has gone out it cannot be recalled or amended, so an incomplete input is a reason to stop, not to send a partial report.
Interfaces
1 in · 0 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| report | report | required | The fact-checked report, as the verifier released it. |
Outputs
0No outputs declared, whatever this node produces leaves the graph.
Dependencies
1The 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
- report-delivery
- name
- Report Delivery
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action27 words
- Publish the grounded report to its reader with the citation trail intact, so every claim in it can be walked back to the passage that supports it.
- spec130 words
- Publish the verified document on
reportto theresearch-deskdestination, addressed to the person whose question opened the run. Carry the citation trail across unchanged: every sentence keeps the inline citation it arrived with, and the reference list keeps each source's identifier URL, document id, or repository path and commit sha, together with the time it was retrieved, so a reader can walk any sentence back to the text behind it. Do not reorder, reword, shorten or reformat the content; you are delivering a verified artefact, not editing one. Publish exactly once, and only after the whole document and its reference list have arrived, once it has gone out it cannot be recalled or amended, so an incomplete input is a reason to stop, not to send a partial report.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- skills/report-delivery.md
- tools
- none
- mcp
- filesystem
- params
- destination: research-desk, include_citations: true
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- report : report
- outputs
- none
- dependencies
- claim-verifier
- cannot
- no type is refused
- will_not
- edit the report it delivers, publish before the reference list has arrived
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- irreversible-action
- 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- report-delivery@1.0.0currentsha256:83f43ee3d0dc9c50e1a91baf6a2926f34dc0217007d0d8282c3d592ca28d3197
pinned byGrounded Research Desk
autogen/grounded-research-desk
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.