Image Studio Asset Review

Draft asset boundary

Image Studio drafts should stay separate from approved WordPress Media Library assets until a human reviews quality, rights, product accuracy, brand fit, and placement. Do not import every variation just because it was generated.

Brand and rights review

Review brand kit settings, prompt, source provider, campaign intent, prohibited motifs, product claims, and whether the output could imply a third-party brand, protected design, celebrity likeness, or inaccurate product state. The Image Studio feature page explains the workspace, and the brand kit tutorial shows a controlled first workflow.

Media Library handoff

Approved assets should enter the Media Library with useful filename context, descriptive alt text, rights notes, and intended placement. The Media Library tutorial explains the handoff pattern.

Quick reference

• Use this page when turning repeatable WordPress, WooCommerce, marketing, support, reporting, agent, or tool work into a controlled process.
• Do not enable unattended write behavior, external calls, or customer-facing output before failure handling and approval ownership are clear.
• Key decision: whether generated assets have product accuracy, rights notes, alt text, owner, placement, and reuse limits before production use.

Scope limits

• Do not use this page to approve generated assets without rights, product accuracy, alt text, owner, placement, and reuse review.
• This page does not justify unattended execution when trigger scope, owner response, failure handling, or approval behavior is unclear.
• Use it to narrow repeatable work before expanding to write actions, external services, or customer-facing output.

Owner and cadence

• Primary owner: operations lead for the affected workflow, watcher, agent, playbook, or custom tool.
• Review cadence: before first run, after failed runs, after provider changes, and during monthly workflow review.
• Escalate when rights, product accuracy, brand compliance, likeness, or intended placement is uncertain.

Access and data boundary

• Image evidence should include prompt, source, rights note, product-accuracy check, alt text, asset owner, and intended placement before reuse.
• Grant workflow, watcher, playbook, agent, and custom-tool access by role, record type, launch surface, and risk level.
• Start with read-only, staging, simulation, or notification-only runs before allowing production writes, external webhooks, or unattended execution.

Production checklist

• Review prompt, brand kit, product accuracy, rights notes, alt text, intended placement, and campaign context before import.
• Keep rejected drafts out of the Media Library and out of production pages.
• Define trigger, owner, input data, output, approval requirement, retry behavior, failure notification, and kill switch before enabling a workflow.
• Start with read-only runs or staging examples until the team has reviewed successful traces and audit records.

Acceptance checks

• Only approved assets enter the Media Library with human-readable metadata and alt text.
• The asset owner can explain rights, source, prompt intent, and where the image will be used.
• The workflow or agent has a named owner who can pause it and explain its last run.
• Failures produce enough audit, diagnostics, and notification context for another operator to respond.

Failure modes to test

• Test inaccurate products, missing rights notes, rejected drafts, weak alt text, expired campaign context, and unsafe Media Library reuse.
• Test missing trigger data, duplicate runs, retry exhaustion, failed notifications, stale sources, permission denial, tool errors, and provider limits.
• Confirm write actions remain paused or approval-gated when simulation, staging, or first-run evidence fails.

Evidence to capture

• Capture prompt, source provider, rights note, asset owner, alt text, intended placement, expiry or reuse decision, and Media Library status.
• Record trigger, owner, input scope, affected records, approval point, run ID or timestamp, output artifact, and failure response.
• Capture simulation, staging, notification-only, or first production run evidence before expanding workflow scope.

Decision record

• Decision field to include: prompt, source, rights note, product-accuracy result, alt text, asset owner, placement, expiry, and reuse rule.
• Record the workflow decision, trigger, owner, input scope, output artifact, approval point, retry rule, failure notification, and kill switch.
• Include the first-run evidence, run ID or timestamp, cost expectation, expansion criteria, and the condition that keeps write actions paused.

Stop or rollback path

Keep assets out of the Media Library or archive them when rights, accuracy, brand fit, alt text, or placement is uncertain. Resume reuse only after metadata and owner approval are complete.

Monitoring window

• Monitor accepted assets, rejected drafts, rights notes, alt text, Media Library imports, and reuse decisions.
• Monitor first runs, retries, costs, failures, alert volume, queued work, and owner response time.
• Review run history before enabling write actions, more triggers, or broader records.

Expansion criteria

• Expand workflow execution only after first-run history shows expected output, manageable alert volume, known cost, and clear failure handling.
• Write-capable steps remain approval-gated until staging, simulation, or notification-only runs are stable.

Common mistakes

• Saving every generated variation to the Media Library without rights, alt text, brand, or placement review.
• Turning a useful prompt into automation before defining trigger, owner, input scope, approval rule, and failure handling.
• Ignoring noisy alerts or failed runs until operators stop trusting the workflow surface.

Common questions

When is a generated asset safe to reuse?

Reuse it only when product accuracy, campaign context, rights notes, alt text, owner, expiry, and placement are still valid.

Who should own this decision?

The operations owner should own the workflow, with specialist reviewers for customer, commerce, content, support, or tool impact.

What should stop the rollout?

Stop when trigger scope, owner, run state, approval behavior, failure response, or write capability is unclear.

Related operations

• Use Workflow Safety before enabling recurring workflows.
• Use Workflow Safe Mode and Kill Switches before production workflow rollout.
• Review Audit Log Review after the first production runs.
• Use Model Evaluation and Regression Review before broad agent or workflow rollout.
• Use Playbooks and Quick Actions for repeatable structured tasks.
• Use Prompt Template Governance before sharing reusable instructions.
• Use Playbook Import Export and Agency Reuse before reusing client workflows.
• Use Tool Validation and Schema Testing before exposing custom tools.