Get card
Download
reply-delivery@1.0.0.yamlClone
npx -y darkprint clone reply-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.
Send the reply that was cleared, or the one a reviewer released, and record that it went.
used in 1 blueprint
Specification
98 words · handed to the agentTake what arrives on clean_reply and send it to the requester exactly as you received it. It reached you one of two ways, cleared by the filter or released by a reviewer, and it is sent the same way in both cases: do not annotate a reviewed reply as reviewed, and do not add a note about the delay. Emit a receipt on receipt saying what was sent and when. Send nothing that did not arrive on that port, and do not resend on your own initiative if the first attempt failed, say so on the receipt instead.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| clean_reply | markdown | required | The reply the filter cleared, or the one the reviewer released. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| receipt | status | What was sent and when, or the reason nothing was. |
Dependencies
2The 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
- reply-delivery
- name
- Reply Delivery
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action17 words
- Send the reply that was cleared, or the one a reviewer released, and record that it went.
- spec98 words
- Take what arrives on
clean_replyand send it to the requester exactly as you received it. It reached you one of two ways, cleared by the filter or released by a reviewer, and it is sent the same way in both cases: do not annotate a reviewed reply as reviewed, and do not add a note about the delay. Emit a receipt onreceiptsaying what was sent and when. Send nothing that did not arrive on that port, and do not resend on your own initiative if the first attempt failed, say so on the receipt instead.in full above - model
- whatever the graph supplies
- agent
- Delivery
- skill
- not named
- tools
- Messaging
- mcp
- slack
- params
- none
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- clean_reply : markdown
- outputs
- receipt : status
- dependencies
- output-filter, reviewer-gate
- cannot
- no type is refused
- will_not
- edit a reply that has already been cleared, resend on its own initiative after a failure
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- reply-delivery@1.0.0currentsha256:3b1e1567ee3a3ab5164ad305c21c6f937846e5b99961c5b81759d569553e4fd1
pinned byGuarded Assistant Line
autogen/guarded-assistant-line
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.