GDP can stage a validated image in a private review queue without writing the repository. Inspect the exact target and preview in Desktop, then explicitly Apply or Reject the pending item locally.
Stage the image for review
An AI-facing image-asset request stages one validated PNG or JPEG for the exact selected GDP repository. It creates a durable Image Asset Review item and records the intended repository-relative target, operation, image dimensions and SHA-256; it does not write the target file.
The target always stays inside the selected repository. A normal repository-path source is read from that same repository; when the current tool exposes source_repo_id, GDP can instead read a safe repository-relative PNG or JPEG from another repository that is already open in GDP while keeping that source repository read-only for this operation. GDP rejects unknown or closed source repositories, absolute or traversal paths, unsafe symlinked locations, blocked sensitive path components, mismatched file extensions, invalid images and oversized payloads.
Create is for a target that does not already exist.
Replace is for an existing image and requires explicit overwrite intent.
Queueing the review item is not repository apply evidence.
Use explicit source_repo_id for a reviewed cross-repository source when that field is present; never emulate it with absolute paths, traversal, shell copy, or invented Base64 transport.
Cross-repository sourcing does not widen apply authority: only the selected target repository receives the pending review item and any later local Apply.
Inspect the validated preview
Open GDP Desktop's Image Asset Reviews surface for the intended repository.
Select the pending item and confirm the exact target path, Create or Replace operation, format, dimensions, byte size and SHA-256 shown by GDP.
Inspect the local preview for the image you actually intend to write.
For public or shared documentation assets, separately review visible account, repository, local-path, conversation, credential, token and other sensitive data before publication.
Technical image validation and Help/publication sensitive-data review are different checks. A valid PNG or JPEG can still be inappropriate to publish.
Apply or reject locally
Apply and Reject remain explicit GDP Desktop actions. The AI-facing submit operation does not expose remote apply or reject authority. When you choose Apply, GDP revalidates the pending operation before writing and verifies the resulting image SHA after the atomic file replacement.
A queued Replace is also protected against stale review: if the existing target disappears or changes after the item was staged, GDP fails instead of silently overwriting a different file state.
Apply only after the preview and exact target are correct.
Reject the pending item when the image, destination or intent is wrong.
After Apply, use fresh repository/image evidence before claiming the asset exists at its target.
For Help screenshots, registry metadata and article evidence are still separate publication requirements after the repository image exists.
