One Folder Runs Claude, Gemini, Codex, and even Obsidian (Free on GitHub)

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: One Folder Runs Claude, Gemini, Codex, and even Obsidian (Free on GitHub)
- URL: https://www.youtube.com/watch?v=4C2w8eIG48A
- Topic: AI Strategy
- My current learning frame: Use a plain-markdown personal knowledge architecture as the handoff layer between Claude, Gemini, Codex, Obsidian, and other tools so project memory stays portable.
- Why this matters: This reinforces the atlas pattern of durable artifacts: folders, notes, and conventions that survive tool switching.

Transcript anchors from this exact video:
- 0:28 / Evidence 1: "video, I show you proof that no matter if you're using Claude, Codeex, or Gemini, or any other local LLM, if you might need it, as some have some security worries, they rather want to use a local..."
- 3:09 / Evidence 2: "somebody. And Pax, the third agent in this constellation is the researcher. So Nolan will ask Pax to go online and research about the best front-end developer to build this or the best journal writer or the best..."
- 8:55 / Evidence 3: "information. This is not task management or project management. We say here there are projects habits that sounds like action but in the end it's the information about these action items. And yet you need to organize these..."
- 11:57 / Evidence 4: "does it just tells any LLM to initiate itself inside this folder but keep things very simplistic and rather forward and reference these agent MD files instead of creating custom skills. So you might have seen endless videos..."
- 17:28 / Evidence 5: "of the box. So here you see how things are connected. The different agents agents index that just visualizes the context in this folder. But here we go. There's Dr. Schmidt and he's connected with the clinic which..."
- 19:15 / Evidence 6: "describing the process map how the agents work. So do you need to create these files? No, because this is what Larry will do and the combination of Nolan who is hiring the agents and creates this skill..."
- 25:29 / Evidence 7: "what was going on. And this is much better than the automemory that is just random and never so comprehensive and context connected than building it this way. Now you see for the other two agents they launched."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A one-page business case for one agent workflow.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Use Case -> Workflow -> Agent Role -> Metric -> Risk -> Adoption
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "One Folder Runs Claude, Gemini, Codex, and even Obsidian (Free on GitHub)", not a generic AI Strategy essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.