Deciding what must not change comes before the generation

The shot

A production can waste fewer generations by deciding, before requesting a shot, exactly which visual elements are not allowed to change. Luma Labs documents this practice directly for Dream Machine in two companion guides published under its Learning Hub: Master Reference Assets: Your Single Source of Truth and Character and Object Consistency. Both describe the same underlying method: define the immovable elements of a shot or project first, then treat every later generation as a variation that must be checked against that fixed reference rather than against the most recent output.

What the documents show

Luma's documentation names specific categories to lock before generating, including "a character's face, proportions, and wardrobe," "a specific lighting style," and a product's "exact physical design." It also names the failure mode this checklist is meant to prevent, in its own words: "a character's facial structure shifts slightly," or "a brand color drifts warmer or cooler," changes that are individually subtle but can compound across a sequence of iterations. This is a vendor's own documented production practice, not an independently tested claim about how well the checklist works; it is offered as guidance for using the product, not as a guarantee.

The workflow

Per Luma's guides, the checklist runs before generation begins: photograph or generate clean reference images of the subject from multiple angles on a plain background, one angle per image; convert each into a written description of shape, proportions, color, and defining features; write down the specific features that must not change; and then, for every later request, explicitly re-anchor the instruction to that saved reference rather than to the prior output. Runway's own Gen-4 Image References guide adds a compatible, narrower recommendation: use "a high-quality photo of your subject with even, natural lighting" and neutral expressions so later generations start from a documented "blank canvas."

What the tool does not change

None of the cited documentation claims this checklist is automatic or enforced by the software; Luma's own guide states that "consistency doesn't happen automatically. It's maintained deliberately," meaning a person still has to remember to invoke the fixed reference on every request and to catch drift when the checklist is skipped.

• Has someone written down, in one place, the specific features that must not change in this shot?
• Are the reference images clean enough -- one angle each, neutral lighting -- to serve as a real anchor?
• Is every new request being checked against that original reference, or against the last generated output?

This is an editorial checklist assembled from Luma's own published production guidance; it reduces wasted generations by moving a decision earlier, not by removing the decision.