https://x.com/claudeai/status/2076351399999557669

In Part 2, I reorganized my Second Brain so the folder structure gave each kind of information a clearer home. That solved one problem: where information lived. It did not solve the next problem: How an AI agent, or even future me, should approach that information. A folder name alone cannot answer questions like: - Where should I look first? - Am I looking at raw source material or knowledge I have already adopted? - Could this contain sensitive information? - Does using it require approval? - Might it be out of date? That gap led me to create what I’m calling Source Manifest Lite. It sounds more technical than it is. Source Manifest Lite is a small routing map for the major source areas in my Second Brain. It is not an inventory of every note, file, or document. I don’t want another system that becomes too heavy to maintain. Instead, each source area gets a short description covering what it contains, what it is meant to be used for, its general sensitivity, any approval boundaries, the canonical place to start, and where supporting material can be found. The distinction between a canonical starting point and supporting material has been especially useful. I may have several raw captures about a subject, but only one current operating note that reflects what I have actually decided to use. The raw material still matters. It provides evidence, history, and context. But it should not automatically outrank the operating note. The same principle applies elsewhere: - Public research is not handled the same way as a sensitive source. - A recommendation is not the same thing as an approved action. - A historical note is not automatically a statement of current practice. Without a routing layer, those differences can be easy to miss, especially when an agent retrieves a passage that appears relevant but lacks the context needed to use it properly. Source Manifest Lite gives the agent a better starting point. It can indicate where to begin, what kind of material it is entering, and where it should slow down or ask for approval.

Hey guys, Adel here. I joined the community a couple of weeks ago and I was reading part of your messages and of course part of the videos shared by @Nick Vasilescu. I want to start congratulating Nick for his generosity sharing knowledge and resources. I'm a software engineer for the last 9 years and I was working as consultant another 9 years before that. Right now I'm working in a small startup orchestrating payments. Why Am I here? Well, I want really to take control of my life, you know when you work for a company there are good things but also bad things. In my opinion, the worst things are related to don't have control about what you want to do or the lack of flexibility in different perspectives. I want really to change that, but I'm a husband and a father and I can't quit my job until I have something in place. I want to be part of this new era, I had a little of exposure to AI in my job, but I want really to learn, grow and take advantage of this opportunity we have in front of us. But I need initially to do it in parallel with my job. I'm Spanish but currently living in Ireland. In one hand I'm checking boring processes here (bookkeeping, logistics management, ...), in order to find gaps and processes with potential to be automated. In the other hand it's where I want to receive help/advice from you guys... I'm seeing a lot of content and I want really to start doing things... Based on your actual experience, if you had to start right now, what would be the main resources or steps you would take? Thank you in advance for your time and help, I hope I can provide updates here... Adel.