A short change can affect many people, while a large internal change may be safe to test away from live work.
Use an impact test, not a size test
A four-line change can affect everyone who reaches a broken path. A much larger internal cleanup may be safe to test away from live work. The number of lines does not tell you either story.
Before choosing a release path, ask four questions: Who is affected if this is wrong? How exposed are they? How reversible is the change? What observable result would verify success?
Where AI fits
AI can organize the known impact, affected people, reversibility, and verification evidence into a release checklist.
The human decision
People assess the real-world impact, authorize the release path, and verify the outcome in the environment that matters.
The lesson
Release caution should follow consequence and recoverability, not the apparent size of a change or the date on the calendar.
The Build Log companion explains how two changes with very different line counts needed different release paths for reasons a diff could not show.
AI Skills
Use this lesson with the AI assistant you already use
Release caution should follow consequence and recoverability, not the apparent size of a change or the date on the calendar.
Paste the prompt, share only the context needed to answer it, and treat the result as a draft for your review. Do not include confidential information or let an AI assistant make changes without your approval.
Optional: for a visual report and saved memory, run /dxdev first.
Don’t have it? Get it at dxdev.com/skills/dxdev. The prompt works without it.
dxdev LESSON · paste into your AI agent
LESSON: 2026-02-19_release-by-impact
WHAT TO SHARE:
A de-identified proposed change, who it affects, how it could be reversed, and how success would be checked.
ASK YOUR AGENT TO:
1. Separate confirmed facts from assumptions and unanswered questions.
2. List affected people and user-facing exposure.
3. Map reversibility and the safest rollback option.
4. Draft verification evidence needed before and after release.
RETURN:
An impact, reversibility, exposure, and verification table with a human-owned release decision.
BOUNDARY: Do not change records, contact anyone, route work, publish content, or act in an external system. A person must review the evidence and approve every consequential step.
