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