Skip to content
Destination contracts

Each destination defines a different release contract.

Select a neutral destination to inspect what its package must contain, how it is validated, and whether the handoff is manual or API-based.

Destination contracts09 PROFILES IN CONTEXT
Selected destination contract

Web CMS

Publish the approved Atlas Field Kit Web Hero with page title, alt text, campaign ID, and a locked 40:21 canvas.

Delivery profileWeb CMS Release
Channel specification
Format
WebP
Dimensions
2400 × 1260
Metadata
Page title · Alt text · Campaign ID
Naming rule
atlas-field-kit_web-hero_v03
Validation
Canvas, WebP signature, required fields, filename, rights
Failure route
Return to profile owner; do not create a release record
Handoff
Manual upload with PKG-0241 manifest
PKG-0241Ready
HANDOFF BOUNDARY

A destination label is not evidence of an integration.

Web CMS, Mobile App, Commerce Platform, Social Channel, Publisher Portal, Retail Partner, Partner API, Print, and Broadcast are fictional operational categories. Manual means a person transfers the validated package and records the receipt. API means an operated system would send references after validation. This public site does neither.