Authored by: LYRA (subagent session: maker-architect)
Date: 21 March 2026
Status: Draft 1.0 — for Lauren's review
*A guided walk through the rainforest to a summit at night. The customer will work for it themselves — no one can achieve this for them. But we are the Sherpas. We have walked the tracks many times before. We carry the load. We prepare them for challenges. We help if they feel they can't do something.*
This is the product bible for Maker: Personal. It is the expedition map — before a single line of Kajabi is configured, before a single lesson is recorded, before a single asset is built.
Everything in this document flows from one truth: the Sherpa is the product, not Lauren. Lauren walked this trail first. She became LYRA's first builder. That walk is now encoded into every scaffold, template, and just-in-time warning in this product. She doesn't have to walk alongside every student. The trail is already marked.
The student does the work. The summit is theirs. The Sherpa made sure they could get there.
"Real expeditions don't teleport to base camp. Neither do we."
For Everest climbers, the journey to base camp is its own leg. Days of trekking. Altitude adjustment. Gear checks. Anyone who has done it will tell you: base camp is not where the climb begins — it's where it becomes possible.
Getting to Base Camp is the first leg of this expedition. Not the most dramatic. Not the summit. But it cannot be skipped, and it will not be rushed.
What they complete:
1. Machine check — confirm their personal computer can run the agent stack
2. OpenClaw installed — the agent runtime on their machine
3. Anthropic account created — the LLM that gives the agent its brain
4. API key generated — their unique key connecting OpenClaw to Claude
5. Credits loaded — $10–20 AUD is enough to begin (the Sherpa tells them exactly how much)
6. Key configured in OpenClaw — one line pasted, one test run
7. Environment check — green light on everything
What the Sherpa carries:
The just-in-time preparation:
Before the terminal appears for the first time:
*"You're about to open a terminal window. If you've never done this, that's fine — this is the only time it will feel strange. Here's exactly what you'll see: a black screen, a blinking cursor, a single line of text. Type the line we give you. Press Enter. Walk away for 90 seconds. Come back to something that exists."*
Before the Anthropic credits step:
*"You're about to spend money. Not much — $20 gets you started comfortably. Think of it as the fuel for the expedition. You wouldn't start a road trip on empty. Load the tank, then we move."*
The view from base camp:
Environment check: all green. A single confirmation: "You're at base camp. Your agent has a home and a brain. The trail starts here."
The mountain is visible for the first time. The climb begins at the next section.
Seven trail sections. Each has a name, a build, a Sherpa load, a just-in-time preparation, and a view.
"The trail opens. You take the first step."
What they build:
The first session. OpenClaw runs. Their agent speaks for the first time — not yet knowing them, but present, waiting, ready. The cursor blinks. Something is alive on their machine that wasn't there this morning.
What the Sherpa carries:
The just-in-time preparation:
Before first session:
*"Your agent is about to respond to you for the first time. It won't know you yet — you haven't introduced yourself. That's fine. This is just a hello. You're not building anything permanent yet. You're just meeting."*
The view from here:
First response received. The Sherpa prompt: "It spoke. You're climbing. Section 2 is where it learns your name."
"The trail opens. Your agent learns your name."
What they build:
The identity file — the soul of their agent. This is `SOUL.md` (personal edition): who they are, what matters to them, how they want to be spoken to, what their life actually looks like. The agent reads this file at the start of every single session. It is the most important thing they will build.
What the Sherpa carries:
The just-in-time preparation:
Before this section begins:
*"This is the most important section of the entire build. Not the most technical — the most important. What you write here determines whether your agent actually feels like an extension of you or like a generic assistant with your name on it. Take your time. There's no timer. No one is watching. This is just you, describing your life to something that will remember it."*
The view from here:
They read their completed file back. The Sherpa prompts them: "Does this sound like you?" If yes — move forward. If no — a short Sherpa guide: "Here's the one thing that makes identity files feel hollow (and how to fix it)."
The milestone confirmation: their agent, first session, greets them by name using what they wrote.
"The first hard thing. We've been here before."
What they build:
Email integration. Their personal email is connected and their agent can read, summarise, draft replies, and flag what matters. This is the first technical crossing — OAuth, app passwords, permissions. It's also the first time the agent does something real.
What the Sherpa carries:
The just-in-time preparation:
Before the River Crossing begins:
*"This section is the most technically involved thing in the entire expedition. Not because it's complicated — because every email provider does it differently. We've been through every one of them. Here's how this works: we give you the exact steps for your exact provider. You follow them. If something doesn't match what we show you, there's a troubleshooting section that covers every variation we've seen. You won't be guessing. You'll be choosing from a known list."*
The view from here:
Their agent reads their last 10 emails. The student sees the output. Real emails. Their inbox. Understood by something that lives on their machine.
Milestone confirmation: "Your agent just read your email. It will never spam you. It will never share your data. It runs on your computer. Everything stays with you."
"You can see further now. Your agent learns your time."
What they build:
Calendar integration. The agent understands their schedule — what's coming this week, what's been committed, where the blank space is, what they might have forgotten. This is lighter than email technically, but this is often where the emotional reality lands: this thing actually knows my week.
What the Sherpa carries:
The just-in-time preparation:
Before this section:
*"One thing to know before you start: your work calendar is controlled by your employer's IT. Your agent cannot and will not reach into that system without your employer's permission. But there's a workaround that millions of people already use — it's built into every calendar app. We'll show you."*
No apologising for the limitation. Frame it honestly. The workaround is in the Sherpa's pack.
The view from here:
Agent outputs their week. They see it — actually see their own life, summarised, by something that is theirs.
Milestone confirmation: "Your agent knows your time. Next: it learns your life."
"The darkest part of the trail. And the most important."
What they build:
The life context file. This is not technical. It is personal. The student documents their family, their rhythms, their priorities, their health context, their home systems, their financial rhythms. The agent needs to know who they're actually serving — not just their name and email, but the actual texture of their life.
This is the section that separates a generic assistant from their agent.
What the Sherpa carries:
- People (family members, their ages, their quirks, their schedules)
- Rhythms (morning routine, evening routine, weekly patterns, school terms, recurring commitments)
- Priorities (what matters most this season — for them and the family unit)
- Health context (chronic conditions, medications, GP, specialists — what the agent should know)
- Home systems (cleaner schedule, maintenance cycle, service contacts)
- Financial rhythm (pay cycle, recurring bills, savings habit — not amounts, just timing and patterns)
- What overwhelms you (honest prompt — what are the things that pile up and cause stress?)
- What brings you back (what resets you — exercise, reading, cooking, nature?)
The just-in-time preparation:
Before this section, a longer Sherpa note:
*"This section is not technical. It's personal. You're describing your actual life to something that will hold it for you. Some people find this surprisingly moving — writing down the names of their kids, their routines, the things they carry — and realising how much they carry. Some people feel exposed. Both reactions are correct. Your context file lives only on your machine. Nothing leaves. No one else reads it. Take your time with this one. The trail is patient."*
The view from here:
The student tests the agent with a real question about their life. Something specific: "What's happening with the kids this week?" or "I need to plan a GP appointment — what do I need to remember?" The agent answers from the context they gave it.
Milestone confirmation: "Your agent knows your life. It's not a generic assistant anymore. It's yours."
"You've been building. Now you use it."
What they build:
First real workflows. Not setup — actual use. The student builds three personal routines that will run every day: a morning brief, an evening wrap, and one custom routine of their choosing (drawn from a prompted list of common personal use cases).
This is the section where building becomes living.
What the Sherpa carries:
- Today's schedule
- Emails needing attention (flagged by priority)
- One thing to remember from yesterday
- One thing coming up in the next 7 days
- What got done
- What's outstanding
- Tomorrow's first commitment
- One thing to note for the family
- Weekly family logistics brief
- Grocery + meal planning assistant
- Health tracking check-in
- Home maintenance scheduler
- Financial rhythm reminder system
- School term planner
- Personal project tracker
- Reading/learning capture
- Social planning assistant
- Gift and occasion tracker
- Appointment prep briefer
- End-of-week personal review
The just-in-time preparation:
Before the Clearing:
*"Everything you've built so far was setup. From here, you start using. This is where it starts to earn its keep — but it will only earn it if you actually ask it things. The first few requests will feel clumsy. That's normal. You're learning a new muscle. The prompts we've given you are tested and real — Lauren uses versions of all of them. Start with the morning brief. Use it tomorrow morning. Then come back."*
The view from here:
They see their morning brief run for the first time. Real schedule. Real emails. Real life, summarised in 90 seconds.
Milestone confirmation: "You just ran your first personal AI routine. This is what every morning will look like."
"One more ridge. Then the view."
What they build:
Deployment confirmation and personal customisation. The agent is running, the routines are live, and now the student makes it fully theirs — custom instructions, a name for their agent if they want one, and a deployment checklist that confirms everything is working the way it should.
This is the last build before the summit.
What the Sherpa carries:
The just-in-time preparation:
Before the Summit Approach:
*"You're close. The last section is short — it's mostly confirmation and celebration. But it includes one important thing: how to maintain what you've built. Your agent will drift slightly over time. App passwords expire. Email filters shift. Life changes. We'll show you the 20-minute monthly check that keeps everything running. After that — you're done. The summit is yours."*
The view from here:
They run the deployment checklist. Every item: green. The agent is running. It will run again tomorrow, without them doing anything.
Seven moments in the journey where the Sherpa role is most critical. What is happening. What the student feels. What the Sherpa does. What this looks like as a Kajabi product feature.
When: Trail Section 1, first command line encounter.
What's happening: The student is staring at a black screen with a blinking cursor. For many, this is the first time they've opened a terminal in their life, or the first time in years.
What the student feels: A specific combination of intellectual curiosity and low-grade physical fear. The feeling of being outside their competence zone in a way that feels irreversible — what if I break something?
What the Sherpa does: Appears before the moment, not after the panic. A calm, short video: Lauren's actual screen. Her terminal. Her first install. No commentary — just watching someone who knows what they're doing do it without drama. Then a card: "Here is the exact line. Copy it. Paste it. Press Enter. Walk away."
Kajabi feature: A pre-section interstitial video (unlockable only after the previous milestone is marked complete). Autoplay. Short. Not skippable on first view.
When: Trail Section 2, SOUL.md creation.
What's happening: The student opens the identity template and stares at it. They know they're supposed to write about themselves but the prompt feels both too simple (I know who I am) and too strange (I've never described myself to a machine).
What the student feels: A mild version of the blank page problem combined with unexpected introspection. Some will feel vulnerable. Some will feel inadequate — my life isn't that interesting. Some will overthink it.
What the Sherpa does: The worked example (Mel) is placed immediately adjacent to the blank template — not as a comparison but as proof that ordinary, specific, human life is exactly right. A Sherpa note: "If Mel's life looks like a worked example, yours looks like the real thing. Just write what's actually true."
Kajabi feature: Side-by-side layout in the lesson page — blank template on one side, Mel's completed example on the other. Audio autoplay option (Lauren reading Mel's example aloud). A "Save and continue" button that only activates after the template has been edited (word count trigger: >100 words added).
When: Trail Section 3, email connection.
What's happening: Something doesn't work. The most common point of dropout in any technical maker product. The error message is cryptic. The student doesn't know if they've done something wrong or if the system is broken.
What the student feels: Frustration spiking toward resignation. The first maybe this isn't for me thought.
What the Sherpa does: The troubleshooting tree is not buried in a FAQ. It appears in-section, immediately after the connection attempt step, as a direct link: "Didn't work? Go here." The tree covers the 12 most common failure modes — each with a plain-language description of what the error looks like, what caused it, and the exact fix. No generic advice. No "contact support."
Kajabi feature: An inline conditional block after the connection step. Triggered by self-report ("Did it work?" Yes/No). If No: the troubleshooting tree expands in-section. A community prompt at the bottom: "Not in the list? Post a screenshot in Maestro Club — someone has seen it before." (Link direct to the relevant community thread category.)
When: Between Trail Section 4 and 5. After the technical complexity, before the first magic.
What's happening: The student has spent real time on setup. They have email connected, calendar connected, identity file written. But they haven't used it for anything real yet. The work feels abstract. The payoff hasn't arrived.
What the student feels: Is this actually going to be worth it? Am I overcomplicating my life? This is the lowest point on the trail — the darkest part before the canopy opens.
What the Sherpa does: A transition moment between sections — not a lesson, not a prompt. A single page called "The Halfway Mark." Tells the student exactly where they are on the trail (visual trail map, their position marked). Shows them what they've already built. Plays a short video of someone who felt the same thing — and what happened when the agent first ran their morning brief.
Kajabi feature: A milestone celebration page (triggered automatically when Trail Section 4 is completed). Full-width. Not a lesson. Treated like a checkpoint camp, not curriculum. Includes: progress visual, completed assets list, "what's coming" preview, and a 90-second testimonial video from a beta maker (or Lauren's own reflection). This page is Kajabi's "module complete" interstitial repurposed as a genuine emotional beat.
When: Trail Section 6, morning brief runs for the first time.
What's happening: The student asks the agent something real and gets a real answer. Their actual calendar. Their actual emails. Their actual life, understood.
What the student feels: This is the summit preview. A sudden, visceral sense of oh, this is what it is. Some will feel delight. Some will feel something stranger — relief, or a small grief for all the years they didn't have this, or a kind of quiet pride that they built it themselves.
What the Sherpa does: Prepares them for the feeling. A pre-step Sherpa note: "The next prompt you're about to run will be the first time your agent does something real. It won't be perfect. The perfect version comes after you've used it for a week. What it will be is real — and that matters more than perfect right now."
Kajabi feature: After the test prompt step, a reflection prompt (text field, optional): "What did you notice? What surprised you?" These responses (opt-in) feed future product development. A social share prompt: "Your agent just ran its first brief. Want to share that you're an Agent Maestro? [Link / graphic]" — shareable without revealing personal content.
When: Trail Section 6, choosing the third personal workflow.
What's happening: The student is presented with 12 workflow templates to choose from. For some, this is easy. For others, this triggers decision paralysis — too many good options, fear of choosing wrong, not sure what their life actually needs.
What the student feels: Overwhelm disguised as enthusiasm. Frozen by choice.
What the Sherpa does: A decision filter before the menu. Three questions:
1. What is the thing in your personal life that falls through the cracks most often?
2. What's the task you dread but that runs on a rhythm?
3. What would save you 20 minutes if it was just done?
These three answers map to recommended workflows. The menu appears after the filter, with a recommended option highlighted. "Start with the one we've flagged. You can add more after the summit."
Kajabi feature: A short interactive quiz (Kajabi assessment tool, 3 questions) that outputs a workflow recommendation. The recommended template is pre-selected when the menu loads.
When: Trail Section 7, deployment checklist.
What's happening: The student runs through the final checklist. Everything is about to be confirmed as working. This is the moment the product shifts from "being built" to "running."
What the student feels: A combination of anxiety (what if something is wrong?) and anticipation (what if it's all right?). The impulse to check one more time. The fear that the summit might not be what they imagined.
What the Sherpa does: The checklist is not a form. It is a ritual. Each item has a confirmation test — not just a checkbox, but an action to perform and a result to verify. The Sherpa note before the checklist: "This is the last section. After this, your agent runs without you. Not because you've finished — because you've built something that doesn't need you to hold it up anymore."
Kajabi feature: A step-by-step checklist with inline test prompts for each item. A progress bar specific to this section. Final item: a button that says "Confirm deployment" — triggers the Summit milestone in Kajabi's progress system, unlocks the Summit community space, and sends an automated email from Lauren: a personal (templated but warm) note: "You made it. Here's what to do on day one."
The vista from the top.
A completed Maker: Personal experience means this:
What the student has running:
What the agent can do:
What their life looks and feels like after:
The student wakes up. Before they touch their phone, they open their laptop and run one command. In 90 seconds, they know: their day, their priorities, what their family needs, what emails matter. They haven't processed 47 notifications. They haven't opened five apps. They've been briefed by something that knows them.
The cognitive load of managing a personal life — the invisible administration of existing — has been reduced. Not eliminated. Reduced. Enough that there's space again. Enough that they can be present at the dinner table because the logistics are held somewhere else.
They remember things. Not because they wrote them on a sticky note that got lost, but because they told their agent and their agent remembered. Their child's school play. Their GP's recommendation to follow up. The home maintenance task that was supposed to happen in March.
They feel — and this is the part that surprises most people — like they got something back. Not time, exactly. Presence. The sense that life is being lived rather than processed.
They feel like a Maker. Because they are one. They built this. No one did it for them.
What they can do next (visible from the summit):
Four moments where it will genuinely feel hard. Named honestly. Designed for.
What it is: Opening a command line for the first time (or the first time in a decade). The interface of people who know what they're doing.
Why it's hard: It's not technical difficulty. It's identity threat. The terminal says: this is for people who know computers. The employed professional in their 30s who has never touched a terminal has a story about themselves — smart, capable, but not a developer — and the terminal challenges that story the moment it opens.
Why it can't be removed: The agent lives on their machine. It runs from a command line. There is no GUI equivalent that preserves the ownership and portability that makes this product what it is. The terminal is the price of theirs forever. It's worth it.
What the product does:
What it is: Writing the life context file (Trail Section 5). Describing your own life — family, rhythms, priorities, health — to something that will hold it.
Why it's hard: Two different reasons for two different people. Some find it unexpectedly emotional — writing down their family names, their children's schedules, the things they carry — and feeling, perhaps for the first time, how much they carry. Others find it cognitively difficult — they've never articulated their own rhythms because they've never had to. The assumptions of daily life don't have words.
Why it can't be removed: A generic context file produces a generic agent. The specificity is the magic. You cannot shortcut this without sacrificing what the summit is.
What the product does:
What it is: App passwords. OAuth flows. Permission grants. The plumbing of connecting personal email and calendar to an agent that runs locally.
Why it's hard: The steps are unfamiliar. The error messages are written for developers. The flow looks different in Gmail than in Outlook than in iCloud. And because it involves credentials and permissions, the fear of doing it wrong is heightened — the stakes feel higher than they are.
Why it can't be removed: The agent needs to access real email and real calendar to be useful. Local access is what keeps data private and personal. The integration complexity is the cost of genuine ownership. It cannot be abstracted without compromising what the product promises.
What the product does:
What it is: The moment the student gives their agent permission to actually do things — not just read, but draft, summarise, flag, and eventually act. The moment the agent goes from passive to active.
Why it's hard: Giving an AI access to your personal email and calendar is, for many people, the first time they've genuinely trusted something with the administrative layer of their private life. Even when they know it runs locally. Even when they know nothing leaves their machine. The psychological weight of the permission is real. This is not paranoia — it's appropriate caution meeting something genuinely new.
Why it can't be removed: An agent that can only be asked questions manually isn't an agent. The routines, the morning brief, the evening wrap — all of these require the agent to access live data on schedule. The trust step is what separates a toy from a tool.
What the product does:
Specific inventory of what comes pre-built, pre-configured, or pre-templated. What the student does NOT have to build from scratch.
| Asset | What it is | What it saves the student |
|---|---|---|
| One-line installer script | Shell script: installs OpenClaw, creates workspace, runs environment check | 2–4 hours of manual setup, dependency management, path configuration |
| Environment check script | Runs after install; confirms all dependencies, versions, paths | The confusion of "did it work?" |
| Pre-built workspace structure | `/workspace`, `/memory`, `/notes`, `/context` created with placeholder files | Decision fatigue about how to organise |
| Himalaya skill (pre-configured) | Email skill with Lauren's own config as the template; provider-specific configs for Gmail/Outlook/iCloud/Yahoo/Proton | Writing config files from scratch; interpreting IMAP documentation |
| Calendar connector scripts | Google Calendar (OAuth), Apple Calendar (CalDAV), Outlook Calendar | OAuth implementation, CalDAV protocol understanding |
| Provider-specific integration guides | Step-by-step, screenshot-level guides for each email and calendar provider | Generic documentation that doesn't match their screen |
| 12-item deployment checklist | With inline test prompts for each item | Uncertainty about whether "done" means working |
| Troubleshooting tree | 12 most common integration failure modes, each with exact fix | Hours of searching Stack Overflow for cryptic error messages |
| Asset | What it is | What it saves the student |
|---|---|---|
| SOUL.md personal template | Structured identity file template with guided prompts as comments | Blank page paralysis; not knowing what an agent "needs to know" |
| Mel's completed example | Full worked example of a fictional Maker's identity file — specific, human, complete | The feeling that their ordinary life isn't enough |
| Life Context template | Six-section template: People, Rhythms, Priorities, Health, Home, Financial Rhythm | Not knowing what to document; forgetting to include the things that matter |
| Agent naming guide | A short guide to naming (or not naming) your agent — with examples and reasoning | Decision paralysis; feeling silly for wanting to name it |
| Asset | What it is | What it saves the student |
|---|---|---|
| Morning Brief prompt | Tested, formatted prompt for daily schedule + email triage + upcoming events + one outstanding item | Writing prompt engineering from scratch; poor first experiences |
| Evening Wrap prompt | Tested, formatted prompt for day summary + outstanding items + tomorrow's first commitment | |
| 12 additional workflow templates | Family logistics, grocery/meal planning, health tracking, home maintenance, financial rhythm, school term planner, personal project tracker, reading capture, social planning, gift/occasion tracker, appointment prep, end-of-week review | Weeks of trial-and-error prompting |
| Starter prompts library | 50+ tested prompts, categorised by life area (family, health, home, finances, tasks, personal) | Not knowing what to ask; early disillusionment from bad prompt results |
| Custom instruction extension guide | How to add new capabilities as life changes; how to update routines seasonally | The agent going stale; students feeling like they've "finished" |
| Asset | What it is | What it saves the student |
|---|---|---|
| Lauren's terminal video | Real screen, real install, no commentary, 3 minutes | The identity threat of the terminal |
| Lauren's identity file audio | Lauren reads through LYRA's identity file principles (10 min, redacted) | The blank page problem for the soul file |
| Beta maker testimonial video | 90 seconds, genuine, mid-journey — for the Halfway Mark checkpoint | The mid-journey doubt moment |
| "What your agent can and cannot do" explainer | Plain language, specific, honest — what access means and what it doesn't | Fear-based dropout at the trust step |
| Halfway Mark page | Milestone celebration interstitial — not curriculum, not a lesson | The emotional low point between setup and magic |
| Summit confirmation email | Automated, warm, templated — from Lauren — arrives when deployment is confirmed | The anti-climax of finishing alone |
| Asset | What it is | What it saves the student |
|---|---|---|
| Maestro Club access | Community space, read-only during build, full access after summit | Isolation during the build; feeling like the only person doing this |
| #integration thread | Pinned, moderated thread for integration issues — answered by community + periodic Lauren review | Unique error messages not in the troubleshooting tree |
| New templates feed | Community area where new workflow templates are released post-launch | The agent feeling stale after summit; no reason to return |
| Summit showcase | Optional: share your agent's name and first breakthrough moment | The achievement being private and uncelebrated |
A complete visual representation of the expedition — stages, Sherpa moments, Night Walk moments, and the summit.
AGENT MAESTRO MAKER: PERSONAL — THE TRAIL MAP
═══════════════════════════════════════════════════════════════════════
PRE-TRAIL: GETTING TO BASE CAMP
─────────────────────────────────────────────────────────────────────
[ Machine check → OpenClaw install → Anthropic account ]
[ API key → $20 credits loaded → Environment green ]
[ "You're at base camp. The trail starts here." ]
╔═══════════════════════════════════════════════════╗
║ TRAIL SECTION 1: THE TRAILHEAD ║
║ First session runs. Agent speaks. You meet. ║
║ Something is alive on your machine. ║
╚═══════════════════════════════════════════════════╝
│
├── 🔥 NIGHT WALK 1: THE TERMINAL
│ [First command line. Identity threat. Fear of breaking something.]
│ Sherpa: Lauren's terminal video. One line. Walk away. Return.
│
├── 🎒 SHERPA MOMENT 1: THE TERMINAL
│ [Pre-section interstitial. Calm. Specific. No prerequisites.]
│
▼
╔═══════════════════════════════════════════════════╗
║ TRAIL SECTION 2: FIRST LIGHT ║
║ Identity file written. Agent knows who you are. ║
║ First session: agent greets by name. ║
╚═══════════════════════════════════════════════════╝
│
├── 🎒 SHERPA MOMENT 2: THE IDENTITY BLANK PAGE
│ [Side-by-side template + Mel's example. Audio option.]
│ [Word count trigger: must write >100 words to proceed.]
│
▼
╔═══════════════════════════════════════════════════╗
║ TRAIL SECTION 3: THE RIVER CROSSING ║
║ Personal email connected. Agent reads inbox. ║
║ First real data contact. ║
╚═══════════════════════════════════════════════════╝
│
├── 🔥 NIGHT WALK 3: THE INTEGRATION LABYRINTH
│ [OAuth. App passwords. Cryptic errors. Provider differences.]
│ Sherpa: Inline troubleshooting tree. 12 failure modes.
│ Community surfaced here: #integration thread.
│
├── 🎒 SHERPA MOMENT 3: THE INTEGRATION FAIL
│ [In-section conditional. "Didn't work? Go here." — not buried.]
│
▼
╔═══════════════════════════════════════════════════╗
║ TRAIL SECTION 4: THE CANOPY OPENS ║
║ Calendar connected. Agent knows the week. ║
║ Corporate calendar workaround documented. ║
╚═══════════════════════════════════════════════════╝
│
├── 🎒 SHERPA MOMENT 4 [CHECKPOINT]: THE HALFWAY MARK
│ [Milestone celebration page. Not curriculum.]
│ [Progress visual. Completed assets. Testimonial video.]
│ [The mid-journey doubt moment met before it arrives.]
│
▼
╔═══════════════════════════════════════════════════╗
║ TRAIL SECTION 5: THE DEEP CANOPY ║
║ Life context file built. Family. Rhythms. ║
║ Health. Home. Agent knows your actual life. ║
╚═══════════════════════════════════════════════════╝
│
├── 🔥 NIGHT WALK 2: THE BLANK LIFE
│ [Unexpected emotion. Difficulty articulating own rhythms.]
│ Sherpa: Mel. Lauren's audio. People section first.
│ MetaSkill lands: Self-Knowledge.
│
├── 🎒 SHERPA MOMENT [embedded]: THE LIFE CONTEXT GUIDE
│ [Lauren's audio. Template broken into small sections.]
│ [Emotional Sherpa note pre-section.]
│
▼
╔═══════════════════════════════════════════════════╗
║ TRAIL SECTION 6: THE CLEARING ║
║ Three live routines. Morning brief runs. ║
║ First real response. The magic arrives. ║
╚═══════════════════════════════════════════════════╝
│
├── 🔥 NIGHT WALK 4: THE TRUST STEP
│ [Granting active permission. Real data. Real access.]
│ Sherpa: Named as trust decision. Reduced-permission option.
│ Security explainer. MetaSkill lands: Judgment.
│
├── 🎒 SHERPA MOMENT 5: THE FIRST REAL RESPONSE
│ [Pre-step note. Reflection prompt. Social share option.]
│ [The delight moment. The summit preview.]
│
├── 🎒 SHERPA MOMENT 6: THE CUSTOMISATION FREEZE
│ [3-question quiz → workflow recommendation → pre-selected menu.]
│
▼
╔═══════════════════════════════════════════════════╗
║ TRAIL SECTION 7: THE SUMMIT APPROACH ║
║ Deployment checklist. Custom name (optional). ║
║ Everything confirmed. Agent runs without you. ║
╚═══════════════════════════════════════════════════╝
│
├── 🎒 SHERPA MOMENT 7: THE DEPLOYMENT STEP
│ [Checklist as ritual. Inline test prompts.]
│ ["Confirm deployment" button — not a checkbox.]
│
▼
╔═══════════════════════════════════════════════════╗
║ ★ THE SUMMIT ★ ║
║ ║
║ Agent deployed. Running. Theirs. Forever. ║
║ ║
║ Morning brief: live. ║
║ Evening wrap: live. ║
║ Custom routine: live. ║
║ Email: read, summarised, draft-ready. ║
║ Calendar: known, flagged, prepared. ║
║ Life context: held, remembered, accessible. ║
║ ║
║ They built this. It is theirs. ║
╚═══════════════════════════════════════════════════╝
│
▼
POST-SUMMIT
─────────────────────────────────────────────────────────────────────
[ Summit confirmation email from Lauren (automated, warm). ]
[ Maestro Club: full access unlocked. ]
[ Summit Showcase: optional share. ]
[ New templates feed: ongoing. ]
[ Path visible: Maker: Entrepreneur (if they want more). ]
═══════════════════════════════════════════════════════════════════════
LEGEND:
╔══╗ Trail Section (major build stage)
🔥 Night Walk Moment (genuinely hard — named, designed for)
🎒 Sherpa Moment (critical Sherpa intervention)
★ Summit
═══════════════════════════════════════════════════════════════════════
For the person building this in Kajabi.
Product type: Kajabi Course (not a community product, not a coaching product — course with community attached)
Milestone gating:
Video strategy:
Automations to configure:
Community (Maestro Club) access:
The 7 MetaSkills — just-in-time appearances:
What Lauren records:
1. Terminal install video (silent screen recording, 3 min)
2. Identity file audio (her voice, her real principles, redacted, 10 min)
3. Halfway Mark video (her face, her reflection, 90 seconds — genuine)
4. Summit confirmation email (template, warm, personal)
5. Provider-specific integration guides (screen recordings, one per provider)
What Lauren does NOT record:
End of document.
This is the expedition map. Everything else is terrain.
Document version 1.0 — 21 March 2026
Author: LYRA (subagent session: maker-architect)
For Lauren Dare / Agent Maestro Academy