COHORT 01 · SESSION 04 · MAY 22 2026

Outputs week.
7 days to Demo Day.

You spent three weeks building density. Today is about turning that density into things — decks, sites, tools, kits, agents — and walking into Demo Day Friday with one of them in your hand.

TODAY'S 60 MINUTES

01What you shipped this week8 min
02What I shipped this week5 min
03How outputs actually get made — ingredients · directions · recipe15 min
04Open mic — who wants to share what they've shipped12 min
05Demo Day · the details12 min
06Homework · Q&A · close8 min

01 / 06

🏁 What you shipped.

Receipts since Session 03. I picked seven. There are more — these are the ones that show range.

WEEK 3 · RECEIPTS

Seven that show range.

Peter Walters

Gave a live talk — built the deck end-to-end in the vault: peter-show-tell.vercel.app. "It was all Claude and Obsidian — I didn't write a word." Also: 50 city guides in parallel, Meta API wired into IG analytics.

Pat Monahan

Shipped radiantson.netlify.app — second project this cohort. Lovable for visualization, Claude Code for the build, vault as the spec.

Mike Zuckerman

2K iCloud photos → metadata extraction → live travel heat map: splendorous-stardust-3b49ef.netlify.app. "I've outsourced my memory into the vault."

Jonathan Beaton

Datomic-backed everything-app prototype with generative views. Demo videos in WhatsApp. Next: Gmail + iMessage + Calendar interception → auto-diarize.

Adam Mischke

Built a /my-voice skill that captures how he writes from years of Facebook / X / SoundCloud / MySpace archives. Also: agent-driven Strudel music generator (livecoding from CLI).

Tami T

Three outputs in one week: Zen Den short-term rental deck (14p) · Wally's Social Media Strategy (34p) · Trust Executor Starter Kit + Annual Accounting templates (AZ law, transferable).

Matt Collins

L3 wholesale brand deck v1 → v2 with pro photos same evening. The skill is now reproducible — first instance of a member's output becoming their own productized template.

Plus: David's Claudian-in-Obsidian power-user write-up, Kevin's cohort tutorial video, Nate's auto-generated session summaries, Andrea cooking on the realtor engine, Barry working the autobiographical script, Ian's Blender pipeline live. Welcome Matt Wiggins, Marta H, Adam Leber, Lexi McClay, Gil, Zach Bell, Ben Uyeda, Andrea Z, Nicole — drop a "here" in WhatsApp.

PATTERN · WORTH NAMING

Last week half of you were creating. This week you're shipping.

Two weeks ago: I'm still ingesting. One week ago: I have an output, kind of. This week: here's the URL. That curve is the whole point of the cohort.

Demo Day in 7 days. Whatever curve you're on is the curve you've got — protect it.

02 / 06

🛠 What I shipped.

Three this week. I'm in the cohort too.

MY WEEK · 1 OF 3

A DTC go-to-market in three days.

Regulated category — messaging compliance is a maze most agencies eat months on. Vault is doing the regulatory lift. Brand voice, channel plan, ad copy, supply-chain comms drafts — all sourced from the same canonical spec.

"I've done 2–3 weeks worth of work (on the old timeline) in the past 3 days. Finding the edges where humans still need to be part of the fit-and-finish before work product ships — but damn, source-of-truth-guided GTM is a powerful thing."

NDA on the brand. You'll see it when it's live. The point isn't the product — it's that the vault carried the compliance load.

MY WEEK · 2 OF 3

1,000+ artworks, finally organized.

A decade of scattered work — series, single canvases, collaborator collections, lineage where one painting got painted over into another. The vault now treats the archive as a lineage graph, not a list. Master CSV outputs both an œuvre view (everything that ever existed) and a physical inventory view (what's still in the world).

Same pattern most of you will hit: your archive isn't a folder. It's a graph. The vault is the only place that lets you say so.

MY WEEK · 3 OF 3

Claude figured out how to mine.

Set up a node on btx.dev. Clicked allow a lot. 20 BTX overnight for $20 in compute. Now spec'ing a home rig — Claude went to Amazon, filled the cart with a 5090 build. I'm in the desert; the renewable upside is the actual reason.

Tier-3 fun mode. Not a Demo Day artifact. Included because the pattern is the move: "figure out how to do this thing I don't yet know how to do, then do it." That's the cohort posture for the next 7 days.

03 / 06

🍳 How outputs actually get made.

Ingredients · Directions · Recipe. Pick one of each. Ship.

THE FRAME

Most of you are stuck because you're picking the wrong axis.

When the cohort says "I don't know what to ship," they usually mean: I haven't separated the ingredients (what's in the vault), the direction (what shape it takes), and the recipe (what I do to combine them).

Decoupling them turns one stuck question into three simple ones. Two of those questions are basically already answered for you by what's in the vault.

INGREDIENTS × DIRECTIONS

Pick one from each side.

IngredientsWhat the vault has

Voice corpus years of journals, emails, posts, transcripts
Archive work product, clients, sessions, photos
Mentor / council bench researched voices of people you learn from
Decisions in flight pricing, hiring, scope, direction
Process IP how you actually do the work — workflows, templates
External feeds IG/Meta API, Granola, Spotify, Apple Health

DirectionsWhat shape it takes

Web deck Peter's talk · Matt C's L3 wholesale deck
Web app music.peteryoga · radiantson · omni-profile
Dashboard / map Mike's photo heat map · Peter's IG analytics
Kit / template Tami's trust executor · my session templates
Skill Adam's /my-voice · Peter's 15 commands
Agent / pipeline Adam's Strudel · Jonathan's everything-app · Ian's Blender

6 × 6 = 36 cells. Almost every cell is a viable Demo Day artifact. The combinations the cohort has shipped so far cover maybe 10 of them.

