Get card
Download
anomaly-gate@1.0.0.yamlClone
npx -y darkprint clone anomaly-gate@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.
Hold the run report to the declared thresholds and emit one signal: a breach naming the step, the metric, the threshold and the figure, or an all-clear.
used in 1 blueprint
Specification
156 words · handed to the agentRead the report handed to you on report and first decide whether it can be judged: every step named in it needs a record count and a failure count, and every step past the first needs a timing. When something is missing, emit on rejected what is missing and for which step, and judge nothing on that pass. When the report is whole, compare each step's failures with failures_per_step and its timing with duration_ms; the unparseable row is compared with unparseable_records in the same way. Emit one notice on signal. When any threshold is crossed, the notice is a breach and names the step, the metric, the threshold and the figure the report carries, worst first when several crossed; when none is crossed, the notice says the run is clear and carries the totals. Quote the report's figures as they stand: the report is not yours to edit, and the thresholds are not yours to move.
Interfaces
1 in · 2 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| report | report | required | The run report, one row per step, as the summariser wrote it. |
Outputs
2Dependencies
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
17 declaredWho the node is. The id is the key the DOT pins.
- id
- anomaly-gate
- name
- Anomaly Gate
- type
- validation
- phases
- Testing
What it does, and the prose the agent is handed when the graph runs.
- action27 words
- Hold the run report to the declared thresholds and emit one signal: a breach naming the step, the metric, the threshold and the figure, or an all-clear.
- spec156 words
- Read the report handed to you on
reportand first decide whether it can be judged: every step named in it needs a record count and a failure count, and every step past the first needs a timing. When something is missing, emit onrejectedwhat is missing and for which step, and judge nothing on that pass. When the report is whole, compare each step's failures withfailures_per_stepand its timing withduration_ms; theunparseablerow is compared withunparseable_recordsin the same way. Emit one notice onsignal. When any threshold is crossed, the notice is a breach and names the step, the metric, the threshold and the figure the report carries, worst first when several crossed; when none is crossed, the notice says the run is clear and carries the totals. Quote the report's figures as they stand: the report is not yours to edit, and the thresholds are not yours to move.in full above - model
- claude-haiku-4-5
- agent
- Threshold judge
- skill
- skills/anomaly-gate.md
- tools
- none
- mcp
- none
- params
- thresholds: {"duration_ms":30000,"failures_per_step":1,"unparseable_records":0}, max_retries: 2
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- report : report
- outputs
- signal : event, rejected : status
- dependencies
- run-summariser
- cannot
- no type is refused
- will_not
- edit the report it judges, move a threshold to make a run pass
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes63 words
max_retriesis the cap on the loop back to the summariser: a report the gate cannot judge goes back at most twice, and the security analyzer reads that key as the bound on the cycle, so removing it would charge the loop as unbounded. The thresholds sit under a key of their own so an operator can tune them without touching the spec.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- anomaly-gate@1.0.0currentsha256:9764b9559b2a66aba09442a5509e0554d685390fc217ef8944f9a0dd590a39f6
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.