Build and deploy are separate states
A successful local build proves that source can produce an artifact under local conditions. It does not prove that artifact was deployed, that production uses it, or that external configuration is correct.
Environments need explicit boundaries
Local development, preview, and production can use different origins, credentials, data, and release controls. Keep those differences visible so a test against one environment is not reported as acceptance of another.
A familiar example
Publishing a static lesson
- The build prerenders the lesson into an HTML file and adds it to the sitemap.
- A local static server verifies the built artifact and its navigation.
- A separately authorized deployment publishes the exact reviewed artifact, followed by a live URL check.
What to remember
- A build creates an artifact; a deployment publishes one.
- Local success and live health are different evidence.
- Keep source, candidate, deployed version, and live verification explicit.