Use case 01
Use Multi Reference when the team needs reference-heavy edits without losing the same campaign memory that powers the rest of the platform.
Edit / Multi Reference
Use more than one source image or board when the route needs tighter visual grounding.
Multi Reference is the edit route for combining several source cues into one more controlled output without losing the original campaign language.
Multi Reference tied back to the active campaign
Source fusion visible enough to review clearly
More grounded revisions packaged as part of the same release flow
Reference fidelity kept inside the operating loop
Primary fit
Reference-heavy edits
Core control
Source fusion
Deliverables
More grounded revisions
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
Multi Reference is strongest when source fusion needs to stay visible and repeatable across more than one launch or format.
Use case 03
The route makes the most sense when more grounded revisions should move directly into reference fidelity 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 reference-heavy edits need
Use Multi Reference when the team needs reference-heavy edits but still wants the route attached to the same campaign spine and decision history.
02
Use source fusion as the main lever
The route is structured around source fusion, which helps teams move from direction into more grounded revisions without dropping context.
03
Close the loop through reference fidelity
The final step is not just generation. Multi Reference stays valuable because reference fidelity 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
Multi Reference fits teams working on reference-heavy edits. 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
Multi Reference is built around source fusion. That focus keeps the output narrower and more repeatable than a general-purpose generator surface.
03
How the route moves forward
Multi Reference should end in more grounded revisions, then feed directly into reference fidelity 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 Multi Reference?
Multi Reference is built for teams focused on reference-heavy edits who still want that work attached to the same campaign operating layer as briefs, references, review, and delivery.
What does Multi Reference control inside Hadogen?
The route is mainly about source fusion. That is the main lever it gives operators while still pushing toward more grounded revisions.
What should teams open after Multi Reference?
Most teams move from Multi Reference into Reference Extension once more grounded revisions is ready for reference fidelity or for the next step in the release cycle.