Approve a release. Not a moving target.

Keep consequential production changes inside an explicit authority boundary, with a reviewable request and an unchanged release.

May this principal deploy this exact change?

The mapped deployment operation takes environment, ref, commit_sha and artifact_sha256. Repository and deployment target are server-owned configuration.

The control plane evaluates prod.deploy for the configured repository. A held request goes through the authenticated human approval process before a bound release can proceed.

Fix the target

Do not let the workload substitute another repository, environment or deployment target.

Bind the approval

Keep the significant request and effective execution binding unchanged. Modified requests require reauthorization.

A hash is an identifier. Verification is a job.

A supplied commit or artifact digest is not independent proof that the artifact is trustworthy. The upstream must deploy the intended immutable revision and verify the expected digest and provenance.

The reviewed adapter must not silently resolve a mutable branch or latest tag instead of the approved artifact.

Keep the change understandable.

Named approval

Agree who may approve a production action and which request values the person must review.

Immutable execution

Confirm the deployment adapter executes the approved revision and artifact, not a later substitute.

Failure and recovery

Agree timeout, retry, rollback and reconciliation behavior with the protected deployment system.

Evidence boundaries

Separate the signed authorization decision from actual deployment-outcome evidence.

Discuss your workflow.

Define the actions, limits and approval process your team needs.

Let’s discuss your pilot