Get card
Download
draft-delivery@1.0.0.yamlClone
npx -y darkprint clone draft-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 approved draft exactly as it was handed over, and record that it went.
used in 1 blueprint
Specification
93 words · handed to the agentTake the draft on approved and publish it to the destination the run was configured with, byte for byte as you received it. Do not reformat it, do not add a header, a footer or a note about how it was produced, and do not hold it back because you would have written it differently. Emit a receipt on receipt naming what was published and when. If publication fails, say so on the receipt and do not retry silently: a second attempt that nobody asked for can put the same piece out twice.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| approved | markdown | required | The draft the critic cleared, unchanged since it cleared. |
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
- draft-delivery
- name
- Draft Delivery
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action15 words
- Publish the approved draft exactly as it was handed over, and record that it went.
- spec93 words
- Take the draft on
approvedand publish it to the destination the run was configured with, byte for byte as you received it. Do not reformat it, do not add a header, a footer or a note about how it was produced, and do not hold it back because you would have written it differently. Emit a receipt onreceiptnaming what was published and when. If publication fails, say so on the receipt and do not retry silently: a second attempt that nobody asked for can put the same piece out twice.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
- approved : markdown
- outputs
- receipt : status
- dependencies
- draft-critic
- cannot
- no type is refused
- will_not
- edit a draft that has already been cleared, publish anything that did not come off the approved 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- draft-delivery@1.0.0currentsha256:71d9c3f57900c969277fc5aff1c64ea581985aa27ec10d334c559355276793e7
pinned byProducer Critic Refinery
autogen/producer-critic-refinery
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.