H3 Hierarchical Evidence Reduction:
The HierarchicalEvidenceReduction node reduces already-admitted evidence under explicit, deterministic budgets, helping you keep a bounded selection of supporting information for later planning stages. Its purpose is to manage existing evidence without inventing observations or filling gaps with unsupported content. The underlying reduction model records what was retained, what was dropped, and summaries of the reduction levels, together with a receipt that makes the process traceable. It also preserves important quality distinctions: when the underlying evidence graph is partial or ambiguous, or the timeline plan is partial, the reduction is marked partial rather than presented as complete. This makes the node useful in evidence-driven creative workflows where you need controlled information reduction while keeping uncertainty visible. Validation failures stop the operation rather than allowing an invalid reduction to continue.
H3 Hierarchical Evidence Reduction Input Parameters:
media
Required connection of type H3_MEDIA_PRODUCER_RESULT. This supplies the media perception producer result to the reconstruction reduction process; it is a structured result from an earlier processing stage, not a direct image, video filename, or text prompt. The node passes this result together with the evidence and timeline information to the reduction builder, so you should supply the media result associated with the material being planned. The provided code does not show which individual fields the builder reads or how those fields influence evidence selection. Minimum: not applicable; maximum: not applicable; default: none declared; selectable options: none. This parameter must be supplied through a compatible connection.
evidence_graph
Required connection of type H3_UNIFIED_EVIDENCE_GRAPH. This supplies the unified evidence graph used by the reduction process. In the provided core implementation, the graph contributes its fingerprint—a reference identifying the graph used—to the reduction plan, helping preserve traceability. Its status also affects the result: a graph marked partial or ambiguous causes the core reduction status to be partial rather than complete. For your workflow, this means incomplete or uncertain evidence is not automatically upgraded to a fully complete result simply because reduction succeeds. Minimum: not applicable; maximum: not applicable; default: none declared; selectable options: none. Connect the graph that belongs to the same evidence-processing workflow as the other required data.
evidence_report
Required connection of type H3_DOWNSTREAM_PRODUCER_REPORT. This provides the downstream producer report passed into the reconstruction reduction builder alongside the media result, evidence graph, and feasible timeline. It is a structured workflow report rather than a text instruction or an adjustable reduction setting. The supplied node source confirms that this report is required, but does not expose the builder implementation needed to describe its individual fields, validation rules, or precise effect on item selection. Supply the report associated with the evidence you are reducing rather than substituting a report from an unrelated run. Minimum: not applicable; maximum: not applicable; default: none declared; selectable options: none.
feasible_timeline
Required connection of type H3_FEASIBLE_AV_TIMELINE. This supplies the reconstruction timeline stage used by the reduction builder, providing the timeline context for reducing evidence within the planning workflow. The underlying core reduction model records the timeline plan’s fingerprint, and a timeline plan marked partial makes the reduction status partial. Consequently, the completeness of timeline planning matters to how you should interpret the reduction result; successful execution alone does not establish that the timeline information was complete. The provided source does not expose the timeline stage’s internal fields or any timing controls on this node. Minimum: not applicable; maximum: not applicable; default: none declared; selectable options: none. Connect the feasible timeline associated with the same media and evidence.
H3 Hierarchical Evidence Reduction Output Parameters:
reduction
Output of type H3_HIERARCHICAL_EVIDENCE_REDUCTION. This is the reconstruction reduction stage returned by the builder, intended for compatible downstream workflow stages rather than direct display as an image or text summary. The underlying core reduction model includes a status, a reduction plan, and a receipt; the plan can record retained evidence, dropped item identifiers, reduction-level summaries, graph and timeline fingerprints, diagnostics, and limitations. These records help distinguish the information kept from the information removed and preserve references to the planning material used. A partial status indicates that completeness is limited, including when the evidence graph is partial or ambiguous or the timeline plan is partial. The supplied code does not show how the reconstruction-stage wrapper exposes these internal records, so do not assume that every core field is directly accessible from the socket. If validation raises one of the handled exceptions, the node raises a pipeline error instead of returning this output.
H3 Hierarchical Evidence Reduction Usage Tips:
- Connect all four required inputs from the same media-and-evidence workflow. Keeping the media result, graph, report, and timeline together helps avoid incompatible planning data.
- Look for this node in the
h3_context/planningcategory. Use it after the required evidence and feasible timeline stages have produced their structured results. - Treat this as evidence reduction, not evidence generation. If an observation is missing or unsupported, address it in the upstream evidence-producing stages rather than expecting reduction to invent it.
- Check upstream graph and timeline completeness when you need a complete result. The core implementation explicitly carries partial or ambiguous graph status and partial timeline status into a partial reduction status.
- There are no exposed budget, token-limit, coverage, or fidelity controls on this node. The budget values shown in the separate semantic-review example belong to that specific core call and are not defaults or adjustable settings for this node.
- Where your downstream tools expose the reduction records, review retained items, dropped identifiers, receipts, diagnostics, and limitations before relying on the reduced evidence for an important creative decision.
H3 Hierarchical Evidence Reduction Common Errors and Solutions:
hierarchical_reduction_failed / hierarchical evidence reduction failed closed
- Explanation: These are the error identifier and message supplied by the node when the reduction builder raises
ContractValidationError,TypeError, orValueError. “Failed closed” means the node stops rather than continuing with an invalid reduction. This message alone does not identify which input caused the problem. - Solution: Inspect the chained exception in the ComfyUI logs for the underlying cause. Confirm that all four inputs come from compatible stages of the same workflow, then rerun any upstream stage whose result is invalid or incomplete.
ContractValidationError
- Explanation: This is one of the exception types caught and wrapped by the node. It indicates that supplied or constructed data failed a required contract check, although the supplied source does not list the individual checks or their exact messages.
- Solution: Read the underlying validation message in the logs. Rebuild the affected upstream result using the expected H3 stage, and avoid mixing results from unrelated media or incompatible workflow versions.
TypeError or ValueError
- Explanation: These exception types are also caught and converted to the node’s failure message. They can indicate that the builder encountered an unsuitable object type or an unacceptable value; the exact cause must be determined from the chained exception.
- Solution: Verify the socket types of all connected producers and check that the upstream nodes completed successfully. If you recently changed custom nodes or workflow components, regenerate the affected structured results before rerunning reduction.
unsupported reduction receipt schema
- Explanation: This exact validation message appears in the provided core code when a reduction receipt’s schema does not match the expected schema. It is a possible underlying compatibility issue, not a separately exposed node setting.
- Solution: If this message appears in the underlying error details, regenerate the affected data with compatible versions of the H3 components. Avoid reusing serialized reduction data from an incompatible version, and do not manually change the schema label to bypass validation.
