MRGI PIXEL / WORKFLOW FIELD GUIDE
Prepare a three-format campaign
Deliver a coherent set of landscape, portrait, and square assets from the same creative brief.
01 / FROM INPUT TO HANDOFF
Follow the decisions.
This walkthrough describes the intended MRGI product behavior. The browser demo illustrates a small part of the workflow; it does not run the complete application.
- 01
Select approved sources
- Start with
- A fictional landscape illustration and brand package.
- Work through
- Choose the asset versions and record the campaign constraints.
- Result
- A defined creative input set.
- 02
Build variations
- Start with
- Landscape, portrait, and square placements.
- Work through
- Apply the recipe and adjust focal framing where needed.
- Result
- A candidate set of format-specific images.
- 03
Inspect exceptions
- Start with
- The candidate set and safe-area rules.
- Work through
- Review clipping, readability, required assets, and visual consistency.
- Result
- Approved variations and a list of corrections.
- 04
Release the batch
- Start with
- The reviewed images and recipe.
- Work through
- Package the outputs with their source and processing references.
- Result
- A traceable campaign delivery.
02 / INPUTS & INTERCHANGE
What travels with the work.
These are foundation formats and intended handoff contracts. Support and fidelity must be confirmed for each released build.
| Artifact | Role | Review consideration |
|---|---|---|
| PSD / PSB | Layered editing foundation | Layer effects, color profiles, and complex documents need fidelity testing. |
| Raster exports | Campaign deliveries | Dimensions, alpha, color profile, and compression settings are target-specific. |
| Brand package | Line handoff | The recipe should pin a reviewed asset version. |
A deliberate cross-app boundary
Use approved Line brand assets and Lens photos, then deliver reviewed variations to Layout.
The intended handoff should identify the selected resource, its version, the destination, and the user’s authorization. A linked application should not inherit unrestricted file access.
Explore the connected applications ↗03 / BOUNDARIES & READINESS
Know what this example establishes.
- The browser illustration is synthetic, not a processed customer image.
- Automated visual checks cannot decide artistic quality.
- Deterministic recipes require stable assets, engines, fonts, and color settings.
Development status
The source foundation is imported. Constrained recipes, visual QA, and the redesigned creative interface are planned.
Before a production release
Validate real-file behavior and platform support, implement the stated authorization and review rules, and document the tested acceptance scope. The interactive website is a product demonstration, not a release candidate for the application.
04 / PRODUCT QUESTIONS
The details that matter.
Will every crop be automatic?
The proposed recipe can prepare candidates and flag exceptions. Subject placement and creative quality may still require manual adjustment.
Does the preview generate images with AI?
No. The preview is a local canvas drawing with geometric shapes and adjustable framing.
Open-source foundation
Layer, mask, adjustment, PSD/PSB, and batch action code exists in PhotoCraft. MRGI is proposing campaign acceptance and provenance workflows, not claiming batch editing itself is new. Read the credits and foundation mapping.
Keep exploring Pixel.
Return to the product breakdown or try the local interactive example.