Get card
Download
dataset-publisher@1.0.0.yamlClone
npx -y darkprint clone dataset-publisher@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.
Cut the committed batch into a dataset version, announce it on the release channel with its row count and schema reference, and close the run.
used in 1 blueprint
Specification
102 words · handed to the agentRead the commit receipt on dataset and cut it into a new immutable version of the forge-records dataset, tagged with the last batch boundary the receipt reports. Post one announcement to the data-releases channel naming that version, its row count and the schema reference the records were checked against. Cut the version before you announce it, and announce it exactly once, the channel has human subscribers and neither the published version nor the message can be recalled once it lands. The run closes when the channel has accepted the announcement; if the version cannot be cut, announce nothing and report the failure.
Interfaces
1 in · 0 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| dataset | json | required | The store's commit receipt, which is what a dataset version is cut from. |
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
16 declaredWho the node is. The id is the key the DOT pins.
- id
- dataset-publisher
- name
- Dataset Publisher
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action25 words
- Cut the committed batch into a dataset version, announce it on the release channel with its row count and schema reference, and close the run.
- spec102 words
- Read the commit receipt on
datasetand cut it into a new immutable version of theforge-recordsdataset, tagged with the last batch boundary the receipt reports. Post one announcement to thedata-releaseschannel naming that version, its row count and the schema reference the records were checked against. Cut the version before you announce it, and announce it exactly once, the channel has human subscribers and neither the published version nor the message can be recalled once it lands. The run closes when the channel has accepted the announcement; if the version cannot be cut, announce nothing and report the failure.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- skills/dataset-publisher.md
- tools
- Messaging
- mcp
- slack
- params
- dataset: forge-records, announce_channel: data-releases
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- dataset : json
- outputs
- none
- dependencies
- record-store
- cannot
- no type is refused
- will_not
- announce a version it has not cut, announce the same version twice
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- dataset-publisher@1.0.0currentsha256:7258bf3690741eb2afc1924aa80f57f672d899d6cee263e32ab04fccdefe2df7
pinned bySchema Forge ETL
autogen/schema-forge-etl
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.