Get card
Download
answer-delivery@1.0.0.yamlClone
npx -y darkprint clone answer-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.
Return the released answer to whoever asked, and record that it went.
used in 1 blueprint
Specification
83 words · handed to the agentTake the answer on released and return it to the caller the run was opened for, exactly as you received it. Do not reformat it, do not prepend a summary, and do not attach a note about which lane produced it, the caller asked a question and is owed an answer rather than an account of the machinery. Emit a receipt on receipt saying what was returned and when. If delivery fails, say so on the receipt rather than retrying on your own.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| released | markdown | required | The answer the budget gate let through. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| receipt | status | What was returned 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
15 declaredWho the node is. The id is the key the DOT pins.
- id
- answer-delivery
- name
- Answer Delivery
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action12 words
- Return the released answer to whoever asked, and record that it went.
- spec83 words
- Take the answer on
releasedand return it to the caller the run was opened for, exactly as you received it. Do not reformat it, do not prepend a summary, and do not attach a note about which lane produced it, the caller asked a question and is owed an answer rather than an account of the machinery. Emit a receipt onreceiptsaying what was returned and when. If delivery fails, say so on the receipt rather than retrying on your own.in full above - model
- whatever the graph supplies
- agent
- Delivery
- skill
- not named
- tools
- Messaging
- mcp
- none
- params
- none
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- released : markdown
- outputs
- receipt : status
- dependencies
- budget-gate
- cannot
- no type is refused
- will_not
- alter the answer it returns, report a failed delivery as a success
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- answer-delivery@1.0.0currentsha256:aa326048037b388548049a100b261dfdedc66f6f8904cbc78f086b1506097944
pinned byBudget Aware Router
autogen/budget-aware-router
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.