Paper Relief private preview · public release in preparation · local-first

Local desktop delivery companion

Delivery Verify by Emulyn

Validate a declared photography delivery or handoff against a versioned job contract and produce repeatable evidence before it leaves the studio.

Coming soonCheckout and download closed

Who it is for

Studios, retouchers, production teams, photographers, labs, and commerce teams handling repeatable deliverables.

The workaround it improves

Manually opening folders, comparing spreadsheets, and relying on memory for recipient, lab, archive, and retouch-return requirements.

Product proof

Interface and demonstration assets

Placeholders are marked honestly until rights-cleared release assets are approved.

Marked placeholder

Delivery Verify pass warning and blocked states placeholder

Marked placeholder

Delivery Verify demonstration placeholder

Exact product contract

Inputs, outputs, reads, and writes

Every Emulyn product keeps its own boundary.

Supported inputs

  • Explicit job contract
  • Versioned rules and profiles
  • Declared delivery manifest
  • Supported local file and metadata observations

Produced outputs

  • Human-readable evidence report
  • Structured evidence report
  • Pass, warning, blocked, unsupported, and needs-decision states

What it reads

  • Declared manifests, contracts, rules, and profile metadata
  • Bounded local file and directory observations required by the active module

What it writes or changes

  • Declared evidence and report files only
  • No silent overwrite, quality judgment, catalog mutation, or undeclared file change

Local, catalog, file, and network behavior

Nothing important stays implied.

Catalog read
The core desktop verifier does not require direct Lightroom catalog access; any future Lightroom companion remains separately bounded.
Catalog write
No catalog write is authorized.
Direct .lrcat access
Never
File creation
Creates only explicitly requested evidence and report outputs using non-overwriting behavior.
Network
No delivery contents, filenames, paths, client names, or rights values are uploaded by default.
Privacy
Job contracts and delivery observations remain local unless the user deliberately exports or shares a report.
Exceptions and ambiguity
Unsupported rules, incomplete profiles, stale requirements, and uncertain observations are reported as blocked, unsupported, or needs decision.
Recovery
Evidence writes use explicit destinations and no-overwrite boundaries; the product does not claim transactional rollback of external jobs.

What it checks, creates, or changes

  • Contract and manifest conformity
  • Retouch-return requirements
  • Commerce asset-matrix requirements
  • Lab-owned delivery profiles
  • Bounded archive and migration observations
  • Retouch handoff and return state

What it deliberately does not do

  • Judge retouch or photographic quality
  • Invent recipient or lab rules
  • Copy, synchronize, relink, repair, or guarantee a backup
  • Silently overwrite files
  • Open a .lrcat database

Included modules

One parent product. No extra SKUs.

These modules share the parent product’s release, license, and checkout. They are not sold separately.

Included

Retouch Returns

Check declared retouch-return IDs, names, counts, formats, dimensions, profiles, and requirements without judging retouch quality.

Included

Lab Delivery

Check against sourced, dated, versioned, lab-owned rules while making stale or unverified profiles visible.

Included

Commerce Asset Matrix

Check declared SKU, variant, view, crop, channel, naming, and deliverable presence against a structured matrix.

Included

Archive & Migration

Check bounded source and destination observations, paths, collisions, hashes, and post-move state without claiming to copy or guarantee a backup.

Included

Retouch Handoff

Present the handoff manifest and required return state, then produce a compatible return report without judging retouch quality.

Exact compatibility

Tested rows only.

Compatibility policy
No public compatibility row is authorized yet.

Private engineering evidence does not become a public support claim until the exact product, host, OS, architecture, and release row pass review.

Known limitations

What still has to be true.

  • The shared contract-and-evidence engine and five modules are not yet unified into a customer release.
  • Studio-tier capabilities are not built and the Studio offer is disabled.
  • Representative external rule owners and jobs remain required.

Installation

Desktop and any included Photoshop companion installation instructions will ship with the exact authorized packages.

Update policy

Proposed one-time major-version license with 12 months of maintenance; legal review remains required.

Policy language remains subject to legal review before public activation.

Frequently asked questions

Clear answers before checkout.

Does Delivery Verify decide whether retouching looks good?

No. It checks declared technical and handoff requirements, not subjective image quality.

Are lab rules supplied by Emulyn?

A lab profile must identify its source, owner, version, and date; Emulyn does not independently certify a lab's requirements.

Support and release

Coming soon means exactly that.

Review licenses, affiliate eligibility, checkout, download, sitemap indexing, and structured product data remain disabled until this product’s release gate passes.

Ask about Delivery VerifyCompare other tools
Evidence describes supported observations against a declared contract and is not a guarantee of recipient acceptance. Emulyn is independent from Adobe and is not endorsed, sponsored, or certified by Adobe.