nano banana upscale image prompt: editing prompt

Define the transformation prompt brief behind nano banana upscale image prompt

For Nano Banana Upscale Image Prompt, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep model-specific prompts variants comparable instead of producing unrelated ideas. Name the source attributes that must remain unchanged, the single intended edit, protected identity or product details, and a reversible review path. Editing, swapping, or upscaling language is a proposed transformation and does not establish that a tool can perform it. Write the decision owner and intended handoff beside the brief so a search phrase cannot be mistaken for a verified product capability or an instruction that has already been executed. At handoff, preserve the claim inventory, and ask the factual editor to record source fidelity before the controlled revision.

Apply the model-specific prompts structure

Write a portable core prompt before adding any vendor or version vocabulary. Keep the subject, action, spatial relationship, shot order, continuity anchors, and end condition independent from a named model. Put model-specific controls in a separate dated note so an unsupported parameter cannot quietly become part of the creative brief. For “nano banana upscale image prompt”, keep a visible distinction between required content, optional treatment, exclusions, and facts that need evidence. That structure gives controlled variants a stable baseline and lets a reviewer identify which instruction caused a material change. At handoff, preserve the control log, and ask the delivery owner to record disclosure clarity before the source comparison.

• Portable shot contract Before delivery, preserve the continuity note, and ask the identity reviewer to record control availability before the bounded test.
• Dated model-control notes Before delivery, preserve the claim inventory, and ask the policy reviewer to record disclosure clarity before the bounded test.
• Version and access verification Before delivery, preserve the reference set, and ask the channel editor to record format readiness before the bounded test.

Prepare authorized inputs for image transformation and editing

This query calls for an untouched authorized source, the exact requested change, protected attributes, exclusions, and a before-and-after acceptance frame. Limit each pass to one visible transformation and record what must not change. Compare edges, texture, anatomy, lighting, scale, and provenance against the source. Record the source, permission, intended audience, protected details, and reviewer before testing language. The goal is a traceable creative proposal, not an assumption that a named platform, model, or workspace will perform the requested action. Before delivery, preserve the authorization record, and ask the creative lead to record temporal order before the bounded test.

Build controlled variants and observable acceptance checks

For this owner, the first review pass should make nano, banana, upscale, image observable rather than merely decorative. Change one meaningful dimension per version and label the hypothesis, invariant details, expected difference, and rejection condition. Approve only when the requested change is authorized, boundaries are explicit, identity and factual attributes remain faithful, and artifacts can be compared with an untouched source. Keep failed variants in the decision record so the final wording is explainable rather than selected by impression alone. Before approval, preserve the control log, and ask the channel editor to record format readiness before the delivery pass.

Review authorization, safety, and changing product facts

Do not bypass ownership marks, conceal provenance, alter identity without consent, or claim that an editorial prompt page performs the edit. The named third-party model or product requires dated first-party verification for identity, version, access, inputs, controls, limits, pricing, licensing, and output behavior; this page makes no comparison or SEELE availability claim. Treat every named model, competitor, access term, platform rule, identity use, commercial claim, and output specification as a dated evidence question. If authorization or first-party support is missing, keep the language editorial, stop the handoff, and record the unresolved gap instead of inventing a workaround. At handoff, preserve the control log, and ask the policy reviewer to record source fidelity before the fallback decision.

Approve a reversible prompt handoff

Confirm the exact provider, version, access surface, accepted inputs, controls, and output behavior against current first-party material before a test. A model name in a query is an evaluation target, not proof that SEELE or any other product currently exposes it. Before approving “nano banana upscale image prompt”, check purpose, source rights, identity consent, factual support, continuity, disclosure, destination requirements, and the named review owner. Preserve the original brief and version notes. This handoff supplies authored guidance only and neither runs generation nor guarantees access, quality, speed, licensing, publishing, downloads, or outcomes. At handoff, preserve the source ledger, and ask the policy reviewer to record revision intent before the acceptance review.