Get card
Download
findings-delivery@1.0.0.yamlClone
npx -y darkprint clone findings-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 cleared synthesis as it stands, and record that it went.
used in 1 blueprint
Specification
88 words · handed to the agentTake the synthesis on cleared and publish it to the destination the run was configured with, unchanged. Do not add a summary above it, do not drop the parts about where the field was thin or where its agreement was suspect, and do not reorder it to lead with the strongest finding, those caveats are the part a reader most needs and the part most easily lost in delivery. Emit a receipt on receipt naming what was published and when. Publish nothing that did not arrive on cleared.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| cleared | report | required | The synthesis the safety screen let through. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| receipt | status | What was published and when, or the reason nothing was. |
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
16 declaredWho the node is. The id is the key the DOT pins.
- id
- findings-delivery
- name
- Findings Delivery
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action12 words
- Publish the cleared synthesis as it stands, and record that it went.
- spec88 words
- Take the synthesis on
clearedand publish it to the destination the run was configured with, unchanged. Do not add a summary above it, do not drop the parts about where the field was thin or where its agreement was suspect, and do not reorder it to lead with the strongest finding, those caveats are the part a reader most needs and the part most easily lost in delivery. Emit a receipt onreceiptnaming what was published and when. Publish nothing that did not arrive oncleared.in full above - model
- whatever the graph supplies
- agent
- Publisher
- skill
- not named
- tools
- File I/O
- mcp
- filesystem
- params
- none
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- cleared : report
- outputs
- receipt : status
- dependencies
- hypothesis-safety-screen
- cannot
- no type is refused
- will_not
- drop the caveats from a synthesis it publishes, publish anything that did not arrive on the cleared port
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- findings-delivery@1.0.0currentsha256:2143a1eea6a78a3b4f10e568cd85e814773d9e80e7ebc0898ab5d40a8b62ace2
pinned byHypothesis Tournament
autogen/hypothesis-tournament
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.