THE RECIPE · 5 STEPS · 1 PAYOFF

What you actually do.

SEED

A question, a brief, a one-line ask. "Build me a wholesale deck for L3." Not "make something cool."

DENSITY CHECK

Ask Claude: "do I have enough in the vault to do this well?" If no, ingest first. If yes, proceed.

SHAPE

Name the direction. Deck? App? Kit? Don't let Claude pick. You pick.

BROWSER PREVIEW

"Give me a browser preview." Five words that turn a markdown draft into a live site. Then password-protect and share.

REAL REACTION

Show one person who isn't in this group. Their face is the only review that counts. Iterate from there.

SHIP TO THE STUDIO

Demo Day. Studio buys. You did the work — now collect.

THE UNLOCK · COPY THIS PROMPT

The five words that turn a draft into a site.

Give me a browser preview of this output. Make it a single-page site, mobile-responsive, password-protected. Then deploy to GitHub + Vercel. Tell me the URL when you're done.

It will install what it needs. It will figure out the deploy. It will hand you a URL. That's the workflow. Peter's talk deck, my session decks, Mike's travel map, Pat's radiantson — all started with some version of this.

ANTI-PATTERNS · WHAT NOT TO DO

Four things that kill outputs.

Polishing before you've shipped. v1 in front of one human beats v5 in your drafts folder. Ask Matt C — v1 deck Saturday, v2 with pro photos Saturday night.
Letting Claude pick the shape. "Make me something useful from my vault" returns a generic report. You name the shape.
Ingesting forever. Density doesn't help you if you never combine. Set a hard line: "I'm shipping by Sunday." Then do.
Building for an imagined audience. One real person beats a theoretical demographic. Mom counts. A friend counts. Don't make it for "creators."

04 / 06

🎤 Open mic.

Who's got something to share? Live URL, half-finished sketch, hard question — all welcome. Raise a hand in chat.

HOW TO SHARE · 3 MINUTES EACH

Drop the link. Share your screen. Tell us the seed.

Drop your URL in WhatsApp as you go up — easier than typing it.
Share the screen — show the thing, not a slide about the thing.
Tell us the seed: what was the brief? Why this shape and not another?
Tell us what fought back — what did Claude get wrong, where did you have to step in?
End with one ask — feedback you want from the cohort, a specific stuck point, who you want to talk to.

Half-shipped is fine. Stuck-and-asking-for-help is fine. If you've got nothing live yet, drop the blocker in chat instead — easier to unstick three of you in 30 seconds than one of you alone all week.

05 / 06

🏁 Demo Day. This Friday.

May 29 · 10a–12p MST · two hours · cohort only · Studio buying. Here's exactly what that looks like.

DEMO DAY · LOGISTICS

The shape of Friday.

When

Friday May 29 · 10a–12p MST — one 2-hour session. Recorded.

Where

Google Meet · link drops in WhatsApp Thursday May 28 night. Same gate as the kickoff.

Per member

~7 minutes. Hard stop. 5 min demo · 2 min Q&A from the room. I'll keep time.

Format

Share screen. Show the working thing. Not a slide deck about the thing — the thing itself, live.

Bring

(1) One live URL or runnable artifact. (2) A one-line description of what it does. (3) A price you'd charge a stranger for it.

Audience

Peers only. No guests, no investors, no outside eyes. The cohort is the room — that's the point.

WHAT COUNTS · WHAT DOESN'T

The bar: one working thing the Studio would pay for.

CountsWorking things

A live URL password-protected is fine
A runnable kit templates + SOP + a working example
A skill bundle commands + docs others can install
An agent or pipeline runs end-to-end with a real input
A productized service "send me X, I send you Y" — paid once already counts

Doesn't countNot yet

A plan a doc describing what you'd ship
A pitch slides about a product that doesn't exist
A screenshot of something you almost built
A vault tour your file structure isn't the artifact
"Coming soon" on Friday the soon has to be now

Polish is not the bar. Working is the bar. Ugly + live beats beautiful + theoretical.

BETWEEN NOW AND FRIDAY

The 7-day arc.

May 23–24 (this weekend): ship v1 in front of one human outside the group. Not the cohort. Not your spouse. One stranger-ish person.
May 25–27 (Mon–Wed): iterate on the one piece of feedback that hurt the most. Don't iterate on praise.
May 28 (Thursday): lock the demo flow. Rehearse out loud once. Drop the URL in WhatsApp by night.
May 29 (Friday) · 10a–12p MST: Demo Day. 7-min slot. Live thing.

06 / 06

💬 Homework & close.

Three things before Sunday. One question before we hang up.

THIS WEEK · HARD HOMEWORK

Three things before Sunday.

Name your shape. Pick one cell from the ingredients × directions grid. Drop it in WhatsApp tonight. "I'm shipping a [direction] using my [ingredients]." One sentence.

Ship v1 in front of one stranger. Not the cohort. Not your spouse. One real outside human. Their reaction is the only signal that matters this weekend.

Drop a live URL in WhatsApp by Sunday night. Password-protected is fine. Working trumps polished. If you can't drop a URL, drop the blocker — I'll help unstick.

Stuck mid-week? Ping in WhatsApp — I'll do a 1:1 unblock Thursday before Demo Day Friday.

WHERE WE ARE · WHERE WE'RE GOING

You are here.

Tour

May 1

System tour · ✅

Kickoff

May 8

First session · ✅

Skills

May 15

diarize · council · emerge · ✅

Outputs

May 22

Today · ingredients × directions · demo prep

Demo Day

May 29

10a–12p MST · Studio buys what you ship

Q&A — what's the question that's been sitting in your draft folder?

See you Friday.

7 days. One working thing. Seven minutes. Let's go.