Add Z-Image to optimization notes
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
# Z-Image Notes
|
||||
|
||||
## Current default assumption
|
||||
|
||||
- `Z-Image` is in scope for collection and optimization alongside `FLUX.2-klein`, `LTX`, and `MiniMax`.
|
||||
|
||||
## What to look for
|
||||
|
||||
- strong `text-to-image` workflows
|
||||
- reference and edit workflows
|
||||
- outpaint / inpaint workflows
|
||||
- high-quality upscaling or restoration-adjacent workflows
|
||||
- any workflow that clearly beats a comparable `FLUX` path in practical image quality or simplicity
|
||||
|
||||
## Current heuristics
|
||||
|
||||
- Prefer real workflow assets over showcase pages.
|
||||
- Favor workflows with clear node requirements and portable imports.
|
||||
- Treat `Z-Image` as especially relevant for image-generation and image-edit categories, not video categories.
|
||||
|
||||
## What still needs proof
|
||||
|
||||
- which `Z-Image` workflows are genuinely stronger than the best current `FLUX` image-generation paths
|
||||
- whether `Z-Image` should become a category-master candidate for `text-to-image` or `image-edit`
|
||||
Reference in New Issue
Block a user