COHORT 01 · KICKOFF #1 · MAY 8 2026

Welcome back.
Now we work.

Last week was the tour. This week is the first real working session — fix what broke during setup, see what's possible, watch the system synthesize live, then three of you on screen.

🔄 THE LOOP YOU'RE IN

Here's something I didn't tell you last week.

The talk I gave you wasn't drafted by me. It was drafted by Claude reading my vault.

The deck you're looking at — I didn't design it. Claude did, after reading my notes from the course-creation workshop I took in 2022, plus my last twelve years of public talks, plus every essay I've published.

The recipes file you got — Claude pulled it out of patterns across 200+ sources I've ingested over the past three months.

Today's session — the one you're sitting in right now — was designed by Claude reading the transcript of last week's session.

🔄 RECURSIVE PEDAGOGY

You're not just learning the system.

You're becoming an input to the system that teaches the system that teaches the next system.

Vault → Teaching Artifact → Cohort → New Sources → Vault (denser)
                                                       │
                                                       └────► next loop

By week 4, your cohort outputs are in my vault. Cohort 02 — if it happens — is designed by Claude reading what you just built.

TODAY'S 60 MINUTES

01State of the cohort — what shipped, what stuck5 min
02Ingest overview — the 6 pipelines10 min
03What's possible — real outputs · David's moment9 min
04Pro tips — eight rules of the road6 min
05Open mic — who wants to share screen?20 min
06Q&A + what's next10 min

✨ HOUSE RULES · SAME AS LAST WEEK

How we work today.

Interrupt me. Anytime. Dumb questions out loud beat silent confusion.
Receipts to WhatsApp. Wins, screenshots, errors, "I'm stuck" — drop them in. The cohort agent learns from them.
Shitty first drafts welcome. Rough is fine. Honest is required.
Build in public. Drop it in WhatsApp when you ship anything in May.
Feedback is a gift. Both directions.

Quick refresh — these are the same five from May 1. They matter more this week, not less.

01 / 06

📍 State of the Cohort.

A week in. Where we actually are.

SETUP WEEK · MAY 1–7

What you actually shipped.

Peter Walters — 1,096 yoga class transcripts ingested. 572 person canon pages built from 146K emails overnight. 28 mentor pages. Shipped 15 new slash commands + 7 ingest pipelines. Promoted to cohort Guide.
Jonathan Beaton — 140GB of Drive ingesting; first /emerge run May 6. "I just read the first paragraph and got choked up."
David Brits — 20 years of creative output thematically synthesized. "I could see suddenly the unity of it all."
Andrea Zeman — installed, ingesting every transaction + saved emails. Deep in input phase.
Matt Collins · Kevin Losani — installed, first ingests in flight.

Every install bug, every "stuck on step 3" — those become the troubleshooting docs for Cohort 02. See: recursion.

WHERE YOU GOT STUCK

Three frictions we'll fix today.

Git wasn't installed. If Claude wants git, just say "install it for me." Andrea hit this; resolved in one message.
The "crowded problem." Too many nodes when you ingest everything at once. Fix: filter by topic or by people-list. Jonathan + Andrea hit this. We'll demo the workaround.
Token / compute ceiling during heavy ingest. The honest fix: beef up to $250/month during ingest week, downgrade after. Peter and David already did. "Welcome to the club."

And one more, the most common: "I don't know what questions to ask." — that's the Curator's Loop. We'll cover it in the demo section.

YOU'RE NOT JUST USERS

You're co-authors of how this gets taught.

Your friction logs improve the kit. Your Demo Day artifacts become the example library. Your stuck moments rewrite the troubleshooting docs.

$1,000 isn't tuition. It's my Studio buying your output on Demo Day. You're a vendor, not a student.

I know this is a funny way to do it, but I wanted to make sure it was both free and we'd follow through.

02 / 06

📥 Ingest, the long version.

Last week I showed you the 6 pipelines as a grid. Today: one slide each. What it eats. What it makes. When to use it.

📷 PIPELINE 1 · PHOTO-PROCESSOR

Your phone is a sensor.

HaveiPhone dump, camera SD, or Google Photos export.

Doextract_locations.py → event_cluster.py → extract_screenshots.py

Getlocations CSV (drop in kepler.gl) · event clusters by date+place · separate screenshot folder.

Best for: anyone with 10K+ photos. Densest archive most people own.

📦 PIPELINE 2 · TAKEOUT-PROCESSOR

20 years of email is a knowledge base.

HaveGoogle Takeout: Mail + Contacts + Calendar.

Dombox_extract_bodies → build_master_csv → match_contacts → build_relationship_graph

Getevery person you've corresponded with, ranked by message volume + recency.

Best for: anyone with a long Gmail history. The export takes ~1 hour to arrive. Highest ROI ingest in the kit.

💬 PIPELINE 3 · CHATGPT-INGEST

You've already had the brainstorm.

HaveChatGPT export (Settings → Data Controls → Export).

DoDrop into tools/chatgpt-ingest/ · run parse_conversations.py

