# 15. What happens after the code works

> Working code starts the delivery. It does not finish it.

Lesson 15 of 27. Part 4 of 6: Judge the result. Source: https://chiefofagents.si/lessons/after-the-code-works

## The lesson

The application travels one path: a feature branch, a pull request, automated checks, a preview environment, independent review, my merge, automatic deployment, live verification, and then real users.

Database changes travel a second path: an additive migration, verification against a test database, my approval for production, and confirmation that production is ready. The two paths join before the merge.

Deployment is not proof. Checking the live system is a separate step.

## How I do it

CI is the automated checks on the proposed change. CD is the automatic deployment after I approve a merge.

## The rule

Treat "it works here", "it is deployed" and "it works for users" as three different claims.
