A single session is easy to manage. A project with fifteen threads is a different problem entirely.

You've learned the Launch Pack — how to carry context from one session into the next. That system works. But at a certain scale, individual Launch Packs aren't enough. When your project grows into multiple conversations, each doing a different job, you face a new challenge that almost nobody talks about: the through line doesn't break all at once. It drifts.

Section by section. Thread by thread. Quietly. Until the day you read everything back and realize the opening and the closing feel like they were written for two different projects — because effectively, inside the machine, they were.

Consider what a serious project actually looks like inside an AI platform. A business plan might have fifteen sections — executive summary, market analysis, competitive positioning, financial projections, and so on. Each section gets its own dedicated thread. Each thread runs deep — hundreds of exchanges, decisions made and reversed, language refined, arguments tested. Max out those threads and you're looking at the equivalent of 300 to 400 pages per conversation. Fifteen threads. Thousands of pages of working material.

Here's what the machine sees: nothing. Each thread is a sealed room. The conversation working on your financial projections has never read your executive summary. It doesn't know your investor is a venture capitalist, not a bank. It doesn't know the voice you locked in three threads ago. It only knows what you brought into that room.

And here's the part that creates drift: each thread, doing its job well in isolation, will gradually pull the project toward its own internal logic. The financial thread starts sounding like a finance document. The marketing thread starts sounding like a marketing deck. Nobody is doing anything wrong. But without something holding the whole project together above all of them, the work loses its coherence at exactly the moment it should be finding it.

Managing a large project requires two layers of documentation working at different altitudes. Confuse the two and you'll find yourself either re-explaining the whole project in every thread or losing the north star entirely.

Here's what most people get wrong about loading context into a new session: they explain when they should be loading. There's a difference.

Explaining sounds like: "So I've been working on this project for a few weeks, it's a business plan for a company I'm building, we've been through a few different directions but I think we've landed on something..." That's narrative. The machine is pattern-matching through it, trying to extract signal from story. You're spending energy and the AI is spending context window on reconstruction work that a well-structured document eliminates entirely.

Loading sounds like a Master Brief followed by a Section Launch Pack followed by one specific instruction. No preamble. No history. Just structured signal at the top, then the work. The machine orients in seconds instead of paragraphs.

One more thing worth knowing: the longer a single thread runs, the more the earliest context compresses. Early decisions — the ones that shaped everything that followed — carry less weight by exchange forty than they did by exchange four. This is not a flaw to fight. It's the architecture. Which means for long, deep working sessions, the move is to break at natural milestones, update the Launch Pack, and open fresh. A clean room with full context runs better than an overcrowded one where the foundations are fading.

The Vault is the name for all of it together — the folder structure, the Master Brief, the Section Launch Packs, the working drafts, the rejected material that isn't dead but isn't ready. Everything the project has ever been and everything it's becoming, organized so you can find any piece of it in under thirty seconds.

The rejected material folder is the one people skip. Don't. The section that landed wrong in thread three might be exactly right in thread eleven. The argument you cut because it was too strong for the opening might be the closing. A Vault doesn't throw anything away. It files it. Everything that gets cut goes somewhere it can be found.

But rejected material isn't always what you consciously decided to discard. Some of it is the stuff that started sounding like everything else — the paragraph you've rewritten four times that keeps circling the same point, the section that felt important until you realized it was just repetition wearing a different jacket. When you're deep enough in a project, everything begins to sound familiar. That familiarity is the signal. If you can't tell whether something is essential or just comfortable, it goes in the rejected folder — not the draft.

And sometimes the right move is to burn it entirely. Not file it. Delete it. Because even material you never open again occupies bandwidth — in the platform, in the Vault, and most expensively, in your head. Knowing something exists means some part of you is still carrying it. There are pieces of a project that don't need to be preserved. They need to be released. A clean room thinks better than a full one. Part of managing a Vault is knowing the difference between what deserves to be kept and what just needs to be gone.

The discipline that keeps a large project coherent is simpler than it sounds: every thread opens with the Master Brief. Every session closes with an updated Section Launch Pack. Every piece of cut material goes into the Vault instead of disappearing. Three habits. Applied consistently across every thread, every session, every sitting — they're what separates a finished project from one that's permanently almost done.

The framework here is a starting point, not a prescription. You'll develop your own version of the Master Brief. Your Section Launch Packs will look different from someone else's. The Vault structure that works for a memoir will look different from one built around a business plan or a keynote. What stays constant across all of them is the principle: the machine holds nothing between sessions. You hold everything. The system is how you do that without it consuming the work itself.