Getconversations grouped by topic. Run /emerge on top of it.

Best for: anyone who's been talking to GPT/Claude for 6+ months. A mirror of what's been on your mind.

📘 PIPELINE 4 · FACEBOOK-INGEST

Old Facebook is your longest journal.

HaveFacebook archive (Settings → Download Your Information; JSON is easier).

DoDrop into tools/facebook-ingest/ · run fb_to_obsidian.py

Getfolder per person · chronological message threads · contact ranking.

Best for: anyone who used FB heavily 2008–2017. Wedding toasts, eulogies, "how did we become friends" reconstruction.

📰 PIPELINE 5 · PRESS / URL INGEST

Any URL → permanent local source.

Havelist of URLs (one per line) in press-ingest/urls.txt.

Doprocess_articles.py → ingest_to_vault.py (Wayback fallback if the original is dead).

Getcleaned local Markdown · screenshots · canon page · grep instead of Google.

Use case A — press about you. Bylines, dates, outlets, content. Survives the publication pulling the article. Half my press URLs are already 404; the vault still has them.
Use case B — research around a topic, place, or thing. Dump 50 URLs about a neighborhood, an instrument, a regulation, a competitor, a craft. The pipeline pulls clean Markdown. Then /diarize "<topic>" synthesizes a canon page citing every source.

Andrea: market briefings on a neighborhood. Jonathan: research on a TV genre. Pat: competitor brand archive. David: public-art commission research. Same pipeline, different target.

🎙️ PIPELINE 6 · GRANOLA-INGEST

Meetings are the fastest-decay archive.

HaveGranola export (per-meeting Markdown).

DoDrop into tools/granola-ingest/_inputs/ · run ingest · then /granola in Claude.

Getrolling source-note: who you met, what was decided, what's open.

Best for: anyone with regular calls. Re-run weekly — new meetings merge with synthesis. Pair with /drift.

WHERE THE INGEST LANDS

Sources → Source Notes → Canon → Outputs.

04 · OUTPUTS

bios, decks, talks, memos, websites — the public face

▲

03 · CANON

durable synthesis — people, places, themes, frameworks

▲

02 · SOURCE NOTES

processed extracts — interpretation, not raw

▲

01 · SOURCES

immutable raw — articles, transcripts, journals, exports

Every pipeline lands in 01_SOURCES. The skills (/ingest, /diarize, /emerge) move material upward.

03 / 06

✨ What's possible.

Once you have ingested sources, the skills produce real artifacts. Here are four I've shipped from my vault.

OUTPUT 01 · BIO

Three bios in 30 minutes.

Havecanon page about your career (or run /diarize <Your Name> to build one).

DoAsk Claude: "100/300/500-word bio for [audience]. Voice: mine."

Getthree bios. Drop in 06_OUTPUTS/Bios/. Re-run on the latest vault any time.

My vault has 9 bios — three audiences (artist · business · speaker) × three lengths. Re-generate when something changes.

OUTPUT 02 · TALK

A 15-minute talk drafted from your archive.

Havestrong canon pages on a few core topics.

Do/diarize on each topic · brief Claude with throughline + beats · use only canon material.

Geta talk that holds together because it's sourced — every claim has a citation.

My TED talk drafted in two days using this pattern. Three variant drafts → hybrid. ~6 hours including research pass.

OUTPUT 03 · YOUR PUBLIC SURFACE

Your site, lookbook, listings — built from your vault.

Haveany public surface — site, landing page, listing template, lookbook, capabilities one-pager.

DoMove the source files into 06_OUTPUTS/Website Copy/ · edit in Obsidian · push · deploy.

GetOne source of truth. Update a canon page → regenerate the public artifact in 2 clicks.

Andrea — listing pages auto-built from a property canon page
Molly — coaching landing page voiced from her somatic canon
Pat — brand-studio capabilities one-pager + client lookbook
Peter — daily yoga app marketing page from class archive
Jonathan — production company site + project decks
David — muralist portfolio + commission inquiry page

My site is one example. Your "site" might be a Notion page, a Squarespace template feed, a single PDF the system regenerates. Same pattern: vault is the source, the public surface is downstream.

OUTPUT 04 · MEMO

A stakeholder memo grounded in what's actually true.

Haveproject page + 90 days of /recap log entries.

DoBrief Claude: "500-word memo to [stakeholder]. What's working / risks / asks. Canon only — no aspiration."

Geta memo that's about what happened, not what you hoped happened. Optional: /council stress-test.

Keeps you honest with stakeholders. Six months later when they ask "what changed?" — the receipts are right there.

📡 LIVE · FROM THE COHORT THIS WEEK

Or: what these outputs feel like when it's your archive.

"I prompted Claude to give me a set of thematic insights about my creative output over the last 20 years… I could see suddenly the unity of it all — how the 'creative principle' has been working through me in ways that had previously appeared to me to be very fragmented."

— David Brits · Cape Town · WhatsApp · May 3

🛡️ TRUST HIERARCHY

