Graphify + Obsidian + Claude Code = CHEAT CODE

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

Source video:
- Title: Graphify + Obsidian + Claude Code = CHEAT CODE
- URL: https://www.youtube.com/watch?v=mWLDn49_8HA
- Topic: Codex + Claude Workflows
- My current learning frame: Turn Graphify + Obsidian + Claude Code into a working note from the transcript anchors: 0:43 sets up combining these two tools, Cloud Code is able to better answer questions about large repositories within the context of our...
- Why this matters: New playlist item from Chase AI; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:43 / Evidence 1: "combining these two tools, Cloud Code is able to better answer questions about large repositories within the context of our vault. Now, what do I mean by that? Well, remember what Graphy does? Graphify allows us to point..."
- 4:21 / Evidence 2: "remember once we've installed Graphify, that includes the Graphy skills. So we just use natural language. So all I need to do is hop into Claude Code and say download the official Cloud Code documentation. Point Graphify at..."
- 6:23 / Evidence 3: "can very easily figure out answers about the documentation. If I ask it a question about sub agents, well, it's very easy for it to figure out what's related to sub aents, things like agent teams, etc. Because..."
- 9:57 / Evidence 4: "what we do is we have claude code take a look at that standalone directory of all those markdown files graphify created and we have claude code go through and say okay let's bring this in ignore that..."
- 12:28 / Evidence 5: "going to do if I tell cloud code to look up the agents command stuff and it's just this right. So what we have to do now is we need to bring in the source documents that all..."
- 14:27 / Evidence 6: "And all those link to one of the 146 full source documents. And so hopping into the main vault. If I go to graph imports claude code docs, right, we can see all that over here. So workree..."
- 16:06 / Evidence 7: "Graphify, whether that's some sort of unstructured documents like we did today or a codebase and bring it into Obsidian, whether that's in a siloed process or you're bringing it into some sort of larger context. I think..."

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 routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
   - 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 "Graphify + Obsidian + Claude Code = CHEAT CODE", not a generic Codex + Claude Workflows 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.