Scope the environment before connecting the work.

Name the product, the users, and the decision this deployment has to support. Then name the source systems and data classes it touches.

Keep the evaluation environment separate from production. They have different data and different acceptance requirements.

• Product family and capability
• Organization, workspace, and user roles
• Source objects and data classifications
• Required output, approval, and retention

Identify the identity provider and the authorization model before you connect any source work. Know which actions are privileged.

Secrets belong in the approved secret-management path. Never put credentials in a public form, a source example, or a documentation screenshot.

• Human and service identities
• Role and permission boundaries
• Secret storage and rotation
• Break-glass and offboarding paths

Document where source data begins and which systems process it. Then document what leaves each boundary.

Every assumption below has to be confirmed against the actual customer environment. Not the reference architecture.

• Ingress and egress paths
• Storage, retention, and deletion
• Region and residency requirements
• Encryption in transit and at rest
• Subprocessors and transfer review
• Restricted-data and redaction paths

Choose the logs, metrics, and audit events you need to understand the workflow. Restricted source content stays out of them.

Decide what failure, rollback, and stale-data behavior looks like before launch. The operating record names the owner and the next action.

• Operational and audit events
• Alert owners and escalation
• Backup, restore, and rollback
• Incident and customer communication

Run the agreed workflow with realistic source material. Exercise the failure and permission states, then record the acceptance decision.

A deployment is not done until the customer holds the runbook, the known limitations, and the rollback record.

• Functional and evidence acceptance
• Security and privacy review
• Accessibility and interaction validation
• Owner training, runbook, and rollback