I'm struggling with a gap in knowledge. Forgive me if this is already mentioned somewhere else. And if so point me in the right direction. Building and working with the folder structure is great, but how are people deploying these projects? Building for yourself, obviously the project is on your machine. But what about building for other people? Are you providing the repo for friends, colleagues, clients etc or sending them the folder structure so their own claude can use it? I'm kind of getting hung up on this point. And feel if I understand this a bit more it will help with more prospective shaping how the projects are built.

If you've ever had a great conversation with an AI assistant and watched all that context vanish the next morning, you know the problem. Models forget. Every session started from zero. We have all been there and we have either use prompts, handoff documents, and structured workflows. Or some mix of the three. I needed my AI to truly know my development environment. So, I built the structure of all three into the memory system. Not just the code, but the cohesion, not just the functions, but the impact. I've spent the past several months building a fix. It's called D.R.E.A.M.S, Deep Retention & Encoding AI Memory System, and I just put up an interactive breakdown of how it works. Overview @ DREAMS, Deep Retention & Encoding AI Memory System What it is, in one paragraph: DREAMS is a persistent memory layer for AI assistants, modeled on how biological memory actually works. Inputs flow through an encoder, sit in a working buffer, get evaluated by a consolidator, and graduate to long-term storage based on emotional weight and reinforcement, not just recency. Six memory types (episodic, semantic, procedural, emotional, contextual, perspective) get encoded, retrieved, and weighted differently. Memories are permanent. Append-only by design. Recall finds them forever. The non-negotiable: Your memory, in your database. DREAMS writes into a database instance you control. Not a vendor cloud. Not a black box. The corpus you build is yours. The continuity, the lessons, the perspective, the entire graph of associations, you take it with you. Any model that can call MCP can read it. Models will change. Your continuity won't. What you can do on the site: - Step through the live architecture, click each stage to see what it does - Read the six memory types and what each one is for, hover any card to see it in action - Type into the simulator and watch a memory encode, consolidate, and promote to long-term storage in real time - Run semantic recall against a seeded library of fifty memories from the build itself