Start creating
Menu
Start creating

Tool / Graph review packet / task entry

ComfyUI Graph Review Generator

ComfyUI Graph Refinement Generator turns source records into reproducible execution packets.

Custom direction0 characters
TemplatesChoose one to replace the prompt above. You can switch at any time.
Review structured video direction
Video task: ComfyUI graph review planner
Creative brief: 
Deliverable: Short concept sequence
Aspect ratio / frame: 16:9 landscape
Shot direction: Keep subject, action, setting, camera behavior, and ordered beats explicit.
Continuity: Preserve identity, wardrobe, objects, geography, lighting direction, and movement across the sequence.
Review criteria: Confirm the sequence serves the brief, respects rights and factual boundaries, and is ready for the intended delivery frame.

Prepared workflow

From brief to reviewable handoff.

Prepare a ComfyUI graph review packet with provenance, dependency pins, security gates, fixture inputs, run logs, failure codes, and a reproducibility disposition.

  1. 01

    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
  2. 02

    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.

  3. 03

    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.

Capability boundary

Dated evidence

Sources behind the current facts.

Product and model details can change. These links identify the evidence checked for the claims scoped below.

  1. X / the public discussion signalMiniMax H3 ComfyUI workflow representative X circulation post

    Representative URL for circulation in the recorded X window only; it is not SEELE, model, integration, specification, availability, quality, repeatability, adoption, campaign, or commercial evidence.

  2. MiniMaxMiniMax H3

    Official model variants, input and output specifications, architecture, open-weight checkpoints, hosted module boundaries, recommended workflows, safety notes, and community license link.

Reader notes

Before you hand off.

Does this planner install or execute a ComfyUI workflow?

No. It prepares an auditable artifact, dependency, security, fixture, run, and disposition specification for execution in an authorized isolated environment.

What should happen when a node version is missing?

Mark the dependency unresolved and request the publisher's version or a documented compatibility range. Do not pick a current release and present that substitution as reproduction of the supplied graph.

Adjacent task planners

Continue the workflow

Take a prepared brief into the workspace.

Open the current SEELE Film & CG workspace to verify the exact model label, access, inputs, controls, region, entitlement, and output handling before applying this prepare a provenance and reproducibility review packet for a ComfyUI graph method.

Try it free