Why outputs hold together: claims travel with their source.

L1Journals · GPSground truth — what & when

L2Business docscontracts, invoices, decks — hard evidence

L3Memoir / autofictioncomposite, dramatized — voice not fact

L4Presssomeone else's framing — myth-shaped

L5Transcriptsperformed in front of an audience

L6Synthesisyour own interpretation — labeled

Mentioned this verbally last week. Dropping the visual today because outputs only hold up if claims travel with their source.

04 / 06

🧠 Pro tips.

Eight rules of the road. Hard-won. Saves you a week of fumbling each.

TIPS 1–2

Start small. Recap always.

Start with one source. Five sources is enough for the system to do something useful. Don't reach for 200 before you've ingested 5.
Run /recap at the end of every session. Otherwise you'll forget what you did and have to figure it out from the file tree. The log is the breadcrumb trail.

TIPS 3–4

Lint weekly. Don't redo what's done.

Run /vault-lint weekly. Catches stub pages, broken links, duplicates, orphans. The system is self-healing if you let it lint.
Don't redo what the system already did. Before writing a bio from scratch, check 06_OUTPUTS/Bios/. Before drafting a memo, check 06_OUTPUTS/Memos/. Past you wrote the right thing — probably.

TIPS 5–6

Workshop, not gallery. Have, not cool.

Vault is the workshop. Outputs are the gallery. Don't share the vault folder. Share what came out of it. The friction is the point — outputs lose their value if everyone sees the wires.
Pick recipes by what you have, not what sounds cool. The fastest path to "oh this is useful" is putting your own data through one full cycle. /emerge sounds magical but it's nothing without sources behind it.

TIPS 7–8

Ingest first. Five is enough.

Ingest first, synthesize second. Every "I don't know what to do next" is solved by ingesting one more thing. Synthesis emerges from density; density emerges from ingest.
Five sources is enough. Don't wait for the perfect 200-source archive. Run /diarize, /emerge, /connect on what you have. The system gets sharper as you add — but it works at 5.

05 / 06

🎬 Open mic.

Who wants to share screen and show what you've built? I'll prompt a few people I know have shipped — but the floor is open.

🔄 BRIDGE · CURATOR'S LOOP

What you'll see in the demos.

YOU

Spot

"This person keeps coming up — make a canon page."

→

CLAUDE

Execute

Reads sources, drafts page, cites every claim.

→

YOU

Codify

Edit, label trust level, link, ship.

You're the curator. Claude is the labor. Watch for this loop in every demo coming up.

PRIMED · PETER WALTERS · COHORT GUIDE

If you want to go first — here's what saturated looks like.

1,096 yoga class transcripts · 146K emails → 572 person canon pages overnight · 28 mentor pages.
Built 15 new slash commands (/mentor, /timeline, /source-check, /war-room, …) and 7 ingest pipelines.
Watch for: the mentor architecture — how he turned voice into infrastructure.

~4 min if Peter wants the screen. Cohort Guide as of May 7.

PRIMED · JONATHAN BEATON

"I just got choked up reading the first paragraph."

Showrunner / producer · Montreal/LA · 140GB Drive ingesting (selective by project — business sensitivity).
Ran first /emerge May 6. The output picked up patterns across 12+ years of pitch work.
Watch for: how he scoped the ingest to not drown — the workaround for the "crowded problem" Andrea also hit.

~4 min if Jonathan wants the screen. He'd show the /emerge output from Monday.

PRIMED · ANDREA ZEMAN

"I'm so in it in the input I don't know what to ask."

San Diego realtor. Transactional archive — every transaction file + every saved email. Less obviously creative; same skills apply.
Hit the "crowded problem" early. We could walk through her vault and pick the one question that unsticks the rest.
Watch for: how /diarize on a single past client breaks the input-overwhelm spell.

~4 min if Andrea wants the screen. This unsticks anyone else stuck in input phase — most of the cohort, by raw count.

🙋 OPEN MIC · WHO ELSE?

Who wants the screen?

Show your vault tour — 90 seconds, pick a folder, read it aloud.
Show one canon page you're proud of (or one you can't figure out how to write).
Run a skill live — /diarize, /emerge, /council, /connect. Even if it fails, we learn.
Show where you're stuck — install error, weird Markdown, "I have 800 sources and no canon." We unstick it together.

Drop your name in chat. I'll pick whoever raises a hand fastest. If nobody does, I run /diarize live on a volunteer's data — but I'd rather see yours.

06 / 06

💬 Q&A.

Whatever you've got. Setup-week friction, recipe questions, "is this normal," what to ingest next. Dumber the better.

UP NEXT

Skills · Outputs · Demo Day.

Today

May 8

Kickoff #1

▲ you are here

Week 2

May 15

/diarize · /council · /emerge

Week 3

May 22

Outputs — bios, decks, sites, apps

Demo Day

June 1

Studio buys what you ship

Always

→

Vault stays open · WhatsApp 24/7

Drop one workflow you want demoed in WhatsApp — I'll attempt it live on May 15.