Rowboat: 13K-Star Open-Source AI Coworker Built On A Local Knowledge Graph

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

Source video:
- Title: Rowboat: 13K-Star Open-Source AI Coworker Built On A Local Knowledge Graph
- URL: https://www.youtube.com/watch?v=D_6xnX5NXRQ
- Topic: Agent Architecture
- My current learning frame: Spin up Robo via the one-click desktop app or the Docker Compose path, point it at your email and calendar, then open the resulting markdown directory in a text editor and grep it to confirm you can actually read and edit your own AI's memory.
- Why this matters: New playlist item from AwesomeFOSS; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:21 / Evidence 1: "self-hosting. The interesting part is the architecture. Every conversation, every contact, every project, every topic gets stored as plain markdown files on your own machine. Structured into a knowledge graph you can actually inspect with a text editor."
- 2:32 / Evidence 2: "posture is clear. The project is open source, the code is auditable, and there is no premium-only feature gate hiding the good parts behind a cloud subscription. The feature set covers the actual workflow of someone who lives..."
- 4:54 / Evidence 3: "fork the code base and change how the graph is built. None of this is an argument that ChatGPT is bad. It is an argument that for the AI co-worker pattern specifically, the one where the assistant actually..."
- 6:37 / Evidence 4: "architectures, star the repository on GitHub. Visibility actually matters for projects making the case that local first is the right answer. Subscribe to Awesome Foss for more open-source tools that actually replace the proprietary defaults."

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 agent harness map with tool boundaries and proof signals.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Model -> Harness -> Tools -> Verifier -> Artifact
   - 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 "Rowboat: 13K-Star Open-Source AI Coworker Built On A Local Knowledge Graph", not a generic Agent Architecture 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.