Platform

Readiness Checks

Verify deploy readiness before shipping.

Readiness checks catch deploy blockers before a release is queued.

Run checks

enclavely readiness --project kms-signer --env secure-signing

CI gate (strict mode):

enclavely verify --project kms-signer --scope all --strict-backlog

Typical checks

Project exists and is accessible
At least one environment is configured
Latest release health and artifact metadata are valid
Latest runner evidence markers, AWS phase timeline, and EIF artifact verification markers are present/valid
Usage and audit events are flowing

When checks fail

Fix reported failures
Re-run enclavely readiness
Deploy only after status is ready

Readiness is environment-name agnostic; it does not require specific names like staging or production.

Routing

Environment URLs and how routing follows healthy releases.

Service Contract

Service contract fields and validation rules.

On this page

Run checks Typical checks When checks fail