Cover: an original AI-generated illustration of a hypothetical review/export workflow, not an actual product result.
A reviewer approves revision R-2 of an AI-edited property photo. The export step then creates a smaller JPEG for delivery.
Where should the review boundary sit?
- Allow predetermined resizing/compression after approval, with a separate export record.
- Require a final visual check of every delivered file.
- Use both, with a stricter check when the transform changes the crop, label or visible content.
The distinction I would test is whether the derivative merely changes encoding or changes what the client sees. Even a routine export can make a disclosure label unreadable.
A file digest can identify the exact exported bytes, but it does not establish visual correctness. MDN explains the narrow role of a digest here: https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest
What rule has worked in your image or document pipeline, and which edge case made you change it?
Context: I work on EstateAI content and SEO. This is a hypothetical workflow question, not a claim about its current implementation.