📱 Rotate to landscape for the full deck experience — most slides are designed wide.

🔒 COHORT 01 · SESSION 03 · MAY 15

Skills Deep-Dive

Same password as last week. Check WhatsApp.

 

tap the link in WhatsApp · password unlocks the deck

COHORT 01 · SESSION 03 · MAY 15 2026

Week 1 in the rearview.
Skills hour today.

One week ago we did Kickoff. Some of you shipped real outputs in seven days. Some of you are still in input. Both are on the curve. Today: /diarize, /council, /emerge — live, on your own data.

TODAY'S 60 MINUTES

  • 01Victory lap — what the cohort shipped5 min
  • 02The pattern — five loops you just ran3 min
  • 03Skills hour — /diarize · /council · /emerge live30 min
  • 04Demo Day in 17 days — your artifact10 min
  • 05Cost · Privacy · Everything-app sub-thread5 min
  • 06Q&A + this week's homework7 min

01 / 06

🏁 Victory lap.

Receipts from week 1. Don't gloss past them.

WEEK 1 · WHAT THE COHORT SHIPPED

Receipts.

Peter Walters
7,567 files · 27M words · 572 person canon pages overnight · IG-analytics dashboard via Meta API · shipped music.peteryoga.com with 1,500 yoga playlists · rebuilt his brother's company site in an afternoon · authored 15 new slash commands on top of the kit's 11.
David Brits
20 years of creative archive ingested. First canon view at 4am, sobbing tears: "the unity of it all… I had some kind of deep awakening last night."
Jonathan Beaton
140 GB ingested. Got choked up reading his first /emerge output paragraph. Building an everything-app on a Datomic data model.
Matt Collins
From "what is Obsidian?" Saturday morning to a 10-page wholesale brand deck for L3 Designs Saturday night → v2 with pro photos two hours later.
Mike Zuckerman
Fought a Git install for days. Updated macOS, unlocked. Shipped his first non-text output — a flight-history travel map.
Kevin Losani
Published a short-form video on how he interacts with Claude Code. Cohort getting taught by the cohort.
Adam Mischke
CLI-native, already running an equivalent system on his side (DocVault). Sharing patterns back upstream.
Pat Monahan
Found his framework: set goals → ask Claude which inputs need active attention vs. set-and-walk-away → work the prioritized list of outputs that move the needle.
Tami T
Used Claude to analyze a restaurant menu for missing flavor profile pre-service. Saturday cooks the test.

SATURDAY POLL · MAY 9

Where you actually said you were.

6
Creating outputs
2
Ingesting · "I think I get it"
1
Having trouble setting up

Normal distribution at day 7. The 6 didn't start there. Peter cried at his own ChatGPT bill yesterday — don't get jealous of the front of the pack. They're paying for the privilege of being on fire.

02 / 06

🔄 The pattern.

Five loops just fired in this room. Worth naming once.

WEEK 1 · FIVE LOOPS

What you watched this week is the system being a demo of itself.

1
Ingest → synthesis → personal insight. David at 4am. "The unity of it all."
2
Vault → output → web artifact. Peter's music site. Matt C's deck. Mike's travel map.
3
Skill use → new skill → shared back. Peter's 15 commands on top of the kit. Eligible for v2.
4
Member question → peer answer → group knowledge. Peter as Guide. That's the pattern, not a coincidence.
5
Cohort use → pattern → system upgrade. Your install bugs become /welcome and /stuck. Your Demo Day artifacts become the example library Cohort 02 sees on day one.

WHAT IT MEANS

Recursive pedagogy isn't a vibe.

It's a measurable thing that already happened to you this week.

— Receipts: Peter's commands, David's testimonial, Mike's Git story now in the troubleshooting docs, the WhatsApp transcript already feeding this deck.

03 / 06

🛠 Skills hour.

Three skills. One vault. Live.

SKILL 1 · BACKWARD

What just happened on Tuesday.

