Can we prove a rollback target?

Every successful production release now gets an immutable manifest with release identity, Compose fingerprint, database-model schema fingerprint and runtime image IDs. Rollback Readiness Brain compares the current release with the immediately previous successful release before allowing even a rollback plan to be considered safe enough for review.

Execution still disabled. A green planning result does not mean DevOpsYar can roll back automatically. Historical image availability, database backup posture and exact human approval must still be re-verified immediately before any future rollback.

LATEST PRODUCTION CHANGENo deployment recorded yet—Waiting for deployment evidence.

risk · —advisor · —readiness · —

Deployments · 24h0

Incidents · 24h0

Temporally correlated0

High / critical risk0

Rollback recommended0

Rollback plan-ready0

Production release risk & rollback readiness

Loading release evidence…