H3 Evidence Fusion Producer:
The H3 Evidence Fusion Producer prepares admitted source metadata for use as structured evidence within an H3 context workflow. Its purpose is to represent information already available about admitted sources while keeping uncertainty explicit, rather than treating that information as proof of what an image or other media actually contains. The implementation describes this as an “uncertainty-capped” projection: it organizes source metadata without claiming semantic perception, such as recognizing objects, understanding a scene, or interpreting an artistic style. For your creative workflows, this provides a metadata-based foundation for later processing while preserving the important distinction between information recorded about a source and information established by analyzing its contents. Despite the name “Evidence Fusion,” the supplied implementation does not establish that this node performs image analysis, compares visual features, or runs a perception model.
H3 Evidence Fusion Producer Input Parameters:
media
A required connection of type H3_MEDIA_PRODUCER_RESULT that supplies the admitted-source information used to construct the evidence graph. In practical terms, this is a structured result from an upstream media-producing stage, not an image upload field, file path, text prompt, or ordinary ComfyUI IMAGE connection. The node passes this result to the admission-evidence builder, so the metadata available in the connected result determines the information available for projection into evidence. This node exposes no controls for adding missing source information or changing how uncertainty is handled. Connect a compatible upstream output, such as the corresponding media result from the H3 Media Admission Producer, after confirming its socket type matches. Minimum, maximum, default value, and selectable options are not specified; this parameter is a required typed connection rather than a numeric or menu setting.
H3 Evidence Fusion Producer Output Parameters:
evidence_graph
A structured H3_UNIFIED_EVIDENCE_GRAPH result containing the evidence representation produced from admitted source metadata. This is the main result to connect to a downstream node that explicitly accepts this socket type. Its importance is that it presents source information in a graph form while retaining the node’s uncertainty-limited scope: you should interpret it as metadata-derived evidence, not as confirmation that visual or audio content has been understood. It is not a rendered image, generated artwork, or a plain-text description. The supplied implementation does not expose the graph’s internal fields, individual evidence values, or numerical uncertainty limits, so those details cannot be specified from this interface.
producer_report
A structured H3_DOWNSTREAM_PRODUCER_REPORT returned alongside the evidence graph by the same admission-evidence construction operation. It provides a separate reporting result that can be passed to compatible downstream components without treating it as the evidence graph itself. The source identifies the result as a DownstreamProducerReport, but does not show its field definitions or contents; consequently, you should not assume it always contains particular status messages, confidence scores, warnings, or counts. Use a compatible downstream consumer or inspection facility, where available, to examine the actual report rather than interpreting it as ordinary text.
H3 Evidence Fusion Producer Usage Tips:
- Connect
mediato an upstream output with the exact typeH3_MEDIA_PRODUCER_RESULT. An ordinary image connection is not a substitute for the structured admitted-media result this node expects. - Prepare and verify your source information upstream. Because this node projects admitted metadata rather than performing semantic perception, it cannot independently fill in missing descriptions or verify that a recorded description matches the media.
- Use this node when you need metadata-based evidence preparation. If your task requires understanding objects, composition, or other media content, use an appropriate perception stage elsewhere in your workflow; do not treat this node as a replacement for that analysis.
- Connect
evidence_graphandproducer_reportonly to downstream sockets that accept their respective types. They serve different purposes and are not interchangeable. - There are no exposed model, threshold, confidence, resolution, or performance settings to tune. Adjust the upstream source preparation or downstream processing instead of looking for configuration controls on this node.
- Keep the node connected to a downstream processing or output branch when you want it evaluated. Its definition sets
OUTPUT_NODEtoFalse, so it is an intermediate processing node rather than a standalone workflow endpoint.
H3 Evidence Fusion Producer Common Errors and Solutions:
Required input missing: media
- Explanation: The node declares
mediaas required. Leaving this connection empty prevents normal workflow validation or execution. This heading describes the problem; the exact ComfyUI message may vary. - Solution: Connect an upstream
H3_MEDIA_PRODUCER_RESULToutput tomedia, then run the workflow again.
Incompatible connection type for media
- Explanation: The input requires
H3_MEDIA_PRODUCER_RESULT, not an ordinary image, string, or a different H3 result type. ComfyUI may reject the connection or report a type mismatch; the supplied node code does not define an exact error message. - Solution: Check the upstream output’s socket type and use a compatible media producer. If your workflow begins with an image or file, first process it through the appropriate upstream admission stage.
Failure while building admission evidence
- Explanation: The node delegates construction to
build_admission_evidence_graphwithout local exception handling. A failure in that operation can therefore surface during execution, but its validation rules and error strings are not included in the supplied source. - Solution: Read the execution error or console traceback, identify the reported cause, and verify that the upstream media producer completed successfully. Avoid manually substituting arbitrary objects for the required structured result.
The node does not run when the workflow is queued
- Explanation: This node is not an output node. If it is disconnected from the branch being evaluated, it may not execute; this is a workflow-connection issue rather than a documented exception.
- Solution: Connect its results to compatible downstream processing that leads to an active output node, then queue the workflow again.
The result does not contain the expected scene understanding
- Explanation: This is a scope mismatch rather than a documented error message. The node explicitly projects admitted source metadata without claiming semantic perception, so its results should not be expected to establish objects, scene meaning, or other content-level conclusions.
- Solution: Use an appropriate perception stage to obtain content-level analysis, and keep that analysis distinct from metadata-only evidence when assembling your workflow.
