Trust increases when a record can show that it changed, when it changed, and where someone should look to understand the change.
The practical check
Ask what history matters, which changes need evidence, and how a reviewer can notice a missing or altered step.
Where AI fits
AI can trace the expected change chain and flag missing, inconsistent, or unsupported links for a reviewer to inspect.
The human decision
People decide what evidence is sufficient and investigate any unexpected change.
The lesson
If a record matters, its change history should make it possible to see what changed, find the supporting evidence, and investigate a missing link.
The Build Log companion identifies change-chain gaps and unsupported links for review.
AI Skills
Use this lesson with the AI assistant you already use
Create a change, evidence, gap, and reviewer-action table.
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: Make Important Changes Reviewable
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 change, evidence, gap, and reviewer-action table.
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.
