Add optimized workflow notes layer

optimized/README.md

@@ -6,6 +6,8 @@ The `models/` tree stores collected originals and community finds.
 
 The `optimized/` tree stores the cleaned-up workflows built from analyzing what we have collected.
 
+The `optimized/notes/` tree stores accumulated optimization notes so future review passes can reuse prior judgments instead of re-reading every collected workflow from scratch.
+
 ## Purpose
 
 These workflows are intended to become the practical default choices for each category after comparing:
@@ -32,6 +34,17 @@ Each optimized workflow should have its own folder and usually include:
 - `README.md`
 - optional notes, screenshots, or benchmark artifacts
 
+## Notes layer
+
+Use `optimized/notes/` for durable working notes such as:
+
+- category heuristics
+- strong and weak source workflows
+- recurring node/version pitfalls
+- preferred model paths
+- unresolved test questions
+- "best current" assumptions waiting for proof
+
 ## Update policy
 
 This section is reviewed on a Sunday-evening cadence.

optimized/notes/README.md

@@ -0,0 +1,13 @@
+# Optimization Notes
+
+This folder is the working memory for the optimized workflow layer.
+
+Use it to capture:
+
+- what looks strong
+- what looks weak
+- what settings seem worth preserving
+- what still needs live proof
+- what should be ignored next time
+
+These notes exist so future review passes do not have to re-trawl every collected workflow from scratch.

optimized/notes/flux.md

@@ -0,0 +1,37 @@
+# FLUX Notes
+
+## Current useful collected workflows
+
+- `models/flux/all-in-one-fluxdev-v0-2/`
+- `models/flux/flow-upscaler/`
+- `models/flux/flux-fill-inpainting/`
+- `models/flux/flux-redux-reference-restyle/`
+- `models/flux/flux-union-controlnet/`
+
+## Current strongest roles
+
+- `flow-upscaler`:
+  - strongest practical upscale-oriented FLUX workflow so far
+- `flux-fill-inpainting`:
+  - cleanest dedicated edit/inpaint route
+- `flux-redux-reference-restyle`:
+  - good reference-led variation / restyling baseline
+- `flux-union-controlnet`:
+  - strongest structure-control baseline
+- `all-in-one-fluxdev-v0-2`:
+  - useful as a source mine, not necessarily as a final master
+
+## Current heuristics
+
+- Prefer clean specialist graphs over giant all-in-one graphs when building optimized masters.
+- Use big all-in-one graphs as idea mines for nodes/settings, not as the final default.
+- Control, edit, and upscale workflows matter more than plain text-to-image for the current interest group.
+
+## Best current optimization direction
+
+- `optimized/upscale-restoration/` should likely borrow first from `flow-upscaler`
+- `optimized/image-edit/` should likely compare:
+  - `flux-fill-inpainting`
+  - `flux-redux-reference-restyle`
+  - `flux-union-controlnet`
+- `all-in-one-fluxdev-v0-2` is the place to steal useful sub-ideas if a cleaner graph needs a missing feature

optimized/notes/flux2klein.md

@@ -0,0 +1,50 @@
+# FLUX.2-klein Notes
+
+## Current default assumptions
+
+- Chris uses `FLUX.2-klein 9B`.
+- Prefer `9B fp8` paths first.
+- `GGUF` is not the default path unless it is the only strong or practical workflow route.
+
+## Strong current source workflows
+
+- Official Comfy `image edit` templates:
+  - `image-edit-9b-base`
+  - `image-edit-9b-distilled`
+  - `image-edit-4b-base`
+  - `image-edit-4b-distilled`
+- Current best outpainting starter:
+  - `models/flux2klein/image-edit-4b-distilled/`
+  - Reason: official, current, and easiest first test even though Chris's main stack is `9B`
+- Community Hugging Face workflow worth remembering:
+  - `models/flux2klein/community-gguf-kv-yarvixpa/`
+  - Interesting because of KV-cache / GGUF optimization ideas, not because it is the default path
+
+## Strong current heuristics
+
+- Prefer official Comfy templates as the baseline unless a community workflow clearly improves something real.
+- For `9B`, watch closely for text-encoder mismatches.
+- Community `9B` optimization notes often revolve around:
+  - low-step usage
+  - `CFG=1`
+  - cleaner model/text-encoder pairing
+  - avoiding broken loader substitutions
+
+## Current weak areas
+
+- We still do not have a clean, trusted, explicitly labeled `9B fp8 outpainting` community workflow import.
+- Some public workflow pages mention outpainting but do not expose a trustworthy raw workflow asset.
+
+## Best current optimization direction
+
+- Build future `optimized/image-edit/flux2klein-9b-master/` from the official `9B` edit template family first.
+- Borrow only proven improvements from community sources:
+  - cleaner graph organization
+  - low-step settings when they are clearly validated
+  - better reference/outpaint control if portable
+
+## What needs Monday proof
+
+- Whether `9B distilled` or `9B base` is the better real default for edit/outpaint on Chris's setup
+- Whether a `4B distilled` outpaint starter still beats `9B` in practical iteration speed enough to matter
+- Which custom-node optimizations are real versus noise

optimized/notes/process.md

@@ -0,0 +1,34 @@
+# Optimization Process Notes
+
+## Standing rules
+
+- Always `git pull --ff-only` before changing the repo.
+- Prefer practical gains over clever complexity.
+- Do not claim "optimal" when the evidence is still thin; "best current" is acceptable.
+- Prefer removing dead branches, duplicated wiring, and stale custom-node clutter.
+
+## Current weekly review priorities
+
+1. `flux2klein`
+2. `ltx`
+3. `minimax`
+4. category masters in:
+   - `image-edit`
+   - `image-to-video`
+   - `text-to-video`
+   - `text-to-image`
+   - `upscale-restoration`
+
+## Current repo split
+
+- `models/` = collected originals and community finds
+- `optimized/` = maintained masters
+- `optimized/notes/` = accumulated reasoning and unresolved questions
+
+## What to record after each Sunday review
+
+- Which optimized categories changed
+- Which source workflows influenced the update
+- What was removed
+- What was kept
+- What still needs Monday testing