Cover imagery

A deck’s cover image is generated from the deck’s own subject and your brand. It arrives after the deck is already finished, which is what keeps a slow or unavailable image model from holding up a presentation you asked for.

The order this happens in

1. The plan writes the deck and saves it. At this point the deck is complete and previewable, wearing the cover its style pack builds out of your brand colours.
2. The plan asks for a cover image and stops waiting. The deck is already usable, so nothing blocks on the answer.
3. When an image comes back, it is attached as a new version of the deck, and that version is re-rendered. The preview and the downloads pick it up on their own.

Because the image is a new version rather than an edit, the deck you already had is never modified in place. If a newer version of the deck exists by the time the image arrives, the image is dropped rather than applied to something it was not drawn for.

What the image is drawn from

The prompt comes from the deck’s title and the resolved theme, so the cover reflects both what the deck is about and how your brand looks. Alpenglow’s is cold blue ridgelines with a single warm band, which is the palette and the imagery guidance from its profile, not a stock mountain.

The imagery you rule out is respected by writers, not by the generator

Visual › Imagery guidance is part of the profile every agent reads. The cover generator works from the deck’s title and theme, so treat a generated cover as a draft: if it is wrong for you, the honest fix is to switch off generation and put your own image on the cover.

When there is no image

Cover generation needs an image model to be configured and reachable. When it is not, or when the request fails for any other reason, three things are true:

• Nothing breaks. The deck stays exactly as it was: Ready, previewable, and downloadable.
• The cover is the pack’s own. A style pack builds its cover out of your brand colours, so a deck with no generated image still looks like yours. It is a designed cover, not a blank rectangle or a placeholder.
• The render report says so. The report for that version records the cover image as failed, which is the only place the difference is visible.

There is no retry. Asking for the deck again is the retry, and it costs one more image request rather than a queue of them.

Turning it off

Cover generation follows the image model your workspace has configured. With no image provider configured, every deck simply uses its pack cover, and no request is made.

Next steps

• How a deck picks up your brand: what the pack cover is built from.
• Export formats: where the cover ends up in each output.
• Generate a deck: the pipeline this hangs off.