Newsletter header image

Branch logic

• If the user has not provided newsletter topic, ask 用於 it before generating the final header image.
• If a reference image is provided, preserve the subject identity, proportions, 和 important details before changing style 或 scene.
• If the first result fails 視覺 inspection, fix the smallest broken area first instead of regenerating the whole image.
• If the first tool path fails, switch to the next listed option: Ideogram, Recraft.
• If the task depends on masks, text, 或 object edges, inspect those details at full size before accepting the 輸出.
• If the image will be 已發布 commercially 或 publicly, run the risk guardrails before export.

When not to use

• Do not use this as proof that the generated header image is factually real 或 legally approved.
• Do not use it when the user needs professional legal, medical, safety, 或 regulated-compliance judgment.
• Do not publish the result until 權利, consent, authenticity, 和 platform constraints have been checked.

• The final asset clearly matches the requested header image.
• The main subject still reflects the original newsletter topic.
• Text, hands, logos, edges, 和 產品細節 are not visibly broken.
• The result is usable in the target channel 且不 another full regeneration.
• Proofread all 可見 text, labels, logos, 和 small typography before using the final image.