Normalize and compose photos for reuse

Why use this

1. A simple image reuse request can become awkward when orientation metadata and visible rotation disagree, or two photographs have very different aspect ratios. Matching their heights can accidentally crop an important subject or enlarge one image beyond an acceptable quality level.

2. A transformation preview could make those tradeoffs explicit before replacing files. The owner could compare the proposed rotation or composition against the originals and decide whether padding, cropping or unequal visual emphasis is acceptable.

Why an agent / simpler alternative

Useful judgment

Interpret the intended visual arrangement and identify when a mechanical size match would damage the composition.

Simpler alternative

Use a photo editor's rotate or side-by-side layout command when the desired transformation is straightforward.

Unsuitable when

The task depends on guessing missing image content or overwriting the only original.

Proposed inputs

1. Name

   Selected image copies

   Owner

   Photo owner

   Minimum scope

   Only the requested files with stable identifiers

   Quality check

   Record dimensions, orientation metadata and original locations.

2. Name

   Layout brief

   Owner

   Requester

   Minimum scope

   Rotation direction, ordering, target size and crop tolerance

   Quality check

   Clarify whether subjects must remain fully visible.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only originals and a separate proposed output path with no clipboard access.

Compatibility unknowns

1. Unknown: current runtime, image-decoding support, color handling and clipboard behavior.

External actions requiring approval

1. Overwriting originals, clipboard replacement and sharing the resulting images.

Expected deliverable and review checks

Proposed artifact

Transformation manifest and proposed preview checklist for orientation, alignment and retained content.

Critical checks

1. The intended upright orientation agrees with visible content and metadata.

2. Composition preserves required subjects and does not distort proportions.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   Rotation is applied to pixels and then repeated by metadata.

   Why it matters

   Different viewers may display the result incorrectly.

   Proposed response

   Flag the orientation conflict and require a consistent metadata policy before export.

2. Signal

   Height matching enlarges the smaller image substantially.

   Why it matters

   One side may appear soft or visually unbalanced.

   Proposed response

   Offer a smaller canvas or padding option for owner review.

Effort and cost — unknown

Setup work

1. Identify originals and define allowed transformations.

Ongoing review

1. Inspect orientation, crop boundaries and export quality.

Unknowns

1. Unknown: processing charges, supported formats and color-profile fidelity.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Two invented image descriptors specify different dimensions, a rotation flag and a subject touching one edge.

Acceptance checks

1. Propose an aspect-preserving layout.

2. Flag the orientation conflict and any crop touching the subject.

Stop conditions

1. Actual image editing, clipboard use or file replacement is needed.

Limits

1. The proposed check evaluates a transformation plan only; it cannot establish resulting pixel quality.