Use case 01
Use Flux 2 when the team needs model-specific image lane without losing the same campaign memory that powers the rest of the platform.
Image / Flux 2
A model-focused still route for teams comparing image engines inside the Hadogen operating layer.
Flux 2 gives teams a model-specific page for still generation while keeping the work tied to the same campaign context as the rest of the platform.
Flux 2 tied back to the active campaign
Engine selection visible enough to review clearly
Model-led stills packaged as part of the same release flow
Visual behavior kept inside the operating loop
Primary fit
Model-specific image lane
Core control
Engine selection
Deliverables
Model-led stills
Use cases
What teams actually use this route for.
These pages are now filled as operating surfaces, not placeholders, so each route explains where it fits inside the wider Hadogen workflow.
Use case 02
Flux 2 is strongest when engine selection needs to stay visible and repeatable across more than one launch or format.
Use case 03
The route makes the most sense when model-led stills should move directly into visual behavior and then into a broader Hadogen release package.
Route sequence
The route is structured around concrete operating moves.
This is the sequence teams typically follow when they use this route as part of a broader campaign system.
01
Start from the model-specific image lane need
Use Flux 2 when the team needs model-specific image lane but still wants the route attached to the same campaign spine and decision history.
02
Use engine selection as the main lever
The route is structured around engine selection, which helps teams move from direction into model-led stills without dropping context.
03
Close the loop through visual behavior
The final step is not just generation. Flux 2 stays valuable because visual behavior remains visible inside the same release cycle.
How it works
The route is broken into modules that map to real production decisions.
Each module explains what this lane controls, where it fits, and how it connects to the wider Hadogen system.
01
Where the route fits
Flux 2 fits teams working on model-specific image lane. The route becomes more valuable when that job stays tied to the same campaign context as the rest of Hadogen.
02
What the route actually controls
Flux 2 is built around engine selection. That focus keeps the output narrower and more repeatable than a general-purpose generator surface.
03
How the route moves forward
Flux 2 should end in model-led stills, then feed directly into visual behavior and the wider campaign system instead of stopping as a disconnected draft.
Related routes
Move deeper through the platform without leaving the same campaign logic.
FAQ
Questions teams usually ask before they use this route.
Who should use Flux 2?
Flux 2 is built for teams focused on model-specific image lane who still want that work attached to the same campaign operating layer as briefs, references, review, and delivery.
What does Flux 2 control inside Hadogen?
The route is mainly about engine selection. That is the main lever it gives operators while still pushing toward model-led stills.
What should teams open after Flux 2?
Most teams move from Flux 2 into GPT Image 1.5 once model-led stills is ready for visual behavior or for the next step in the release cycle.