How to give AI persistent context so it stops starting from zero every conversation — and why the right project setup determines whether Ring 2 actually pays off.
Every tool handles memory differently. ChatGPT has Memory that auto-summarizes facts about you across chats. Gemini saves personalization info. CoPilot grounds in your M365 graph activity. Claude, by default, has no user-level memory at all.
So why doesn't this solve the context problem? Because the memory each tool gives you for free is shallow, automatic, and not fully under your control:
The result: you still spend the first ten minutes of every important conversation explaining your organization, your audience, your constraints, your tone. Next week, same problem, different angle — and you mostly start over.
Projects give you the deep, explicit, controllable context layer that auto-memory cannot.
Ring 1 lived entirely in the Conversation layer — every prompt was self-contained. Ring 2 begins when you expand into Project and Canonical layers. A project (whatever your tool calls it) is the container for both. Without it, Ring 2 has no home.
This is why the next move is project setup. Not because projects are cool. Because encoded judgment has to live somewhere AI reads automatically — otherwise you'll keep typing the same context every chat, and nothing accumulates.
Different tools call these different things, but the underlying structure is the same. Miss any one and the project becomes a folder of chats, not a working system.
Written once, active in every conversation inside the project. Who you are, what this project is for, how you want AI to think with you. The difference between a generic assistant and one that already knows your context.
Documents AI reads before responding. Strategy memos, brand guidelines, previous analyses, your voice and taste docs. AI references these directly — you don't paste them into every conversation.
Decisions, directions, conclusions across time. Some tools handle this automatically; others require manual updates to knowledge files. Either way, the project is where work continuity lives.
All conversations within the project in one place, searchable. Return to any thread, pick up where you left off, or trace how a decision evolved over multiple sessions.
Each major tool has its own name for projects. Knowing the map lets you apply the same discipline regardless of which tool you use.
| Tool | What it's called | Default behavior |
|---|---|---|
| Claude | Projects | Explicit. You load files, write instructions, manage what AI sees. |
| ChatGPT | Projects (newer) or Custom GPTs (older) | Mixed. Memory is auto across chats; project knowledge is manual. |
| M365 CoPilot | Copilot Studio Agents, Notebooks, or saved prompts | Implicit. M365 graph grounds across your work email/files automatically; explicit scoping is optional but powerful. |
| Gemini | Gems + Drive grounding | Mixed. Workspace data is grounded; Gems add explicit scope. |
Each tool makes a different bet about how much you should do yourself. Knowing which bet your tool made tells you exactly what work is still on your plate.
Assumes you'll load context yourself. Nothing carries between projects unless you put it there. No surprise memory, no ambient grounding.
Grounds in your M365 graph — email, OneDrive, SharePoint, Teams, Calendar. You don't create a project layer; your work environment is the project layer.
User-level Memory (auto), Projects (manual), Custom GPTs (shared scope). The most layered model — most flexibility, most decisions to make.
The "I have CoPilot grounding, I don't need projects" instinct is half-right and creates four real problems.
A scoped container — a Copilot Studio Agent, a Notebook, or a designated OneDrive folder you point AI at — solves all four problems. You still need it.
Not every task needs a project. The question: does AI need to know something about you, your work, or your context to give you something genuinely useful — and will you need that same context more than once?
Projects start as folders for related chats. They become the container for everything Ring 2 and Ring 3 you do.
Identify one real project you'll set up live with us. It does not need to be your most important work. It needs to be something you return to weekly, where AI knowing your context would change the quality of the output.
One sentence: what is it? "I advise mid-market PE portfolio companies on operations." or "I write a weekly insurance industry newsletter."
The most context-loaded artifact you have for this work area. The first thing AI should always know.
Examples of context you typed more than once in the last week. The most important item — tells us exactly what should live in the project.
The repetition examples tell you exactly what should live in the Project layer (context for this work area) versus what belongs in the Canonical layer (about you, across all your work). We use them as the seed for your install.
wrap. See your first FOR THE FILE output. Paste into signals.md.By the end, you walk out with a working project containing your first knowledge files, the Capture Skill installed, and one captured signal. That's the install of Ring 2. The real work begins the next morning — using it every week, watching it accumulate, watching your AI get smarter about you on its own.
Specific interface details and feature names change. The underlying concept — giving AI persistent context to eliminate the re-explanation tax — does not. When something described here doesn't match what you see in your tool, check the support documentation for that tool. The principle is durable; the buttons evolve.
AI tools are rapidly evolving how they handle memory. Claude has been adding memory features in some surfaces. ChatGPT's Memory expands periodically. CoPilot's grounding behaviors continue to develop. Gemini's Saved Info works differently on consumer vs. Workspace accounts. Treat the specifics in this document as a snapshot, not a permanent map. The underlying principle — that projects give you deep, explicit, controllable context that auto-memory cannot replicate — holds across the changes.