A content process becomes hard to trust when draft, review, approval, publication, and correction exist only as assumptions or messages.
The practical check
Make each transition visible enough that someone can tell what is allowed next, who owns it, and what evidence is required.
Where AI fits
AI can organize a content record into explicit states, required evidence, and pending decisions.
The human decision
People approve publication, corrections, and exceptions; AI can prepare but not advance consequential states.
The lesson
A content workflow becomes trustworthy when every state makes the required evidence, allowed next action, and accountable human owner visible.
Each content transition’s evidence, allowed action, and accountable owner are traced in the Build Log companion.
AI Skills
Use this lesson with the AI assistant you already use
Map each content state to evidence, allowed next action, and human owner.
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 Content State Visible
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. Map each content state to evidence, allowed next action, and human owner.
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.
