Repeated explanations are a sign that important context is trapped in memory instead of being available where the work begins.
Give a new session maintained inputs, not a generated retrospective
This is not about one person carrying organizational memory. It is about the point where a new work or AI session begins. That moment needs confirmed rules, known constraints, exceptions, and references that are maintained before the session starts.
A useful context note should distinguish a confirmed rule from an open question and point back to the source when the detail matters.
Where AI fits
AI can organize selected facts, constraints, and exceptions into a small source-linked context draft for the start of a session.
The human decision
People verify the rules and decide what the maintained input treats as true. AI should not fill a missing rule with a plausible reconstruction.
The lesson
Repeated re-explanation is evidence that a durable session-start input is missing.
The Build Log companion shows how a committed context file reduced guesswork without asking an assistant to invent the operating rules.
AI Skills
Use this lesson with the AI assistant you already use
Repeated re-explanation is evidence that a durable session-start input is missing.
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-26_shared-context-first
WHAT TO SHARE:
Selected rules, constraints, known exceptions, and links or references a new session should read first.
ASK YOUR AGENT TO:
1. Separate confirmed facts from assumptions and unanswered questions.
2. Separate confirmed rules from open questions.
3. Attach a source reference to each load-bearing constraint.
4. Flag anything that needs a human update before it becomes session input.
RETURN:
A session-start context note with confirmed context, open questions, and source references.
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.