/diarize
What
Cross-source synthesis for a single day or range. Pulls journal entries, meeting notes, voice memos, photos with metadata, calendar items, sales calls — and writes the canonical what happened, why it mattered, what changed downstream.
Why now
Most of you have a week of new ingest. /diarize over the last seven days will surface your own week-1 patterns — the fastest way to feel the system's compounding before Demo Day.
Watch
Where it crosses sources — that's the magic the kit doesn't otherwise sell. The output gets dense around 10+ sources for a day. Below that, it just summarizes.
/diarize · LIVE RUN
Volunteer
Peter Walters · vault: last 7 days · 200+ sources to choose from
Prompt
/diarize 2026-05-08 to 2026-05-14
Look for
The moment it cross-references the IG-analytics ingestion with a journal note about "feeling stuck on growth." That bridge is the value.

Volunteer can decline live read — fall back to Matt's vault for the demo. Either way, name the cross-source moment when it appears.

SKILL 2 · FORWARD

What should I do about this.

/council
What
Anonymous 5-advisor review of a real decision. Each advisor is a tier-matched mentor from your /mentor library — synthesized from each mentor's actual writing and recorded talks that you've ingested.
Why now
Every one of you has a pending decision. Pricing. Whether to take a client. Whether to ship rough. Whether to fire someone. The cohort is full of decisions that have been pending for weeks because there's no good way to think them through alone.
Watch
The disagreements between advisors — that's where the surface area for your own judgment lives. If all 5 agree, the question wasn't hard.
/council · LIVE RUN
Volunteer
Whoever drops a real pending decision in chat in the next 30 seconds
Default decision
Andrea: "Should I lead with the agent-factory direction or stay focused on the realtor touchpoint engine?"
Look for
The disagreement. If two advisors split — that's the call you actually have to make. Synthesis isn't the goal; clarity about the trade-off is.

SKILL 3 · SIDEWAYS

What's the thread I haven't named yet.

/emerge
What
Looks for patterns across your vault that you haven't named yet. Returns 3–5 candidate "themes you didn't know you had."
Why now
A week of ingest produces enough signal for the first real patterns. Run it now, get something honest. Run it next week, get something richer. Run it Demo Day, you have a thesis.
Watch
The top theme. If it feels true and surprising, that's the spine of your Demo Day artifact. If it's already obvious, the vault isn't dense enough yet — keep ingesting.

This is the skill that made Jonathan choke up at his first output paragraph.

/emerge · LIVE RUN
Volunteer
Jonathan Beaton · 140 GB ingested
Prompt
/emerge — top 3 themes, surface only
Ask the volunteer
"Does the top theme feel true?" — if yes, that's the spine. If no, what's missing from the vault is the assignment.

COHORT EXTENSION · TRY THIS WEEK

Peter wrote 15 new commands on top of the kit.

Three that extend tonight's session directly:

  • /mentor — critique from named real-person mentors using their researched voice + critique style. Tier mode, pair mode, disagree mode.
  • /war-room — 5-advisor anonymous peer review (Karpathy method). The next move once your /council roster has strong written voice.
  • /timeline — date-anchored chronological page from scattered evidence. Pairs with /diarize.

Whole set is in his shared skill bundle. v2 of the kit pulls from this. Cohort is now the upstream.

04 / 06

🏁 Demo Day · 17 days.

Some of you know what you're shipping. Some don't. Both are fine today. Neither is fine in a week.

DEMO DAY · MON JUNE 1

Your working hypothesis.

Peter Walters
Daily yoga app · music.peteryoga.com is the spine
Pat Monahan
Brand-brief / merch-deck generator for hospitality clients
Jonathan Beaton
Auto-generated TV pitch deck — sci-fi-rooted-in-fact show
Andrea Zeman
Realtor touchpoint engine · auto-emails, market briefings, listing inputs
Kevin Losani
Storyline-discovery tool from 60TB of documentary footage
Matt Collins
Wholesale deck skill productized from L3 v1 → v2
Mike Zuckerman
Travel/movement intelligence — flight map is v0
Barry Silver
Autobiographical performance script
David Brits
Second-brain dashboard for 20-yr archive
Tami T
Restaurant social/menu intelligence — Saturday tests the menu
Nate Uyeda
Place-build framework from Art City work
Adam Mischke
DocVault patterns abstracted for the kit
Ian Warner
Blender × Claude rendering pipeline (already wired)

