- artifact
- sha256:a91e…
- target
- production / eu-west
- strategy
- canary · 10% → 100%
- approval
- 2-of-3 · release team
Approve this build.
Nothing adjacent.
Auths Deploy binds approval to the artifact and operation that will actually reach an environment—not a reusable role, a broad scope, or a session.
The approval and release
cannot drift apart.
The deployment profile gives security meaning to the artifact digest, target, configuration, strategy, and time window. Change a covered field and the authorization no longer matches.
Canonicalize the release
Turn artifact, target, configuration, and rollout strategy into one unambiguous action.
Gather authority
Required approvers sign or delegate against the exact action digest and constraints.
Check at admission
The deployment boundary resolves authority locally before accepting the release.
Deploy what was proven
The verified action drives the release. A substituted artifact or target fails closed.
Approval integrity
Reviewers approve the exact artifact and deployment parameters that enforcement later sees.
Threshold authority
Sensitive environments can require multiple independent signatures without a bespoke approval service.
Portable evidence
The complete authority path can accompany the release into disconnected or isolated environments.
Deterministic admission
The same proof, action, and trust context yield the same release decision everywhere.
Verify. Decode. Execute.
The verified action—not ambient credentials or unchecked request data—becomes the command.
// Bind admission to immutable release data.
action = deploy_profile.encode(
artifact_digest,
environment,
rollout
)
release = auths.verify(proof, action, trust)
deploy(release.verified_action)Make approval inseparable from execution.
See how explicit trust, bounded delegation, and exact actions form one portable authorization model.