H3 Local Reconstruction Acceptance

Twenty-one required inputs. That's the headline number, and it tells you most of what you need to know: this is not a node you sprinkle into a workflow, it's a gate at the end of one.

What it does

It accepts an end-to-end reconstruction route - and only one route is acceptable. The module behind it keeps a fixed disposition table: deterministic_manual is complete; full_reference_perception, comfyui_native, ollama and specialist are not_qualified; official_oracle and fixed_h3_generation are not_authorized. So the node's answer is a qualified yes to exactly one thing - the chain where every claim was authored by a human and every step is deterministic - and a documented no to everything else.

Read that list again, because it's a design statement. Machine perception doesn't qualify. An external oracle doesn't qualify. Fixed H3 generation doesn't qualify. What qualifies is the manual route, fully assembled: request, registry, admitted media, hard constraints and their report, intent and its report, evidence and its report, cross-references and theirs, directive authority and theirs, the feasible timeline, the hierarchical reduction, the semantic planning stage, the plan, the profiled prompt, validation, the validated report, and the native H3 wiring. All present, all current.

"Current" is doing real work. The node checks that each value is an exact typed object and that each report actually belongs to the value it was issued for. It also refuses when the media envelope's own disposition isn't complete - partial admission can't be accepted as a finished route.

Inputs and outputs

The input list is basically the full stage inventory above: request, reference_registry, media, hard_constraints, hard_constraints_report, intent_graph, intent_report, evidence_graph, evidence_report, cross_reference_graph, cross_reference_report, directive_authority, directive_report, feasible_timeline, hierarchical_reduction, semantic_planning, plan, profiled_prompt, validation, validated_report, native_h3_wiring. No widgets.

Three outputs:

• reconstruction (H3_LOCAL_RECONSTRUCTION) - the acceptance record.
• accepted_prompt - the prompt text, now formally accepted for the route.
• accepted_report - the context report that goes with it.

Wire the accepted prompt into the native H3 nodes; keep the reconstruction record if you need to show what your pipeline actually did.

Why anyone wants this

Because "we generated it with AI" is not an audit trail, and increasingly that matters - regulation and platform policy in 2026 keep pushing on documentation of what a generative pipeline did and which decisions were human (ai-regulation.md). This node is the pack's answer to that pressure: a single acceptance value that says the route was deterministic, manual, and complete, with no model-directed inference anywhere in it.

It's also just useful engineering. The failure it prevents is the muddle - a workflow that half-ran, a stage you bypassed to save a click, a prompt that's technically valid but built on evidence the pipeline never verified. Downstream of acceptance, you know what you're standing on.

Install

Standard for the pack, and it's not in the registry yet:

cd ComfyUI/custom_nodes
git clone https://github.com/rookiestar28/ComfyUI-MiniMaxH3-Studio.git
# restart ComfyUI

Zero Python dependencies declared, no model downloads at install time, prebuilt frontend extension, Python 3.10+. The repo's workflows/m13_10_local_reconstruction.json is an API-format graph wiring all twenty-one inputs - the only sane way to learn this node's shape is to open that file and read the edges.

Honest advice

Most people should not build this. If you want a video, use the sidebar's Start H3 App Mode or the four-node core route (Request → Plan → Compiler → Validator → Preview), and never think about acceptance gates. This node exists for pipelines that need to make a provable claim about their own determinism.

If you do want it, build the chain forwards in the order the inputs are listed, and run it after every change - not at the end. A missing or stale stage surfaces as a refusal naming the stage, so running it early turns a debugging session into a to-do list. That's about the friendliest thing a twenty-one-input node can do for you.