Adobe Production Readiness Decision

Overview

Issue an evidence-backed production decision across Adobe auth, entitlements, API versions, data custody, async reliability, spend, observability, and rollback. This workflow produces a reviewable artifact and evidence before any live side effect.

Prerequisites

• Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle.
• Named product, identity, security, data, budget, release, and operations owners appropriate to the scope.
• Synthetic or approved non-production fixtures with secret and content canaries.

Current Contract

A launch is ready only when the deployed artifact and actual organization/project/workspace, credentials, product profiles, service versions, storage, queues, events, monitoring, support, and rollback are evidenced together. Passing a token call or happy path is insufficient. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

Verify secret lifecycle, user consent if applicable, least privilege, entitlement, rotation, revocation, and environment isolation. JWT, Photoshop v1, and retired Lightroom Firefly Services references are launch blockers.