Get card
Download
step-tracer@1.0.0.yamlClone
npx -y darkprint clone step-tracer@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.
Turn every value a watched step emits into one trace record carrying the step's name, the time it arrived, its outcome, and the size and digest of the value, and hand the record on.
used in 1 blueprint
Specification
146 words · handed to the agentYou sit beside one step of a pipeline. You are handed whatever that step emits on step, and its outcome on outcome when the pipeline emits one. For every value that arrives, write one trace record and emit it on traces: the step's name, the time the value arrived in UTC, the outcome as the step reported it or unknown when nothing arrived on outcome, the byte size of the value, and a sha256 over its canonical form. When the outcome is a failure, copy the first line of the error into the record and nothing more of it. Never copy the value itself into a record: a trace names what passed and how big it was, and the payload stays on the edge it came in on. Write nothing to disk and keep nothing between records; whoever runs the graph decides where records are kept.
Interfaces
2 in · 1 outInputs
2| Name | Data type | Required | Description |
|---|---|---|---|
| step | structured | required | One step's output, as the pipeline emitted it. Any typed structured value wires here. |
| outcome | status | optional | The step's own outcome, when the pipeline emits one, so a failure is counted rather than read as a missing record. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| traces | json | One trace record per value seen, with the step's name, arrival time, outcome, size and digest. |
Dependencies
0None declared, no edge has to arrive for this node to run.
Card values
13 declaredWho the node is. The id is the key the DOT pins.
- id
- step-tracer
- name
- Step Tracer
- type
- tool
- phases
- none declared
What it does, and the prose the agent is handed when the graph runs.
- action34 words
- Turn every value a watched step emits into one trace record carrying the step's name, the time it arrived, its outcome, and the size and digest of the value, and hand the record on.
- spec146 words
- You sit beside one step of a pipeline. You are handed whatever that step emits on
step, and its outcome onoutcomewhen the pipeline emits one. For every value that arrives, write one trace record and emit it ontraces: the step's name, the time the value arrived in UTC, the outcome as the step reported it orunknownwhen nothing arrived onoutcome, the byte size of the value, and a sha256 over its canonical form. When the outcome is a failure, copy the first line of the error into the record and nothing more of it. Never copy the value itself into a record: a trace names what passed and how big it was, and the payload stays on the edge it came in on. Write nothing to disk and keep nothing between records; whoever runs the graph decides where records are kept.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- skills/step-tracer.md
- tools
- none
- mcp
- none
- params
- clock: utc, digest: sha256, include_error_head: true
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- step : structured, outcome : status
- outputs
- traces : json
- dependencies
- none
- cannot
- no type is refused
- will_not
- copy a step's payload into a record, write a record anywhere but its output port
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes70 words
stepis typedstructuredrather thananyso the edge into it stays a typed edge: json, a table, a report or a plan wires straight in, and a step that emits text or bytes needs a wrapping step first. The record carries a digest and a size in place of the value, which is what lets the records travel to the summariser without carrying the pipeline's data with them.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- step-tracer@1.0.0currentsha256:bde41983fb57171ce381c3a84394f5cef961406613712cfeacbbd93db9f76e8d
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.