Read the room — let people revise live. "That's not quite right anymore" is the right answer in week 2.

THE COMMISSION CONTRACT · STILL THE DEAL

$1,000 isn't tuition.

It's my Studio buying your output on Demo Day. You ship — I buy. That's not a metaphor.

The artifact doesn't have to be polished. The bar is one working thing the Studio would actually pay for. Not a finished product. A working thing.

05 / 06

💸 Cost · 🔒 Privacy · 🧩 Everything-app.

Three quick answers to questions that came up this week.

TOKEN ECONOMICS · THE HONEST ANSWER

Three things to know about cost.

  1. $20 is for after-the-fact users. You are during-the-fact users. Ingest is expensive. Synthesis is expensive. Both are front-loaded.
  2. Beef up during ingest. Downgrade after. Real pattern from this cohort. David flagged it. Peter is on Max and still hits limits — because he's running 10 things in parallel. That's a choice, not a requirement.
  3. For overnight / batch jobs, use a harness — not the Claude interface. Hermes / open-claw / a simple agent loop. The interface throttles by design. CLI + a runner doesn't. (See Adam's repo if you're technical. For most of you: not yet — bookmark.)

TRUE NORTH

Token maxxing while compute is cheap.

I have a post-it on my bathroom mirror that says it.

Anyone who wants to argue about the cost can argue with me in two years.

PRIVACY · WHERE YOUR DATA ACTUALLY LIVES

Your vault is a folder on your computer.

That's the answer. Privacy depends on what touches that folder.

  • Tier 1 · local-only: geo, IDs, finances, health, contacts. Local until you decide otherwise.
  • Tier 2 · cloud OK with normal hygiene: work product, projects, drafts.
  • Tier 3 · whatever: public-facing essays, talks, decks.

If you wouldn't email it to a stranger, don't send it to a cloud LLM without thinking. If you would, ship it. Full version is pinned in WhatsApp from Tuesday.

EVERYTHING-APP THREAD · YOU'RE NOT ALONE

Three of you are converging on the same thing.

  • Adam Mischke — CLI-native DocVault, Datomic-ish data model
  • Jonathan Beaton — Datomic data model + generative views
  • Peter Walters — generative city-guide builds, 50 in parallel

Three independent builds. Same direction. The kit didn't ship with this — you're surfacing it on your own.

Jonathan invited cohort-internal videochat. Take him up. If you're in this thread and want my read: drop the link in WhatsApp, I'll do a 30-min review Saturday.

06 / 06

💬 Q&A & homework.

What's the question that's been sitting in your draft folder.

THIS WEEK · SOFT HOMEWORK

Three things before Sunday.

1
Run /diarize on your last 7 days. Drop a screenshot in WhatsApp if anything surprises you.
2
Run /emerge once. Read the top theme aloud to yourself. Decide if it's the spine of your Demo Day artifact, or a distraction.
3
Name your Demo Day artifact in WhatsApp. Even if it changes next week. A named thing is a thing. An unnamed thing is an idea.

Saturday office hours again if anyone gets stuck — same time, same Meet link. Not recorded, no pressure.

WHERE WE ARE · WHERE WE'RE GOING

You are here.

Tour
May 1
System tour · ✅
Kickoff
May 8
First working session · ✅
Skills
May 15
Today · diarize · council · emerge
Outputs
May 22
Rough cuts · artifact rehearsal
Demo Day
Jun 1
Studio buys what you ship

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

See you in seven.

Saturday office hours if you get stuck. Otherwise next call Friday May 22.

COHORT 01 · SESSION 03 · MAY 15 2026
press N for script · S for speaker view · F for fullscreen