---
title: "Do Not Make Every New Session Start From Guesswork"
canonical: https://dxdev.com/blog/2026-02-26_shared-context-first/
datePublished: 2026-02-26
---
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.