Require exact-artifact Owner authorization for production

[shiny-code-bot]

Goal

Require a separate Owner authorization for every exact production artifact while keeping evidence assembly deterministic and rollback available.

Scope

• Build a deterministic release-evidence bundle containing the exact image/artifact digest, source and merge commits, included PRs, agent attestations, Owner acceptances, required checks, runtime configuration identity, and target product/environment.
• Require an Owner of the target product/system to approve the exact tested artifact before provider mutation.
• Keep the individual-change acceptance and production authorization as distinct events; the same Owner may perform both.
• Execute promotions through Launchplane and provider APIs, including Dokploy, under the executing engineer/agent identity.
• Permit automatic or engineer-triggered rollback/containment to a known-good artifact without prior Owner approval.
• After rollback, require restored normal authority and a fresh exact-artifact Owner authorization before any forward promotion.
• Defer emergency forward-promotion break glass to its own Later issue.

Acceptance Criteria

• No production mutation occurs before exact artifact, target, policy, and current Owner authorization are validated.
• The release bundle proves continuity from reviewed PR heads to the built artifact without a routine second full LLM code review.
• Missing, stale, unreviewed, or newly introduced changes block authorization.
• Owners can inspect the release candidate, full-suite results, included changes, and target before approval.
• Rollback is idempotent, audited, and cannot create an automatic re-promotion loop.
• Provider/UI bypasses cannot produce a Launchplane-authorized promotion record.

Finish Line

Every production deployment is an exact-artifact Owner-authorized Launchplane promotion with deterministic evidence and safe audited containment.

Next Action

Define the release-evidence and production-authorization contracts, then integrate them into generic-web and Odoo promotion admission before provider mutation.