H3 Cross Reference Producer:
The H3 Cross Reference Producer builds standardized, source-owned identities from admitted media, helping you organize references while keeping each identity grounded in its original source. Its central purpose is to establish source identity rather than infer semantic identity: it does not, by itself, determine that people, voices, objects, or scenes in different references represent the same real-world entity. This distinction helps you avoid treating uncertain relationships as established facts when assembling a reference-based creative workflow. The node supports source-only handling and an ambiguous resolution setting, allowing you to represent uncertainty instead of forcing a definitive identity decision. It belongs to the h3_context/assembly category and prepares structured reference information rather than generating or modifying artwork.
H3 Cross Reference Producer Input Parameters:
reference_registry
Required input of type H3_REFERENCE_REGISTRY. This supplies the reference registry used when building source-owned cross-reference identities. You can obtain this connection from the H3 Reference Registry node. The registry provides the reference context against which the admitted media is processed, so use the registry associated with that media rather than one from an unrelated workflow branch. This parameter accepts a structured connection, not a text description or an image directly. No default value, numerical minimum, or numerical maximum is defined in the interface.
media
Required input of type H3_MEDIA_PRODUCER_RESULT. This supplies the admitted media result from which the node builds source-owned identities. The provided reachability mapping identifies the H3 Media Admission Producer’s media output as a source of this connection. Although your references may contain images, video, or audio within the broader workflow, this socket expects the H3 media-result structure rather than a raw media connection. It works together with reference_registry to provide the source material and reference context for identity construction. No default value or numerical bounds are defined.
resolution
Optional dropdown with the options source_only and ambiguous; the default is source_only. This selects the resolution setting passed to the cross-reference builder. The default aligns with the node’s documented purpose of building identities grounded in sources without inferring semantic identities. The alternative, ambiguous, provides a way to select ambiguous handling rather than assume a resolved identity. The supplied class does not expose the builder’s detailed behavior, including how this setting interacts with candidate strings, so neither option should be treated as a guarantee of automatic matching or disambiguation. Numerical minimum and maximum values do not apply.
entity_kind
Optional dropdown that identifies the kind of entity being represented. Available options are subject, voice, object, and scene; the default is subject. Choose the category that fits your reference task—for example, voice for a voice-related identity or object for a prop-related identity. This value is passed to the cross-reference builder to specify the entity category; selecting it is not evidence that the node detects or recognizes that category automatically. Numerical minimum and maximum values do not apply, and no additional categories are listed in the interface.
candidate_a
Optional STRING input with an empty-string default, "". This provides the first candidate value passed to the cross-reference builder. It is available alongside candidate_b and the resolution setting, but the supplied code does not define whether the text must be an existing identifier, a label, or another representation, nor does it show when a nonempty value is required. Populate it according to the candidate conventions used by your surrounding H3 workflow rather than assuming it accepts arbitrary descriptive prompts. No minimum length, maximum length, or fixed set of allowed values is declared in the interface.
candidate_b
Optional STRING input with an empty-string default, "". This provides the second candidate value passed to the cross-reference builder, giving the node another candidate entry alongside candidate_a. The visible class forwards this text unchanged; it does not document candidate formatting rules, uniqueness requirements, or the exact relationship between candidates and ambiguous resolution. Use a value consistent with your workflow’s candidate conventions when you need to supply one, and do not interpret this field as an instruction to merge two identities. No minimum length, maximum length, or predefined options are declared.
H3 Cross Reference Producer Output Parameters:
cross_reference_graph
First output, of type H3_CROSS_REFERENCE_GRAPH. This is the structured cross-reference graph produced from the registry, admitted media, and selected settings. Its documented role is to represent canonical, source-owned identities without inferring semantic identities. In practical terms, you can use it to carry source-grounded identity information to compatible downstream H3 sockets, rather than manually converting that information into prompt text. It is not an image, an audio result, or proof that entities in separate references are the same. The provided code does not expose its internal fields or the precise representation of ambiguous cases.
producer_report
Second output, of type H3_DOWNSTREAM_PRODUCER_REPORT. This is the accompanying producer report returned with the cross-reference graph. It provides a separate reporting result for the production step, allowing compatible downstream tooling to consume report information independently of the graph. The supplied class does not reveal the report’s fields, status values, diagnostic messages, or display format, so you should not assume that it contains particular confidence scores, warnings, or counts. Use a compatible inspection or reporting path in your installed workflow to see the information it actually contains.
H3 Cross Reference Producer Usage Tips:
- Start with
resolutionset tosource_onlywhen you want source-grounded identities without making assumptions about whether entities across references are the same. - Keep
reference_registryandmediaconnected to the same reference-processing branch. This avoids accidentally pairing admitted media with an unrelated registry. - Choose
entity_kindto match your task:subjectfor subject references,voicefor voice-related references,objectfor props or other objects, andscenefor scene references. Treat this as a category setting, not an automatic recognition feature. - Use
ambiguouswhen your workflow needs ambiguous identity handling, but check the installed builder’s documentation or diagnostics before relying on a particular interpretation ofcandidate_aandcandidate_b. - Leave candidate fields at their empty defaults unless your workflow requires candidate values. The interface does not establish that either field must always be filled.
- Connect
cross_reference_graphto a compatible downstream input when assembling your workflow. This is not an output node, so simply placing it on the canvas does not make it a standalone preview or export step. - Keep
producer_reportavailable for inspection when troubleshooting. Do not judge the validity of identity relationships solely from whether the graph connection can be made.
H3 Cross Reference Producer Common Errors and Solutions:
Missing required input: reference_registry
- Explanation: This is a descriptive troubleshooting label, not a confirmed exception string from the supplied code. The node requires a reference registry connection and has no default registry.
- Solution: Connect the H3 Reference Registry output of type
H3_REFERENCE_REGISTRYtoreference_registry, using the registry associated with your admitted media.
Missing required input: media
- Explanation: This is a descriptive troubleshooting label. The node requires an admitted media result; an unconnected input does not supply the material needed for source-identity construction.
- Solution: Connect a compatible
H3_MEDIA_PRODUCER_RESULT, such as the H3 Media Admission Producer’smediaoutput, and verify that the upstream producer completes successfully.
Incompatible socket type
- Explanation: This is a connection-level troubleshooting description rather than a verified node-specific message. Raw images, audio, video, or plain text do not match the two required structured input types.
- Solution: Pass your references through the appropriate H3 registry and media-admission steps, then connect their typed results instead of connecting raw media directly.
Unsupported resolution or entity_kind value
- Explanation: The interface lists only
source_onlyandambiguousforresolution, andsubject,voice,object, andsceneforentity_kind. An externally edited workflow or programmatic call could supply a different value; the exact validation behavior is not shown. - Solution: Restore the values through the node’s dropdowns. For a baseline configuration, use
source_onlyandsubject.
Candidate values are rejected or do not behave as expected
- Explanation: The supplied class accepts candidate strings but does not show their validation rules or interpretation. There is no confirmed candidate-related error message in the provided source.
- Solution: Check the full error details and your installed builder’s candidate requirements. Test with the default source-only configuration and empty candidates, then introduce candidate values according to the documented conventions of your workflow.
Expected automatic identity matching does not occur
- Explanation: This is a limitation misunderstanding rather than necessarily an execution error. The node explicitly builds source identities without inferring semantic identities, so it should not be expected to recognize the same person, voice, or object across different sources automatically.
- Solution: Use this node for source-grounded identity organization. If your workflow needs semantic identity matching, handle that through a separately documented process rather than interpreting this graph as confirmation of a match.
