Field Notes
Promotion scripts that live on one laptop
If the only path to production is a personal script, your release train has a single point of failure wearing headphones.
We still meet teams where production promotion means asking Sam to run a script from a home directory. Sam is careful. Sam also goes on leave.
Signals you have a laptop gate
- The runbook says “ask platform” with no repository link
- The script path differs between the two people who know it
- New engineers cannot promote without a shoulder-surf session
A minimum shared path
Move the script into the repository that owns the service, run it from CI with explicit approvals, and log who promoted what. You do not need a perfect platform on week one. You need a path that survives Sam’s long weekend.
What we push back on
Replacing a laptop script with a dashboard nobody understands is not progress. Shared automation should be readable by the team that ships the service — not only by a tooling specialist.
During Release Automation Audits we treat laptop gates as high-priority findings because they combine operational risk with knowledge risk.