# Use One Local Make Command For UI Candidates

The two-profile publication detail below is superseded by ADR 0042. The single
command and local-first decisions remain active.

The v1 CP9 UI candidate path is one local maintainer command: `make dbaas-ui-candidate`. It uses the maintainer's existing `gh` identity to resolve and clone the private upstream `master` commit, then runs the overlay, compile-time checks, route-probe generation, conformance checks, and static-server packaging. It validates locally by default; publication requires an explicit opt-in and a runtime account `cp9-developer` AWS profile authorized by the account-414 repository policy. It never promotes a candidate, changes the checked-in image pin, provisions registry infrastructure, or pushes Git changes. CP9 does not introduce a GitHub Actions workflow, source-repository secret, or GitHub OIDC roles for v1. If automation is added later, it invokes the same Make target so local and automated delivery do not diverge.