From d87cc7843e1ee6bbd75bf9b296239e1ee4a261dc Mon Sep 17 00:00:00 2001 From: Morpheus Date: Sat, 8 Aug 2026 21:45:19 +0000 Subject: [PATCH] Add Z-Image to optimization notes --- optimized/notes/process.md | 5 +++-- optimized/notes/zimage.md | 24 ++++++++++++++++++++++++ 2 files changed, 27 insertions(+), 2 deletions(-) create mode 100644 optimized/notes/zimage.md diff --git a/optimized/notes/process.md b/optimized/notes/process.md index 52da2b9..5e0cb5a 100644 --- a/optimized/notes/process.md +++ b/optimized/notes/process.md @@ -10,8 +10,9 @@ ## Current weekly review priorities 1. `flux2klein` -2. `ltx` -3. `minimax` +2. `zimage` +3. `ltx` +4. `minimax` 4. category masters in: - `image-edit` - `image-to-video` diff --git a/optimized/notes/zimage.md b/optimized/notes/zimage.md new file mode 100644 index 0000000..6eecc99 --- /dev/null +++ b/optimized/notes/zimage.md @@ -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`