“I don’t know where to find the stuff that I want to find, and I don’t just want to browse articles for an hour. I know it’s in there. I know we talked about it. And by the way, I don’t just want a quick response — I want to learn. I want to turn that into a teaching path.” — Lou
Session context: 2026-07-16_Mastermind — Lou demoed the Composer, an experimental feature on the member hub, and Mazie recognized her own problem in it immediately.
Core Idea
Every knowledge business with a few years behind it accumulates the same liability: a large, valuable, unnavigable back catalog. The instinctive fixes are search and curation. Both are wrong, for the same reason — they assume the member’s problem is finding content.
Mazie named the real problem in one line: “I’m so far behind in all of the learning here.” She isn’t missing a search box. She’s missing a path. And when Lou confirmed the Composer could build her one, her response was “that would be like a lifesaver” — which is not how anyone has ever described a search feature.
Lou’s diagnosis of why the catalog resists navigation: “Right now those things aren’t organized by course or by learning path. They’re just weekly calls.” The material is organized by when it was produced, not by what anyone needs to learn. Every session archive, podcast back catalog, and newsletter archive has this shape. Chronology is the producer’s organizing principle leaking into the consumer’s experience.
The traditional fix is to go build the courses — pick themes, sequence the material, produce a curriculum. That’s months of work, it’s obsolete the moment you record next week’s session, and it bets your guess about what members need against what they actually need.
The Composer inverts it. The member states where they are and what they want; the system reads across everything — insights, recaps, skills, transcripts, video with timestamps — and composes the path on demand, citing sources so the member can go deeper on any block. Lou’s version pulled from nine sources on a single question and presented the result as an article, not a chat answer. Threads accumulate into a workspace; a workspace can be collapsed into one piece, a newsletter edition, or a learning sequence.
Two things make this more than a better search:
Curriculum becomes a query result, not an artifact. You don’t build ten courses. You build the composition layer once, and every member gets the course only they needed. The catalog stops being something you have to reorganize as it grows — growth makes it better, since there’s more to compose from.
The output is a starting point, not an answer. Lou: “I don’t just want a quick response — I want to learn.” The gap between a chatbot over your archive and this is the difference between answering the question and building the path that makes the question make sense.
Lou’s honest framing, which is the right one for anything at this stage: “I don’t know if it’s overkill, or if it’s just kind of useful.” It shipped as a dev-link experiment, gated on whether members actually use it.
Practical Application
Before building anything, run the diagnostic on your own archive:
- Ask your three most-behind members what they’re trying to learn — not what they want to find. The gap between those two answers is the whole insight.
- Try to answer one of those requests from your catalog by hand. Time it. If it takes you — the person who made the material — more than ten minutes, your members have already given up.
- Ask whether the answer is a document or a sequence. If it’s a sequence, no amount of search will produce it, and a composition layer is the only thing that will.
Coaching question: “Is my archive organized around when I made it, or around what someone needs to learn — and which one am I charging for?”
Related Insights
- Insight - Separate the Conversation From the Document Library — the library is the substrate; the Composer is the layer that reads across it and assembles.
- Insight - The AI Paralysis Triad — Fear, Doubt, and Overwhelm as Compounding Blockers — Mazie’s “so far behind” is overwhelm in its native habitat; a composed path is a structural answer to it, not a motivational one.
- Insight - Multi-Pass Retrieval Turns Shallow Searches Into Strategic Intelligence — the retrieval mechanics the Composer depends on.
Evolution Across Sessions
Establishes the baseline for on-demand curriculum as a member-experience pattern. The vault has extensively covered building the knowledge base and getting knowledge in; this is the first insight about how a member gets knowledge out of a large one — and the first to name chronological organization as the specific defect. It’s also the first live evidence of member demand for it, in Mazie’s reaction. Future sessions should report whether members actually used the Composer, since Lou explicitly conditioned further development on that. Open thread: the video-with-timestamps version and the single-voice audio pipeline (11 Labs / HeyGen) were described but not demoed — the HeyGen pipeline remains deferred pending the Kasimir demo.
Source
- 2026-07-16_Mastermind (Lou — Composer feature and the back-catalog navigation problem; Mazie Zdanowicz — the member-side need)