Adobe Integration Reference Architecture

Overview

Define a production Adobe architecture spanning identity, service adapters, async workers, asset custody, I/O Events, App Builder, evidence, and recovery. 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

The architecture separates control plane from data plane: identity/entitlement/configuration/deploy/approvals are control; prompts/documents/images/events/jobs are data. Each Adobe product has its own version, storage, error, limit, and lifecycle adapter. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

Bind credential broker output to organization, project/workspace, service, scopes, product profiles, environment, and owner. User-owned data uses explicit user auth rather than silent S2S substitution.