owner
Record the reason
Every change connects to a problem, metric, complaint, task, or roadmap note.
Do not change copy, pricing, routes, or email only because it sounds prettier today.
before opening the door
Release ritual
A mini ritual before merge/deploy: what changed, what was checked, how to rollback, who to notify, and where to record the decision.
The release ritual turns deploy from tossing a candle into a well into opening a door carefully with one hand on rollback.
owner
Keep receipts
After important changes leave a short changelog: what changed, where, how to verify, how to rollback.
Do not leave the future team facing a riddle without a map and lamp.
everyone
Protect the user
If the user is vulnerable, anxious, or asks for risky advice, move the response back into safe boundaries.
Do not promise healing, guaranteed futures, legal wins, money, or influence over another person.
Release note
Before deploy, write a short note even if the release is small.
- Changed routes and files.
- Checks run and checks skipped.
- Expected user-visible change.
Rollback note
Rollback should not be invented during the fire.
- Previous archive or branch known.
- Routes that need manual verification listed.
- Owner knows how to pause affected flow if rollback fails.
checklist
- typecheck/lint/test passed or exception documented.
- links/route audit/structure/security passed.
- No internal route accidentally indexed.
- Final archive excludes node_modules/.next/env.
handoff
- Release handoff goes to owner with archive link, checks, caveats, and next layer suggestion.
red flags
- Release touches multiple risky systems at once.
- Skipped checks are hidden.
- Rollback cannot be explained in one paragraph.
related doors