Defining the Boundary: Required vs. Optional

In professional retouching, there is a dangerous gap between a "beautiful preview" and a "reviewable source." A preview is the polished image you send to a client for approval. A source is the layered Photoshop (PSD) file that allows another designer to make changes.

The problem arises when generative AI is used to "bake in" changes—meaning the AI pixels are merged directly into the product layer. For example, imagine a high-end preview of an olive-oil bottle. At a glance, the lighting is perfect and the composition is stunning. However, when you zoom in to 200 percent, you notice the AI has slightly warped the serif on the label's font or shifted the shade of the oil.

Because these AI fills were merged down into a single flattened layer, the original, accurate product details are gone. The next designer cannot simply "undo" the warp; they must start the entire project over from the original photograph. To avoid this, you must treat the source as a legal record of the product, ensuring that no AI-generated pixel ever replaces a required product detail.

To prevent a file from becoming "baked-in," you must first identify your required assets. These are non-negotiable product details that must match the physical item exactly. If a required asset is altered—even slightly—the image becomes a misleading representation of the product, which can lead to legal issues or client rejection.

Consider our olive-oil bottle. The required assets include the exact font and spelling on the label, the specific golden-green shade of the oil, and the precise matte texture of the bottle cap. These elements are the "truth" of the product. If you use generative AI to expand a background and the tool accidentally "hallucinates" a different font weight or a slightly different oil color, you have compromised the required assets.

In your workflow, you treat these assets as untouchable. Before you ever open a generative tool, you list these specific details in your project brief. By explicitly marking the label, cap, and oil as required, you create a mental and technical boundary that tells you—and any designer who inherits your file—which pixels must be preserved at all costs.

While required assets are the non-negotiable 'truth' of the product, optional assets are the environmental or decorative elements used to fulfill the creative brief. These are the areas where you allow the AI to 'hallucinate'—to invent pixels that were never in the original photograph. Because these elements do not define the product itself, they can be changed, moved, or entirely generated without compromising the accuracy of the delivery.

Take our olive-oil bottle project. The client wants the bottle on a stone table outdoors in the late afternoon. In this scenario, the stone tabletop, the warm orange hue of the sunlight, and a decorative olive branch resting in the background are all optional assets. You aren't selling a specific stone or a specific branch; you are selling an atmosphere.

By identifying these as optional, you give yourself permission to use generative AI to iterate quickly. You can test five different types of stone or three different lighting angles in seconds. The key is to keep these optional assets on their own layers, separate from the required product, so the atmosphere can be swapped without ever touching the bottle.

Once you have identified what is required and what is optional, you must formalize a production boundary. This is not a visual line in the image, but a strict rule set in your project brief. A production boundary prevents 'hallucinations'—where the AI makes a statistical guess about a pixel—from bleeding into the areas that must remain accurate. Without this boundary, you risk the AI subtly changing a product's logo because it 'thought' the logo should blend with the background light.

For the olive-oil bottle project, your brief should include a clear split. Under a heading called "Untouchable," you list the bottle, the label text, the cap, and the oil color. Under a heading called "Generative," you list the stone tabletop, the ambient sunlight, and the decorative foliage.

By writing this down before you start, you create a technical constraint. When you later use a generative fill tool, you refer back to this list to ensure your selection masks are tight. If a prompt produces a beautiful result but alters a pixel in the "Untouchable" zone, the boundary tells you the result is a failure, regardless of how polished it looks.

The production boundary is enforced in Photoshop through precise selections. To keep your required assets untouchable, you must isolate the optional assets before using any generative tool. If you simply select a large area and prompt for a "stone table," the AI may attempt to "blend" the bottle into the stone, subtly altering the edges of your product—this is where hallucinations begin.

To apply the boundary concretely, imagine you need to generate a stone surface beneath your olive-oil bottle. Instead of selecting the whole bottom half of the image, you create a tight selection that wraps around the bottle's base, leaving a small, intentional gap of a few pixels. By ensuring the selection area contains only the background and zero pixels of the bottle itself, you tell Photoshop exactly where the generative boundary ends.

You then apply the Generative Fill to this specific area. Because the bottle pixels were never part of the selection, they remain identical to the original photograph. The AI creates the stone surface and the contact shadow in the selection zone, but it cannot reach across the boundary to warp your label or change your product's silhouette.

The final step before you ever touch a prompt is to categorize every element of your project. This process transforms a vague creative vision into a technical blueprint. By sorting elements into two distinct columns—Required and Optional—you eliminate guesswork. If an element is Required, it is a fixed constant; if it is Optional, it is a variable that the AI can solve for you.

Let's walk through a concrete example using a project list: 'Product Logo', 'Sunlight', 'Bottle Cap', and 'Background Foliage'.

1. Product Logo: This is a core identity asset. It must be placed in the 'Required' column because any AI-generated warp of the logo is a failure.
2. Sunlight: The mood of the light is a creative choice, not a physical product spec. Place this in the 'Optional' column.
3. Bottle Cap: The material and shape of the cap are product truths. Place this in 'Required'.
4. Background Foliage: The specific leaves in the background are decorative. Place this in 'Optional'.

You use this sorted list as your master checklist during the edit. If you find yourself adjusting a 'Required' asset with a generative tool, you know you have crossed the boundary and must stop.