TL;DR: For a Node.js Express photo intake service, start with three application-owned checkpoints: transformation completed, OCR completed, and moderation decided. Report processed counts, original and delivery byte sizes, failures, and observed processing cost with transformation tags; keep a photo held until its required checks finish. Retry attempts need their own accounting. A successful compression count cannot tell a property manager whether a maintenance photo is safe to release or whether its text was extracted.
Consider this proposed page: property photo releases are stalled while the processing dashboard is green. The responder sees completed delivery copies, a growing set of photos awaiting decisions, and no clear distinction between a check that rejected content and a check that never completed. This is a design exercise, not an account of a production incident.…