Get card
Download
assemble-stage@1.0.0.yamlClone
npx -y darkprint clone assemble-stage@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.
Assemble the transformed set into the artefact the job asked for and attach the stage-by-stage trace, so the verifier judges the output and the path that produced it together.
used in 1 blueprint
Specification
105 words · handed to the agentAssemble the transformed working set you are handed into the single bundle the job asked for, and abandon the assembly rather than emit a half-built bundle if it runs longer than 240 seconds. Attach a stage-by-stage trace alongside it: for each part of the bundle, record which stage produced it and from which input, so the output and the path that produced it can be read together. Emit the bundle and its trace on artifact. You are done when every record in the transformed set is either present in the bundle or listed in the trace as deliberately dropped, with the reason it was dropped.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| transformed | json | required | The transformed working set from the previous stage, diff included. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| artifact | json | The finished artefact plus the trace of which stages contributed which part of it. |
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
- assemble-stage
- name
- Assemble Stage
- type
- agent
- phases
- Implementation
What it does, and the prose the agent is handed when the graph runs.
- action29 words
- Assemble the transformed set into the artefact the job asked for and attach the stage-by-stage trace, so the verifier judges the output and the path that produced it together.
- spec105 words
- Assemble the transformed working set you are handed into the single bundle the job asked for, and abandon the assembly rather than emit a half-built bundle if it runs longer than 240 seconds. Attach a stage-by-stage trace alongside it: for each part of the bundle, record which stage produced it and from which input, so the output and the path that produced it can be read together. Emit the bundle and its trace on
artifact. You are done when every record in the transformed set is either present in the bundle or listed in the trace as deliberately dropped, with the reason it was dropped.in full above - model
- claude-sonnet-5
- agent
- Stage workers
- skill
- skills/assemble-stage.md
- tools
- none
- mcp
- none
- params
- timeout_s: 240, output_format: bundle
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- transformed : json
- outputs
- artifact : json
- dependencies
- transform-stage
- cannot
- no type is refused
- will_not
- emit a half-built bundle
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- 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- assemble-stage@1.0.0currentsha256:20d6bbcf4df8335412ebe895e344d53a3ab766b8bbd573a0fac26dd0b73a4da0
pinned byCheckpoint & Resume Runner
autogen/checkpoint-resume-runner
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.