Artefact bundle
- UI workflow JSON and SHA-256
- Optional API-format JSON, labelled separately
- Model and custom-node manifest with source, licence, version and hash
- Non-sensitive input assets or their reproducible source
Four trust levels, each saying one thing
A higher level adds evidence; it does not erase model licences, security review or the limits of the tested machine.
| Level | Label | What has been checked | What has not been promised |
|---|---|---|---|
| DRAFT | Editorial reference | A guide or diagram may describe a graph. | No downloadable artefact, schema pass or execution result is implied. |
| UPSTREAM | Maintainer-provided | The workflow comes from official ComfyUI documentation, examples or template packages. | 42 UK has not necessarily reproduced it on local hardware. |
| SCHEMA | Machine-checked | JSON parses, matches its declared ComfyUI workflow schema and carries a dependency/model manifest. | Schema validity does not prove that dependencies install or the graph executes. |
| REPRODUCED | Execution receipt | A clean, recorded environment loaded and ran the hashed graph with expected output and logs. | Different software, hardware, models or inputs may behave differently. |
Current 42 UK status: no locally hosted workflow file passed the Schema or Reproduced gate during the 5 August 2026 review. Existing articles are listed as Draft references until an actual artefact and receipt exist.
Upstream workflow entry points
These are maintained by the ComfyUI project or its original examples repository. Follow the linked page for the current models and instructions; model downloads and licences can change independently of the graph.
| Workflow | Source | Nodes and inputs | How to obtain it | 42 UK status |
|---|---|---|---|---|
| Built-in Workflow Templates | Official template browser | Official templates are required to avoid third-party nodes; model requirements are embedded. | In ComfyUI: Workflow → Browse Workflow Templates. | UPSTREAM |
| Basic text to image | Official tutorial | Core checkpoint, text encoding, latent, sampler, VAE decode and save nodes. | Load the workflow asset from the tutorial and follow its current model instructions. | UPSTREAM |
| Inpainting | Official tutorial | Input image, mask and VAE Encode for Inpainting plus the normal sampling chain. | Download the workflow-bearing image from the tutorial and drag it into ComfyUI. | UPSTREAM |
| ControlNet scribble | Official tutorial | Core ControlNet loading and application; the tutorial provides a preprocessed input because core does not include every preprocessor. | Use the workflow-bearing image and exact model paths documented on the page. | UPSTREAM |
| SDXL examples | Original examples | SDXL text-to-image and related example graphs; requirements vary by example. | Download a displayed image containing workflow metadata and load or drag it into ComfyUI. | UPSTREAM |
| Two-pass “hires fix” | Original examples | Two-stage generation/upscaling examples; inspect each graph’s model requirements. | Load the metadata-bearing example image from the upstream page. | UPSTREAM |
Download the provenance register as CSV. “Upstream” records a maintainer source; it is not a local execution claim.
The upstream workflow_templates repository runs JSON, schema and bundle consistency checks in CI. That is strong provenance for its artefacts, but still not a claim that every model fits every local machine.
Load a workflow safely
A workflow is executable configuration. Inspect what it needs before installing whatever the graph happens to request.
- Start with provenance. Download from the linked maintainer page, not a re-upload with the same screenshot.
- Keep the original. Hash the JSON or metadata-bearing image before editing it.
- Inspect missing models. Confirm filename, source, licence and intended model directory before downloading.
- Inspect missing nodes. Core-only workflows are the cleanest baseline. For custom nodes, review the repository and install into the ComfyUI environment.
- Run locally first. Remove private paths, API keys and personal media before sharing or using a cloud service.
- Save a receipt. Record ComfyUI commit, workflow hash, dependency versions, launch flags, input hashes, outcome and output hash.
Useful upstream behaviour: ComfyUI saves a workflow in generated-image metadata when the format supports it, and a workflow can also be stored as human-readable JSON. Metadata is convenient; a separate versioned JSON file is easier to review and diff.
How a 42 UK workflow becomes “Reproduced”
The promotion gate is intentionally boring. Boring receipts survive enthusiastic prose.
Execution receipt
- Operating system, accelerator, driver, Python, PyTorch and ComfyUI commit
- Install route and exact launch flags
- Load validation, execution outcome, duration and complete error log
- Output dimensions, format, hash and embedded metadata check
- Parse JSON and detect the declared workflow version.
- Validate against the matching official ComfyUI workflow JSON schema.
- Reject absolute personal paths, obvious secrets and undeclared custom node classes.
- Build a clean test environment using the documented installation route.
- Load the graph without broken links or missing-node placeholders.
- Run once for setup and at least once as a measured reproduction.
- Verify output and store logs, hashes and the environment receipt.
- Display tested scope and date beside the download. Never silently carry a “Reproduced” badge across an untested dependency update.
UI workflow JSON and API format are different jobs
The editable UI workflow represents the visual graph. ComfyUI’s API documentation describes an API format with node IDs as keys and each node’s class_type and inputs. Publish the format name instead of making users infer it from a failed import.
| Format | Primary use | Validation | Library labelling |
|---|---|---|---|
| UI workflow JSON | Open, inspect and edit the visual graph in ComfyUI. | Match the declared official workflow schema, currently documented as workflow v1.0. | workflow-ui.json |
| API-format JSON | Submit a graph programmatically to a compatible ComfyUI API. | Confirm node classes/inputs against the tested server and execute a non-sensitive test request. | workflow-api.json |
| Metadata-bearing image | Carry a UI graph with an example output. | Extract the workflow, hash both files and check that sharing did not retain private data. | example-output.png |
42 UK workflow field notes
These pages are useful reading, but none is labelled as a validated workflow download on this hub.
- ComfyUI basics: nodes, models and workflowsDRAFT Editorial introduction; compare current interface details with official docs.
- AI image-generation workflow patternsDRAFT Pattern guide, not a hashed downloadable artefact.
- Nodes and optimisation deep diveDRAFT Candidate hypotheses need an isolated test receipt.
- Observer workflow field noteDRAFT Performance claims remain outside the benchmark dataset until reproduced.
Primary sources
These maintainer resources were checked on 5 August 2026.
- ComfyUI workflow conceptOfficial description of graphs, workflow JSON and embedded metadata.
- Built-in workflow templatesTemplate browser, model requirements and contribution rules.
- Official workflow template repositoryTemplate source, packages and automated validation.
- Workflow JSON specificationOfficial versioned schema for UI workflows.
- ComfyUI API workflow formatOfficial explanation of API-format graphs and job submission.
- Original ComfyUI examplesMetadata-bearing examples across image-generation techniques.