Ship a Backend to Production
One commit, from a repository to serving real traffic. Every hop produces something, is owned by someone, fails in its own characteristic way, and has a piece of evidence that proves it did its job. Open a hop to see all four.
The reason to walk this end to end is that “the deploy worked” is almost never one fact. It is eleven separate facts, each of which can be false while the others are true: a green pipeline that never ran the relevant check, a tag that moved between build and deploy, an apply that succeeded while nothing became ready. The evidence line on each hop is the one that turns an assumption back into a check.
- What you own here
Which branch is deployable, what must pass before merge, and who can push directly.
How this hop fails- — A change merged without the check that would have caught it
- — Direct push bypassing required checks
Evidence it workedThe protected branch rejects a push that skips required checks — tested, not assumed.