Create first optimized workflow masters

optimized/notes/minimax.md

@@ -0,0 +1,35 @@
+# MiniMax Notes
+
+## Current default assumptions
+
+- `MiniMax H3` is promising, but brute-force paths are too heavy to be the first bet on a `3070`.
+- Speed-first and low-VRAM community workflows matter more than official purity for the first real test.
+
+## Strong current source workflows
+
+- `models/minimax/minimax-h3-official-t2v/`
+- `models/minimax/minimax-h3-official-i2v/`
+- `models/minimax/minimax-h3-turbo-lora-community/`
+- `models/minimax/minimax-h3-int8-r2v-community/`
+
+## Strong current heuristics
+
+- Prefer Turbo LoRA for the first `text-to-video` attempt.
+- Prefer INT8-based community workflows for `reference-to-video` exploration.
+- Keep attention and memory-efficiency helpers if they are already integrated and well documented.
+
+## Current weak areas
+
+- No proof yet that MiniMax is truly practical on Chris's box.
+- Custom-node stack is more fragile than the current `flux2klein` path.
+
+## Best current optimization direction
+
+- Keep `optimized/text-to-video/minimax-h3-3070-turbo-master/` as the first MiniMax default.
+- Keep the INT8 reference-video workflow as the next donor for future low-VRAM optimization.
+
+## What needs Monday proof
+
+- whether the Turbo LoRA workflow is just technically possible or actually usable
+- whether the source-recommended `8`-step path holds up in quality
+- whether MiniMax feels like a real challenger to `LTX` locally