A successful deployment can prove that a process ran, not that the intended change reached the live place people actually use.
The practical check
Name the visible marker or outcome that would prove the right version is live, then check it after deployment.
Where AI fits
AI can organize expected markers, live checks, and evidence into a post-deploy verification list.
The human decision
People decide whether evidence confirms the intended result and whether rollback is needed.
The lesson
Do not declare success because a pipeline is green. Check an observable live marker that proves the intended artifact or behavior is actually present.
A visible live marker anchors the deployment check recorded in the Build Log companion.
AI Skills
Use this lesson with the AI assistant you already use
Create a ticket marker, live check, evidence, and human disposition checklist.
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: Verify the Live Result
WHAT TO SHARE:
A de-identified description of the work, current evidence, and the decision you are considering.
ASK YOUR AGENT TO:
1. Separate confirmed facts from assumptions and unanswered questions.
2. Create a ticket marker, live check, evidence, and human disposition checklist.
3. Identify the narrowest useful next review step.
RETURN:
A short table with the evidence, uncertainty, human-owned decision, and next action.
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.
