d5sd5s

Confirm a release is healthy, or say precisely what is not.

After a release, compare error and delivery signals against the pre-release baseline and report whether anything moved beyond normal variance.

Who it isA release engineer who checks whether the deploy actually landed cleanly.
Wakes upWhen a release is marked complete
Reads
Reports toSlack or a dedicated mailbox. You choose on the next screen.
Add Deploy health check to your workspaceNothing runs until you add it.
Engineeringone of 24 ready-made agents in the library
Deliverable

A post-release health note comparing error and delivery signals against the prior baseline.

Human sign-off required

A post-release health note comparing error and delivery signals against the prior baseline. Prepared for review, never posted.

How this composition works.

A deploy is usually declared fine because nobody looked. This workflow compares the window after a release against the equivalent window before it, so a regression is reported as a difference rather than as a raw count. It states what changed and what it cannot explain, and never rolls back or reconfigures anything itself.

Read the release

Identify what shipped and when the release window opened.

Compare error signals

Measure new and regressed errors against the pre-release baseline.

Check delivery

Compare edge availability and response behaviour for the same window.

A human signs off

Rollbacks, configuration changes, and production remediation require an engineer.

Deliverable

A post-release health note comparing error and delivery signals against the prior baseline.

Human sign-off required

A post-release health note comparing error and delivery signals against the prior baseline. Prepared for review, never posted.

Composed from the tools engineering already uses.

Put your engineering workflow under policy. Tell us what your team repeats today.

More for engineering.