The application name does not identify the model
Record the selected model while producing a brand asset. Do not infer it later from the fact that the work happened inside Firefly. Adobe's 10 November FAQ says AI Assistant can choose across Firefly and partner models unless a model is explicitly specified. That makes model selection part of the production brief.
Ian Dean's 15 November Creative Bloq commentary raises the practical communication problem: a familiar application name can conceal a meaningful change in the production route. The record below is my proposed studio workflow. It does not certify the legal status of an image or claim that all providers have the same terms.
Specify the route before generating the final asset
Decide which models are approved for exploration and which are approved for the intended deliverable. These can be different decisions. A quick internal composition test does not automatically become an approved campaign image when someone likes the layout. State the intended use alongside the selected model.
If the workflow requires an explicit model, make that selection part of the task and retain the available product evidence. Do not ask a generated image to reveal its own history. Where the interface or workflow does not expose a reliable record, mark the model unknown and resolve it before promoting the asset into the final set.
Keep a small record outside the exported image
Use one entry per chosen asset: file identifier, creation date, application, model as shown, reference permissions, significant edits, intended channels and reviewer. Save the relevant terms link with a review date. Keep prompt history or private reference material in the controlled working folder rather than a public delivery archive.
For a fictional product launch, an approved record could connect a final background image to a named generation route, two licensed reference photographs and a designer's compositing pass. The brand logo remains an approved vector file. That distinction helps a future editor replace the background without accidentally regenerating the identity.
Review the image and the production choice separately
A strong composition can still use an unapproved route. An approved route can still produce distorted packaging, invented lettering or an unsuitable visual association. Give the visual review and production review separate outcomes. Neither should disappear inside a single approved checkbox with no explanation.
Adobe distinguishes its Firefly-model commercial-use assurance from responsibility for assessing partner-model output suitability. Read the applicable provider documentation for the actual workflow. If a client needs a specific contractual answer, obtain that answer before delivery rather than treating a product badge as a substitute.
Deliver an asset another designer can maintain
The handover should identify which final files are approved, which editable components remain available and where the production record lives. If export metadata is cleaned for delivery, preserve useful provenance separately and leave visible credits intact. Metadata handling should not erase the working evidence behind a decision.
JQ's AI brand visuals work combines production choices with art direction. For a branding studio, begin with one campaign and a short approved-model record. The aim is an image set that remains understandable when the original chat and its creator are no longer available.
Link Map
Sources and editorial review
Assigned to the 10–16 November 2026 editorial series. This edition was prepared and source-checked on 16 November 2026; assigned dates do not imply prior public deployment. Proposed workflows and illustrative examples are JQ AI SYSTEMS editorial analysis, not completed client experiments.
- Adobe: Firefly AI Assistant FAQ (10 November 2026; primary product FAQ, dated update).
- Ian Dean, Creative Bloq: Is Firefly still the safe AI option? (15 November 2026; dated editorial commentary).