Where should state, queues, and policy live for support ticket resolution while mapping workflow state, without weakening retry outcomes?

Support ticket resolution can pair the risk in deployment rollback with retry outcomes anchored in deployment operations; keep the review concrete by recording the relationship between support ticket resolution and deployment operations, the owner of deployment rollback, the retained retry outcomes, and the boundary assigned to production agents. Keep the review concrete by recording how support ticket resolution changes deployment operations, who owns deployment rollback, which retry outcomes is retained, and where production agents sets the boundary. Operators need a run record that shows completed steps, pending work, tool outcomes, and the next safe recovery action. For this scenario, review state preservation, configuration drift, and protection against cross-tenant leakage. Use measurable acceptance criteria so the answer can guide an architecture review.