Hi everyone, I have just reached level 2 and would like to make a first post of my own. I have always been interested in technology, economics, and human behavior, but only recently started writing about how they connect. How AI is used inside our systems is the focus here. It is what brought me here, and why ICM makes sense to me. I also like to explore how we humans behave with these systems. I am sharing an essay I originally wrote in Portuguese and translated into English for this community. It explores the social cost of asking another person for help, and how AI changes that choice. Asking a machine can spare us the embarrassment of admitting what we do not know, or the judgment that sometimes comes with an answer. I look at how that changes whom we turn to, what we trust, and how we relate to one another.

Using ICM alone makes one person fast. Using it as a shared knowledge base makes a whole team fast and consistent. I call it an organized organisation 😂 The hard part isn't the AI, it's conflict management. I enforce four steps in code, not prompts: - Resolve conflicts: Git or a shared drive, depending on the case - Permissions and visibility: who edits instructions vs. who edits data - Handle stale files: give new information dates and context - Full auditability: every request is logged My setup today: 7 people on community-based research. I'm the maintainer (rules). Everyone else is a member (data). They can suggest rules, but I approve them. The AI even flags broken rules to me: "he wants to do this but can't, check it out". Still unsolved: stale files. Expiry dates or events help, but assigning them when a file is created is the hard part. For now, expired files stay put, the AI traces linked files to infer why, and asks me when unsure. Every failure updates the rules. If you're building team ICMs, I'd love to compare notes. Technical or not, message me. 🤝

⬅️ 𝗣𝗥𝗘𝗩.: 𝟬𝟱 — 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝗜𝗻𝗴𝗲𝘀𝘁𝗶𝗼𝗻　│🏠 𝟬𝟬 𝗦𝗧𝗔𝗥𝗧 𝗛𝗘𝗥𝗘│　𝗡𝗘𝗫𝗧: 𝟬𝟳 — 𝗖𝗼𝗺𝗶𝗻𝗴 𝗦𝗼𝗼𝗻 ➡️ Note: Press on the links above to navigate to each series or home. At the end of Post 05, my Knowledge System was able to process documents, extract their contents and recognise unchanged files. A great achievement and another step forward. However, there was a bit of a problem. Just because you have the information you need doesn't mean you can find it. Imagine thousands of documents. Somewhere in there is the information you are looking for. But which file does that information sit in and where exactly within that file? It's the needle in the haystack. I certainly didn't want to ask an LLM to read everything each time. Remember, I don’t have tokens burning a hole in pocket. 😅 🔎 𝗦𝗼, 𝗵𝗼𝘄 𝗱𝗼 𝘄𝗲 𝗳𝗶𝗻𝗱 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝘀𝘁𝘂𝗳𝗳? From Post 05, I already had the extracted content stored in JSON files on disk. Those files contained the information extracted from the original Word, Excel and PDF documents, along with details of where it came from. Technically, those files could be searched directly. However, with potentially thousands of documents in mind, I wanted a better way to organise and search that information. That's where SQLite came in. Essentially a lightweight database that could act as a searchable catalogue. The idea was simple: 📁 Original documents (Word, Excel, PDF) —> ⚙️ Extracted JSON files (stored on disk) —> 🗂️ SQLite catalogue (searchable index) —> 🔎 Matching passages and their source locations. Instead of going through all the extracted files for every search, SQLite could help locate matching information through its search index. Most importantly though, this was still deterministic processing, not AI reasoning.

Over the past few days, I’ve had some fascinating conversations here in this community, including a private chat with @Bryson Bossley . Those conversations got me thinking. And last night, I couldn’t stop thinking. One thought led to another. Ideas connected. Questions became bigger. And somehow, I ended up writing a speech and turning it into a video. So please, WATCH THE VIDEO FIRST. And if you recognize yourself in what I’m saying, if something in that message resonates with you… Come back and read this. ——— What Can We Build Together? 50,000 minds. Thousands of skills. Countless ideas. And yet… most of us are still trying to succeed alone. Think about that for a moment. What if the greatest opportunity in this community isn’t the next AI tool, another course, or another business? What if it’s the person reading this right now? Someone here might have exactly the knowledge you’re missing. Someone else might need exactly what you already know. And the strange thing is… Neither of you even knows the other exists. Isn’t that a tremendous waste of potential? I made this video because I believe we’re overlooking something extraordinary. It’s not another tutorial. It’s not a sales pitch. It’s a question we should all be asking ourselves. What could we achieve if we stopped trying to do everything alone and started combining what we’re already good at? Maybe we don’t need another thousand ideas. Maybe we need to connect the people who can bring them to life. And maybe it starts right here. Not with another complicated system. Not with another promise of success. But with people discovering each other. So let me ask you three simple questions. 1. What are you genuinely good at? 2. What do you need help with? 3. What would you build with others? Don’t overthink your answers. You don’t need to impress anyone. You don’t need to sell yourself. Just be yourself. Because somewhere among the people reading this, someone might have exactly the missing piece you’ve been searching for.

Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.