The bait, then the rug-pull.
Andrej Karpathy's tweet about his AI second-brain system reached 21 million people — a jaw-dropping number for a post full of technical file paths and markdown schemas. Dream Labs AI opens with a blunt diagnosis: 99% of businesses are feeding Claude the whole internet and getting average slop back. The fix takes under ten minutes to set up, and this video shows every step live.
What the video promised.
stated at 00:43 "How to set it up personalized to you and your business in the next ten minutes." delivered at 12:36
Where the time goes.
01 · Cold open — credibility hook
Karpathy name-drop (ChatGPT founder, Tesla AI director). Problem: no memory, no context, no business alignment. Promise: collapse a month of work into a single day.
02 · How most people use AI wrong
The 'generalist bubble bath' diagram — Claude pulls from the whole internet unfiltered → AI slop output. Identifies the root cause: no business-specific filter layer.
03 · Karpathy's specialist approach
Obsidian as the filter: goals + context + data + schema between you and the LLM. Self-learning loop: every query feeds back into the directory and makes it smarter.
04 · Anatomy of the second brain
Raw data → Schema rulebook → Wiki (concepts/entities/sources/synthesis). AI handles everything except the initial data drop.
05 · Setup — Obsidian + Claude Code
Download Obsidian (Notion-like, neural graph view). Use Claude desktop, terminal, or any IDE.
06 · Karpathy's viral tweet + IDEA file
The 21M-view tweet. GitHub gist link. Copy the raw MD. Karpathy improved it post-virality with an updated IDEA file for download.
07 · Creating your Obsidian vault
Brand-name the vault (DreamLabs AI). Keep the welcome page — Karpathy's transform function needs it. Paste the 91-line IDEA file.
08 · Claude Code builds it out
Voice prompt to Claude Code. Five build steps: directory structure, CLAUDE.md schema, index.md, log file, welcome transform. Graph view in Obsidian starts populating in real time.
09 · What raw data to feed it
Business goals, content transcripts, directional articles, project files, competitor research, Hormozi 12-question interview, role-model skill plugins (Tony Robbins 'gaming cartridge' analogy).
10 · Dropping assets in
Drag any file type (PDF, MD, images, notes) into /raw/assets. Claude creates an MD for each. Goals file shown: 'practical not novelty' doctrine.
11 · Compiling the wiki
Tell Claude: 'compile my business wiki.' It reads sources in parallel, writes summary/entity/concept pages, updates index + log. Took 8m42s for DreamLabs dataset. Obsidian graph builds out neural connections live.
12 · Querying live + results
Query 1: 'Give me a YouTube video idea based on my business and past videos.' Result: 'I let Alex Hormozi's AI run my business for 30 days — the brutal truth.' Query 2 (mentioned): 'Tell me where the gaps in my knowledge are.' Closes with subscribe CTA.
Visual structure at a glance.
Named ideas worth stealing.
Generalist vs. Specialist AI
Generalist: Claude pulls from the whole internet → average output. Specialist: Obsidian filter layer (goals + context + data + schema) sits between you and the LLM, then re-filters internet output back through your business lens.
Karpathy's IDEA File / LLM Wiki Schema
- Raw data (/raw/assets)
- Wiki structure (/wiki/concepts, /entities, /sources, /synthesis)
- CLAUDE.md schema (rulebook)
- Log file (self-learning tracker)
- Index.md (master index)
Open-source GitHub gist. Copy the raw MD, paste into Obsidian vault, Claude Code scaffolds the full directory and transforms the welcome page.
Raw Data Taxonomy
- Business goals doc
- Your own content transcripts
- Directional articles (aspirational, not authored)
- Project files
- Competitor research
- Interview answers (e.g. Hormozi 12 Qs)
- Role model skill plugins
Any file type works. More data = better outputs. The system is only as smart as what you feed it.
Role Model Skills Plugin
Take a public figure's publicly available content, synthesize into a skill file ('gaming cartridge'), plug into the wiki. Creates a 'board of directors' of mentors shaping every AI output.
Lines you could clip.
"A thousand IQ employee who gets smarter every conversation you have, knows exactly what your business goals are, and even autonomously builds towards them while you sleep."
"The average IQ, the victim mindset, the stuff you don't believe in — it's all getting jumbled, mixed into your training data, and giving you very average AI slop output."
"For the first time ever, it's gonna have compounding knowledge and even be able to show you where the holes in your knowledge around your business and goals and action steps might be."
"We're not using AI for AI's sake. We're not using technology for technology's sake. The core of my AI business is practical, not novelty."
"Every video so far teaches setup. None show what happened after."
How they spent the runtime.
Things they pointed at.
How they asked for the click.
"If you've made it this far into the video and haven't hit that subscribe button below, please do. This is a new channel and we wanna grow an amazing audience together."
Mid-video ask, not end — placed at 85% mark while wiki is compiling. Honest and direct, no over-engineering.
Word for word.
The second brain format is a content category Joe doesn't own yet.
The video is half 'here's a powerful system' and half 'watch me build it live for my own business' — and the live-build half is what earns the trust.
- Build your own Karpathy second brain immediately: MCN data, JoeFlow transcripts, joe-profile.md, and sessions history are the raw corpus. You have more data than this creator does.
- The 'role model skill plugin = gaming cartridge' angle is a video Joe hasn't made — and it's a banger. 'I built an Alex Hormozi brain for my business, here's what happened.'
- The framework contrast (generalist slop vs. specialist masterpiece) maps directly onto Joe's 'stop renting, own your stack' positioning — adapt it for MCN+ sales copy.
- The live-query payoff ('here's the video idea the system generated for me') is a repeatable format: build → query → show results. Joe can do this monthly with new raw data drops.
- The 'gaps in my knowledge' query is an underused format angle — 'I asked my AI what I'm missing. Here's what it said.' That's a hook Joe should steal.
How to make your AI actually useful for your work.
The reason AI gives you generic answers is that it's working from the whole internet — not from what you actually care about.
- Create a simple folder on your computer where you collect everything important to your work: your goals, past projects, key articles, notes from conversations.
- Karpathy's IDEA file (free on GitHub) gives you a ready-made structure — you don't need to design a system from scratch.
- Feed Claude Code your folder and tell it to build a wiki. It takes about 10 minutes and the results improve every time you add more context.
- The 'gaps' query alone is worth setting this up: ask the system 'what am I missing?' and it will tell you things you wouldn't have thought to ask.
- This is not a SaaS tool — it's files on your computer. You own it, it doesn't expire, and it gets smarter the more you use it.































































