A domain, a deployment, and a source tree must agree

A practical way to prevent one public URL from hiding several conflicting truths.

A domain can point at one runtime while a local folder describes another. A deployment can be healthy while its source is incomplete. These are not cosmetic discrepancies: they make a future repair unsafe.

The practical test

Keep a small ledger for each public site: canonical hostname, source repository and revision, output directory, deployment target, current release, rollback reference, and owner. It turns a vague website task into a checkable change.

Related practice

Use this note as a prompt for a concrete review: identify the current public route, the source that owns it, the people it needs to serve, and the failure state it must survive.

← Back to notes