ComfyUI Graph Review Generator

Register the artifact and its trust boundary

Give the workflow a stable review identifier and record its public source URL, publisher, retrieval timestamp, graph filename, byte hash, declared license, documentation, and claimed model family. Store the graph unchanged as the review input; make edits only in a separately identified copy. Add an attribution row for every linked repository, checkpoint host, package index, download script, and external endpoint. Classify each item as first-party model material, ComfyUI core, community extension, local configuration, or unresolved. The packet should state explicitly that an H3 label does not convert a community graph into a MiniMax or SEELE artifact, and that the public discussion signal contributes no security, compatibility, or runtime assurance.

• Immutable graph identifier and hash
• Publisher and retrieval record
• Dependency owner and license
• Trust classification and unresolved items

Pin the executable environment before a run

Create rows for the ComfyUI revision, runtime language, framework, accelerator stack, operating system, extensions, commits, model filenames and hashes, encoders, decoders, audio modules, preprocessors, environment variables, ports, file paths, and expected resources. For every custom node, capture its repository and install behavior, then require a source review or approved sandbox disposition. Use placeholder names for secrets and record only the required permission scope; never embed live tokens, cookies, credentials, proxy details, or private paths. If the graph depends on an unavailable file, incompatible version, ambiguous model, or undisclosed service, record a blocked state rather than silently swapping in another component.

Specify the reproduction protocol and closeout

Choose a rights-cleared fixture, expected graph validation result, run budget, timeout, output directory, logging level, and acceptance criteria before execution. Capture the resolved workflow, environment lock, input hashes, visible parameters, random-state setting when available, terminal output, errors, output hashes, and manual review notes. Use consistent failure codes for missing dependency, version conflict, load failure, invalid input, runtime fault, nondeterministic setup, unsafe behavior, or result outside the declared review scope. Close with reproducible, conditional, blocked, or not reproducible; name the reviewer, date, exact environment, remaining risks, and the change that would justify another attempt. The disposition applies only to that packet, not to H3, ComfyUI, SEELE, or a vendor generally.