Get card
Download
panel-fan-in@1.0.0.yamlClone
npx -y darkprint clone panel-fan-in@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.
Collect the branch verdicts into one set without reconciling them, and say plainly when a branch did not report.
used in 0 blueprints
Specification
118 words · handed to the agentGather what each branch produced and emit all of it on collected, each verdict tagged with the branch it came from and otherwise untouched. Do not reconcile them, do not summarise them, and do not drop the outlier: disagreement between branches is the signal a panel exists to produce, and a fan-in that resolves it has thrown away the only thing the extra branches bought. Where a branch produced nothing, or failed, record that as a missing verdict rather than omitting the branch, a set of two verdicts that was meant to be three is a different result from a set of two. Whichever node decides what the panel concluded reads this output; you are not that node.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| verdicts | json | required | What each branch produced, arriving as the branches finish. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| collected | json | Every branch's verdict tagged with its source, plus an explicit entry for any that did not report. |
Dependencies
0None declared, no edge has to arrive for this node to run.
Card values
12 declaredWho the node is. The id is the key the DOT pins.
- id
- panel-fan-in
- name
- Panel Fan In
- type
- parallel.fan-in
- phases
- none declared
What it does, and the prose the agent is handed when the graph runs.
- action19 words
- Collect the branch verdicts into one set without reconciling them, and say plainly when a branch did not report.
- spec118 words
- Gather what each branch produced and emit all of it on
collected, each verdict tagged with the branch it came from and otherwise untouched. Do not reconcile them, do not summarise them, and do not drop the outlier: disagreement between branches is the signal a panel exists to produce, and a fan-in that resolves it has thrown away the only thing the extra branches bought. Where a branch produced nothing, or failed, record that as a missing verdict rather than omitting the branch, a set of two verdicts that was meant to be three is a different result from a set of two. Whichever node decides what the panel concluded reads this output; you are not that node.in full above - model
- whatever the graph supplies
- agent
- Fan in
- skill
- not named
- tools
- none
- mcp
- none
- params
- none
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- verdicts : json
- outputs
- collected : json
- dependencies
- none
- cannot
- no type is refused
- will_not
- reconcile or summarise the verdicts it collects, drop an outlier, omit a branch that failed to report
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes25 words
- A
parallel.fan-incard, the counterpart topanel-fanout. Confirm the runner wires fan-out results through to a fan-in before building a graph that depends on it.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- panel-fan-in@1.0.0currentsha256:570cadcc676f86e2a21d606704b8def0ef8c7234fa583cacbd1f25e5f1fc3dd5
No blueprint pins this exact version.
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.