Production operations
Run the production checklist
Ship Field Notes with verified ownership, configuration, domain, security, monitoring, recovery, and documentation rather than only a successful build.
8 minute lesson
Finish the course by treating deployment as an operating responsibility. The final artifact is the application plus the evidence needed to keep it reliable.
Verify the production commit, routes, form mutation, errors, environment scopes, domain and HTTPS, access, logs, alerts, usage controls, and rollback target. Document how to deploy, diagnose, recover, rotate secrets, and remove the project. If the project is temporary, deleting it and its credentials is part of the lifecycle.
Attach evidence to the release: immutable deployment ID, commit, build result, production-domain response, high-value smoke checks, migration state, current alert owner, and known-good rollback target. Record which external systems can still make a code rollback unsafe.
The runbook should be executable by someone who did not build the project. Give exact places to inspect, a decision point for rollback, and the steps that reconcile Git, data, and credentials afterward. Finish with decommissioning instructions for domains, tokens, environment variables, integrations, and external data so a retired project does not remain an unowned security or billing surface.
Deploy the final Field Notes release, complete the checklist, perform one rollback drill, and ask another person to follow the deployment and recovery notes.
Lesson completed