04

Destination contracts

A destination is a contract, not a folder.

A release profile states what must be present, what blocks the package, and whether the final handoff is manual, portal-based, or API-shaped.

Release profile explorer

Inspect what Ready means for one destination.

The local selector changes the example contract in the browser. It does not transfer a file or claim a live destination integration.

Destination contractLocal example
Owned digital

Web CMS

Profile current
Output
WebP · 2400 × 1260
Metadata
Alt text · page context
Handoff
Manual package
Blocks release
Source version + alt text
PKG-0241 · DEC-0318-Aatlas_keyvisualWeb CMS

Nine destination categories

Name the requirement without implying a platform partnership.

The categories remain generic. Each record still exposes an output, metadata set, handoff mode, and validation blocker.

01
Web CMSOwned digital

WebP · 2400 × 1260

Source version + alt text

02
Mobile AppOwned digital

AVIF · 1440 × 2560

Safe area + locale

03
Commerce PlatformCommerce

JPG · 1600 × 1600

Square crop + product code

04
Social ChannelSocial

MP4 · 1080 × 1350

Duration + safe area

05
Publisher PortalPartner

ZIP · renditions + manifest

Manifest + rights scope

06
Retail PartnerPartner

ZIP · mixed media

Naming + required files

07
PrintPhysical

PDF · CMYK

Color profile + trim

08
BroadcastVideo

PNG frame · 3840 × 2160

Safe area + caption link

09
Partner APIPartner

JSON manifest · asset references

Schema + current IDs

Replacement path

A new source version invalidates the package before it changes the destination.

Trace how Version 03 supersedes the earlier rendition and blocks PKG-0240.