Workflow contract
- Export an API-compatible workflow without credentials or local file paths.
- Name required inputs, defaults, validation limits and outputs.
- Define output formats, size limits and failure responses.
ComfyUI on RunPod
A workflow that runs locally is a starting point, not yet a production endpoint. Use this checklist to make its dependencies, inputs, outputs and release behaviour explicit before it serves an application.
01 · Contract
02 · Reproducibility
Record the ComfyUI revision, custom-node commits, package versions, model files and hashes used by the candidate. Avoid mutable tags and floating package ranges.
Check model, node and code licences against the intended use. Keep source links and required notices with the candidate. This is technical inventory, not legal advice.
03 · Runtime evidence
04 · Release
Attach an immutable image digest, supported GPU profiles, reference-test results, known issues and documented changes to the candidate.
Keep the previous verified image available and document the endpoint change needed to restore it. A successful SEO publication is not commercial runtime clearance.
Technical fit review