Delivery/Deployments/Overview
Delivery
What shipped, when, where, and whether it made things worse.
Delivery covers everything that ships code, and — more usefully — everything that connects a change to its consequences.
Deployment history
Every deploy, what was in it, and what happened afterwards.
Pipelines
Gate → deploy → smoke → health → promote or roll back.
Releases and changelogs
What shipped, per environment, with AI-drafted notes.
Environments
The version matrix, and the one answer to "is this production?".
Per-server rollout
Which box got which version, and last-known-good rollback.
Insights and DORA
Blast radius, change-failure attribution, lead time.
Freezes and approvals
When not to ship, and who says yes.
Setting it up
Webhooks, Jenkinsfiles, and how deploys get recorded.
The point of recording deploys
Most incidents are caused by a change. A monitoring system that knows what changed answers the first question of every incident before anybody asks it.
Specifically, it is what lets an alert say:
errors rose on
/checkouteleven minutes after release 4.18.2 went to production, on the three servers that got it first
Every clause there comes from a different part of this section, joined in one database.
Around delivery
Part of Delivery — Deployments, pipelines, releases and everything that ships code.