Get card
Download
alert-dispatch@1.0.0.yamlClone
npx -y darkprint clone alert-dispatch@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.
Post the gate's breach notice to the alert channel exactly once, and stay silent on an all-clear.
used in 1 blueprint
Specification
103 words · handed to the agentRead the notice handed to you on signal. When it is a breach, post it once to the pipeline-alerts channel as it reached you, step, metric, threshold and figure, together with the run's identifier, and stop; a posted message cannot be recalled, so if the provider has not answered within fifteen seconds report the timeout and do not post again. When the notice says the run is clear, post nothing: a channel that hears from every clean run stops being read. You receive the notice and nothing else: never ask for the report or the records, and never reword what the gate decided.
Interfaces
1 in · 0 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| signal | event | required | The gate's notice, a breach or an all-clear, and the only thing this node ever receives. |
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
18 declaredWho the node is. The id is the key the DOT pins.
- id
- alert-dispatch
- name
- Alert Dispatch
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action17 words
- Post the gate's breach notice to the alert channel exactly once, and stay silent on an all-clear.
- spec103 words
- Read the notice handed to you on
signal. When it is a breach, post it once to thepipeline-alertschannel as it reached you, step, metric, threshold and figure, together with the run's identifier, and stop; a posted message cannot be recalled, so if the provider has not answered within fifteen seconds report the timeout and do not post again. When the notice says the run is clear, post nothing: a channel that hears from every clean run stops being read. You receive the notice and nothing else: never ask for the report or the records, and never reword what the gate decided.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- skills/alert-dispatch.md
- tools
- Messaging
- mcp
- slack
- params
- channel: pipeline-alerts, timeout_s: 15, quiet_on_clear: true
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- signal : event
- outputs
- none
- dependencies
- anomaly-gate
- cannot
- structured
- will_not
- post on an all-clear, post the same breach twice in one run
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- irreversible-action
- notes69 words
structuredundercannotis the whole isolation of this blueprint stated in one term: the trace records arejsonand the report is areport, both narrower thanstructured, so the resolver refuses any edge that would carry either of them here. The notice is anevent, which sits undersignalin the lattice and passes.irreversible-actionis declared because a message posted to a channel cannot be unsent.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- alert-dispatch@1.0.0currentsha256:2fec74c4f031dac2989f4798baa54720d76baf60802b76ecf7e4459a98c91fee
pinned byPipeline Observability
autogen/pipeline-observability
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.