# Publish CP9 UI Images From Account 414

CP9 sessions may run in different consumer AWS accounts, so storing the CP9 UI image only in the current 804 account would turn every additional account into an image-copy and lifecycle problem. CP9 publishes each immutable UI image candidate once to ECR in account `385595570414`; consumer accounts receive cross-account pull authorization and select promoted digests without copying the image. The registry is durable CP9 release infrastructure, not a session resource, and `cp9 destroy` never removes it. Repository region placement and the concrete authorization mechanism remain implementation details of the image distribution contract.