H3 Local Reconstruction Acceptance:
The H3 Local Reconstruction Acceptance node is a final acceptance point for a manually assembled H3 context workflow. It brings together the visible stages of an end-to-end reconstruction route without repeating the work those stages have already performed. Here, “reconstruction” refers to assembling and accepting the context-processing route, not directly reconstructing an image or generating a video. The node is specifically described as accepting only a current, deterministic manual route: a workflow assembled through explicit stages rather than an unspecified alternative route. Its purpose is to provide a controlled handoff after context preparation, planning, and validation, along with a structured record of the accepted reconstruction. If the acceptance operation encounters a contract, type, or value error, it stops rather than returning a partially accepted result. This makes it useful when you need an explicit checkpoint before passing prepared context further through an H3 workflow.
H3 Local Reconstruction Acceptance Input Parameters:
request
Required connection of type H3_CONTEXT_REQUEST, represented internally as a RawContextRequest. This supplies the context request that the reconstruction is being accepted against, giving the acceptance operation the original request alongside the later processing stages. Connect the request belonging to the same workflow you are assembling, rather than a separate request created for another task. The node forwards this object to the acceptance routine; it does not expose controls for editing the request here. Minimum, maximum, default, and selectable options are not specified; this is a required structured connection, not a numeric or text setting.
reference_registry
Required connection of type H3_REFERENCE_REGISTRY, represented internally as a ReferenceRegistry. This supplies the workflow’s reference registry alongside the stages that use reference-related information. Including it allows the acceptance operation to receive the registry associated with the reconstruction, rather than relying only on the final prompt. Use the registry from the same context-processing route as the other connected objects. The supplied source does not expose the registry’s internal fields or its detailed acceptance rules. Minimum, maximum, default, and selectable options are not specified.
media
Required connection of type H3_MEDIA_PRODUCER_RESULT, represented internally as a PerceptionProducerResult. This carries the result of the media-perception stage into the final acceptance operation. It is a structured producer result, not a direct image, video, or audio socket, so connect the compatible H3 stage result rather than raw media. Its role is to include that stage’s result in the assembled reconstruction; this node does not perform media perception again. Minimum, maximum, default, and selectable options are not specified.
hard_constraints
Required connection of type H3_HARD_CONSTRAINTS, represented internally as a HardConstraintSet. This supplies the hard-constraint set associated with the workflow—the requirements treated as firm restrictions during context processing. The acceptance operation receives these constraints together with their accompanying producer report and the later planning stages. You do not adjust constraint strength or add restrictions inside this node; prepare them upstream. Minimum, maximum, default, and selectable options are not specified.
hard_constraints_report
Required connection of type H3_DOWNSTREAM_PRODUCER_REPORT, represented internally as a DownstreamProducerReport. This supplies the report associated with producing the hard constraints, giving the acceptance operation both the constraint result and its corresponding report. Connect the report produced for the connected hard_constraints rather than another report that happens to share the same socket type. The supplied source does not show which report fields are inspected during acceptance. Minimum, maximum, default, and selectable options are not specified.
intent_graph
Required connection of type H3_INTENT_GRAPH, represented internally as an IntentGraph. This supplies the structured intent stage of the context workflow, allowing it to be included alongside constraints, evidence, and planning information during acceptance. It is an already-created graph object rather than a place to type your creative instructions. Any changes to the intent representation must be made upstream before reconnecting or rerunning the route. Minimum, maximum, default, and selectable options are not specified.
intent_report
Required connection of type H3_DOWNSTREAM_PRODUCER_REPORT. This is the producer report associated with the connected intent_graph. Its purpose is to carry the reporting information for that stage into acceptance, rather than leaving the acceptance operation with only the graph itself. Because multiple report inputs use this same type, take care to connect the intent stage’s report specifically. Minimum, maximum, default, and selectable options are not specified.
evidence_graph
Required connection of type H3_UNIFIED_EVIDENCE_GRAPH, represented internally as a UnifiedEvidenceGraph. This supplies the unified evidence representation assembled upstream for the context workflow. The node forwards it to the acceptance operation as one of the existing stages; it does not build, merge, or reinterpret evidence in the visible node implementation. Connect the graph belonging to the route you intend to accept. Minimum, maximum, default, and selectable options are not specified.
evidence_report
Required connection of type H3_DOWNSTREAM_PRODUCER_REPORT. This supplies the producer report corresponding to evidence_graph, so the reconstruction includes both the evidence-stage result and its report. Use the report generated with that evidence graph, especially when you have several evidence-processing branches in a workflow. The exact report content and field-level acceptance checks are not shown in the supplied implementation. Minimum, maximum, default, and selectable options are not specified.
cross_reference_graph
Required connection of type H3_CROSS_REFERENCE_GRAPH, represented internally as a CrossReferenceGraph. This supplies the workflow’s cross-reference graph as a distinct part of the reconstruction. It is separate from the unified evidence graph and must be provided through its own compatible connection. The visible node passes it into the acceptance operation without modifying it; the supplied excerpts do not specify its internal relationship types or matching rules. Minimum, maximum, default, and selectable options are not specified.
cross_reference_report
Required connection of type H3_DOWNSTREAM_PRODUCER_REPORT. This supplies the producer report associated with cross_reference_graph. Its role is to accompany the cross-reference stage during acceptance, rather than substitute for the graph itself. Connect the report from the same cross-reference production step, not the evidence, intent, constraint, or directive report. Minimum, maximum, default, and selectable options are not specified.
directive_authority
Required connection of type H3_DIRECTIVE_AUTHORITY, represented internally as a DirectiveAuthorityBundle. This supplies the directive-authority information prepared by the upstream workflow. It is included as an existing structured stage in the acceptance operation, not used as an editable instruction-priority control in this node. The supplied source does not describe the bundle’s internal authority rules, so specific override or conflict-resolution behavior cannot be inferred here. Minimum, maximum, default, and selectable options are not specified.
directive_report
Required connection of type H3_DOWNSTREAM_PRODUCER_REPORT. This supplies the report corresponding to the connected directive_authority bundle. Including the matching report keeps the directive stage and its reporting information together in the reconstruction submitted for acceptance. Although its socket type is shared with several other reports, its intended source is specifically the directive-authority stage. Minimum, maximum, default, and selectable options are not specified.
feasible_timeline
Required connection of type H3_FEASIBLE_AV_TIMELINE, represented internally as a ReconstructionTimelineStage. This supplies the already-prepared feasible audiovisual timeline stage of the reconstruction route. The acceptance node receives this stage rather than calculating a timeline or exposing timing controls itself. If you need to revise timing-related planning, make that change in the upstream timeline stage and regenerate affected downstream results. Minimum, maximum, default, and selectable options are not specified.
hierarchical_reduction
Required connection of type H3_HIERARCHICAL_EVIDENCE_REDUCTION, represented internally as a ReconstructionReductionStage. This supplies the result of the hierarchical evidence-reduction stage for inclusion in the accepted route. The node does not expose reduction strength, hierarchy depth, or evidence-selection settings, and the supplied source does not establish the reduction algorithm. Treat this as an already-produced stage object that must come from a compatible upstream connection. Minimum, maximum, default, and selectable options are not specified.
semantic_planning
Required connection of type H3_CONSTRAINED_SEMANTIC_PLANNING, represented internally as a ReconstructionSemanticStage. This supplies the constrained semantic-planning stage of the reconstruction. It is passed to the acceptance operation alongside the timeline, reduction stage, and context plan; this node does not perform that planning again. Any adjustments to how meaning or constraints are handled must be made in the stage that produces this object. Minimum, maximum, default, and selectable options are not specified.
plan
Required connection of type H3_CONTEXT_PLAN, represented internally as a ContextPlan. This supplies the context plan being accepted as part of the assembled route. It is distinct from the semantic-planning stage object, and both connections are required by the interface. The node forwards the plan to the acceptance routine rather than creating or editing it. Minimum, maximum, default, and selectable options are not specified.
profiled_prompt
Required connection of type H3_SOURCE_PROFILED_PROMPT, represented internally as a SourceProfiledPromptResult. This supplies the structured source-profiled prompt for the reconstruction. It has two visible roles: the complete object is submitted to the acceptance routine, and, after acceptance succeeds, its document.text value is returned as accepted_prompt. Consequently, changes to the prompt text must be made upstream; this node does not rewrite or embellish it. Minimum, maximum, default, and selectable options are not specified.
validation
Required connection of type H3_VALIDATION_RESULT, represented internally as a ValidationResult. This supplies the validation result associated with the assembled context workflow. The acceptance operation receives it together with the prepared prompt, context plan, and report; the visible node does not provide a validation bypass or tolerance setting. The supplied excerpts do not identify the individual validation checks or status values accepted by the underlying routine. Minimum, maximum, default, and selectable options are not specified.
validated_report
Required connection of type H3_CONTEXT_REPORT, represented internally as a ContextReport. This supplies the context report submitted with the reconstruction for acceptance. After successful acceptance, the node returns this same report as accepted_report; it does not visibly generate a replacement report or alter its contents. Use the report associated with the connected prompt and validation result. Minimum, maximum, default, and selectable options are not specified.
native_h3_wiring
Required connection of type H3_NATIVE_H3_WIRING, represented internally as a NativeH3Wiring. This supplies the native H3 wiring object included in the acceptance operation. The reconstruction result includes a wiring fingerprint, making wiring information part of the recorded reconstruction, although the supplied excerpts do not show how that fingerprint is calculated or checked. This is a structured connection, not a switch that automatically connects your workflow. Minimum, maximum, default, and selectable options are not specified.
H3 Local Reconstruction Acceptance Output Parameters:
reconstruction
Output of type H3_LOCAL_RECONSTRUCTION, represented internally as a LocalReconstructionResult. This is the structured result issued when the acceptance operation succeeds. The supplied result definition includes the route, its disposition, stage fingerprints, prompt fingerprint, report fingerprint, wiring fingerprint, limitations, a run fingerprint, and a schema identifier. Fingerprints serve as identifying signatures for recorded content or stages; they are not image-quality scores. This output is therefore the reconstruction’s acceptance record, not generated media or a replacement prompt. The excerpts do not enumerate the possible route dispositions or limitation messages.
accepted_prompt
Output of type H3_PROMPT_STRING. On successful acceptance, this is exactly the text taken from profiled_prompt.document.text. The node does not visibly add wording, remove content, or run a new prompt-generation step before returning it. You can use it wherever a compatible H3 prompt-string connection is expected, with the understanding that “accepted” means the reconstruction acceptance routine completed successfully, not that the node has assessed the artistic quality of a future image or video.
accepted_report
Output of type H3_CONTEXT_REPORT. This is the same validated_report object supplied to the node, returned only after the acceptance routine succeeds. It lets you pass the existing context report onward alongside the accepted prompt and reconstruction record without creating a second report. Its contents should be interpreted according to the upstream report-producing stage; this node does not visibly summarize, rewrite, or add fields to it.
H3 Local Reconstruction Acceptance Usage Tips:
- Place this node at the acceptance end of your manually assembled H3 context route. It joins existing stages rather than replacing perception, planning, prompt preparation, or validation.
- Connect all 21 required inputs. There are no optional inputs, numeric tuning controls, dropdown settings, or defaults exposed by this node.
- Keep stage results and reports paired correctly. In particular, the five
H3_DOWNSTREAM_PRODUCER_REPORTsockets have the same type, so matching socket types alone does not tell you whether a report belongs to the intended stage. - Use objects from one coherent workflow route. After changing the request, references, constraints, or planning stages, rerun the affected downstream stages before attempting acceptance again.
- Make creative and planning adjustments upstream. To change wording, edit the process that produces
profiled_prompt; to change timing, adjust the producer offeasible_timeline. This node has no local controls for either task. - Connect structured H3 results rather than raw text or media. For example,
mediaexpects a media-producer result, whileprofiled_promptexpects a source-profiled prompt object rather than a plain string. - Use
accepted_promptandaccepted_reportfor onward delivery, and retainreconstructionwhen you need the route record, fingerprints, or recorded limitations. - Treat this as a strict acceptance checkpoint. Its description limits acceptance to a current deterministic manual end-to-end route, and the interface provides no override for another route.
H3 Local Reconstruction Acceptance Common Errors and Solutions:
local_reconstruction_failed — local reconstruction failed closed
- Explanation: These are the error identifier and message passed to the node’s pipeline-error helper when the acceptance routine raises
ContractValidationError,TypeError, orValueError. “Failed closed” means the node stops rather than returning a partially accepted reconstruction, prompt, or report. The final display formatting depends on the error helper. - Solution: Inspect the full error details or console traceback for the underlying cause. Check that all connected objects belong to the intended route, that reports match their stages, and that affected downstream stages have been rerun after upstream changes.
ContractValidationError during acceptance
- Explanation: This is an underlying exception class explicitly caught by the node, not a guaranteed standalone interface message. It indicates that an acceptance contract was not satisfied. The supplied source does not show the individual contract checks, so the exact cause cannot be determined from the wrapper message alone.
- Solution: Read the chained exception for the specific failed condition. Review the upstream validation result and reports, confirm that you are using the supported manual reconstruction route, and correct the reported issue before trying again.
TypeError during acceptance
- Explanation: This exception class is caught and converted into the failure-closed pipeline error. It can indicate that a supplied value is not of the form expected by the acceptance implementation. The source does not provide a specific type-error message.
- Solution: Verify every connection against the declared socket type. Avoid substituting raw strings, raw media, or manually assembled objects for the required H3 stage results. If the problem follows a package update, recreate or refresh affected upstream nodes and rerun them.
ValueError during acceptance
- Explanation: This exception class is also caught and converted into the failure-closed pipeline error. It indicates that the acceptance operation rejected a value, but the supplied excerpts do not identify the permitted values or the exact rejection conditions.
- Solution: Inspect the underlying exception rather than guessing which setting to change. Regenerate the affected stage through its normal producer, check its associated report, and rerun downstream processing so the acceptance node receives an updated set of results.
Missing required input or incompatible connection
- Explanation: This is a connection troubleshooting category, not an exact error string shown in the provided source. Every input is required and uses a declared socket type, so an incomplete graph or incompatible connection can prevent the workflow from reaching acceptance.
- Solution: Check all 21 required sockets and connect each to a compatible H3 output. Pay particular attention to the structured timeline, reduction, semantic-planning, source-profiled prompt, and native-wiring inputs; none has a fallback value.
Stage and report connected to the wrong matching-type sockets
- Explanation: This is a possible wiring issue, not a confirmed literal error message. Several report connections share
H3_DOWNSTREAM_PRODUCER_REPORT, so a connection can look type-compatible while referring to a different stage. The supplied source does not show whether or how each such mismatch is diagnosed. - Solution: Trace each report wire to its producer and pair it with the corresponding hard-constraint, intent, evidence, cross-reference, or directive-authority result. If acceptance still fails, use the underlying exception details to identify any additional mismatch.
