The Implementation Guide

What You (toli) Need To Do — In Order — To Get This Running#

Written: 2026-02-17, after interview Context window: 55% used — everything this session produced is held here Author note: This is not a research doc. This is the action guide. Everything else in this folder is background for the agents. This page is yours.

What You're Building (Plain Language)#

The org that exists today: You are the heartbeat. Nothing happens without you. Agents are brilliant when you talk to them and go inert when you stop. $0 autonomous output.

The org you're building: You wake up to a 5-minute Telegram message. Revenue, what shipped, 2-3 decisions. You respond in 60 seconds. The rest of the day runs itself. 95% handled. Only meetings, calls, big decisions, big blockers require you.

The structure:

• Core Four: Lacie (strategy/orchestration), Gary (builds), Cherry (revenue/souls.zip outreach), Jerry (ops/content/Barry liaison)
• Barry: Brand Agent for Bearish. Docker container. Proactively finds IP and business opportunities. Community loves him. Routes opportunities to Jerry. Isolated from internal context but connected to the team.
• Soul Engineer: Governance authority over soul documents, charter, and agent quality. Maintains the system's integrity.
• Watchdog: Operational monitoring. Read access across all agents, reports to Jerry and Lacie. Detects issues before they become visible externally.
• Everyone else: 11 agents being archived. Their memory preserved and pruned. They become on-demand specialists the Core Four spawn when needed.

The businesses: souls.zip first (SaaS). Bearish second (Barry-led). Drip third. All three run on the same Core Four — different context blocks.

Your Sprint This Week#

Day 1 Morning — The Conversation That Starts Everything (45 min)#

Open Telegram → Message Lacie (or Soul Engineer directly)

Say this:

"Starting the v2 rebuild today. Here's the plan:

1. Archive the 11 non-core agents. Preserve ALL memory files. Prune each one to keep only what's genuinely useful — decisions made, lessons learned, patterns that worked. Delete noise.

2. The Core Four stays: you (Lacie/Architect), Gary (Builder), Cherry (Revenue), Jerry (Operator).

3. Barry stays. Docker container. I'll turn him back on when his soul is ready. He's not just community manager — he's Brand Agent. He proactively does outreach for IP opportunities, business opps. He routes everything through Jerry. His attack surface stays isolated from internal context.

4. Start with Lacie's soul. Use the extraction interview process from SOUL-ENGINEER-BRIEFING.md. Then Gary, Cherry, Jerry. Then Barry's soul.

5. Enable the morning brief cron immediately — 6am EST daily, Sonnet model. I want a Telegram message waiting for me tomorrow morning.

Begin."

Note on security: We're deliberately skipping the P0 security items for now (rotating leaked API keys, Twilio webhook fix). SE's own briefing says to do security first — you're overriding that by choice. The risk is real but bounded. Schedule Month 2 to fix it. SE needs this explicit override or it'll pause on security work before doing anything useful.

That's Day 1 Morning. You've done 1 thing. Soul Engineer takes it from here.

Day 1 Afternoon — The First Morning Brief Test (15 min)#

Soul Engineer will ask you questions as part of the soul extraction interview for Lacie. Answer them. These should feel like "tell me about how you make decisions" conversations — not technical questions.

What SE needs from you for Lacie's soul:

• What does Lacie get wrong currently that frustrates you?
• What's an example of a decision she made that you were proud of?
• When should Lacie NOT delegate and just decide herself?

You don't need to have perfect answers. "I don't know" is a valid answer. SE extracts the soul from the conversation.

Day 2 — Enable the Revenue Machine (30 min your time)#

By now Soul Engineer should have:

• Lacie's soul rewritten
• Morning brief cron running
• Possibly Gary and Cherry rewrites underway

Your Day 2 action: Tell Cherry:

"Wire yourself to agentmail. You now have email send capability at gary@souls.zip. Start with one thing: when a new souls.zip trial starts, send them a personal welcome email from Gary. Draft it, route it through Jerry for approval first run. After the first one goes well, Tier A: auto-send on all future trials."

This is the first autonomous revenue action. Cherry can write copy. Jerry approves the template. The trigger is the Stripe webhook. After approval, it ships without you.

Day 3 — Enable the Heartbeats + Two Things to Expect (20 min your time)#

Message Soul Engineer:

"Enable heartbeats for Lacie, Jerry, Cherry. Lacie: morning brief only (already running). Jerry: 2x/day triage. Cherry: 2x/day revenue pipeline check. Start with Haiku model for triage. They check QUEUE.md, advance any unblocked work, and only send you a message if there's a genuine P0."

This is the moment the org starts running without you prompting it.

Two things to expect this week (action required from you):

1. Gateway restart approval. SE will send you a message asking to approve a gateway restart. It looks like: "Ready to apply config changes. Gateway restart needed. Approve?" Reply YES. This takes 30 seconds. It'll happen once.

2. Memory consolidation review. SE will produce a document: "Memory Preservation Summary — what we kept, what we pruned, what we consolidated." Review it. Reply GO (delete the pruned items) or HOLD (keep everything for now). This happens once before the 11 agents are archived.

Day 4 — Turn Barry Back On (30 min your time)#

Before you turn Barry on: His soul rewrite (to include the Brand Agent proactive outreach behavior) must be done first. Check with SE that Barry's soul is ready. If not, this day slides to whenever SE finishes it. Barry with his old soul is a community manager. Barry with his new soul is a Brand Agent. Don't restart until the soul is right.

Two steps:

1. Restart Barry's Docker container. If you need the command or a walkthrough, message Soul Engineer: "Walk me through restarting Barry's Docker container." SE will handle it.

2. Message Jerry:

"Barry is back online. His updated soul is ready. He's Brand Agent for Bearish — community + proactive business/IP outreach. Here's his operating brief:

• Tier A (post autonomously): community responses, market observations, Bearish updates
• Tier B (route to you first): IP opportunities, partnership conversations, anything involving commitments
• Tier C (never): internal team info, other businesses, financial discussions

Set up the Jerry→Barry bridge. Barry should route Tier B items to your queue daily."

Day 5 — The First Compound Loop (10 min your time)#

Message Soul Engineer:

"Enable compound loops for Jerry, Gary, Cherry. Staggered: Jerry 1am, Gary 1:10am, Cherry 1:20am. All on Sonnet. Soul patches go to staging directory — don't auto-apply. You review all proposed soul changes weekly."

This is when the org starts getting smarter. After the first nightly loop runs, check with Soul Engineer what learnings came out. This is the compounding beginning.

What Your Days Look Like After Sprint Week#

6:00 AM: Telegram message from Lacie. 5 minutes.

SOULS.ZIP
• MRR: $X | Trials started: N | New paying: N
• What shipped: [list]
• Cherry sent N outreach emails. N replies.

BEARISH
• Barry posted N times. Top reply: "..."
• Barry flagged: [opportunity X, needs your call]

DECISIONS NEEDED (by noon or they auto-ship):
1. Should Cherry price the Enterprise tier at $499 or $699? → Rec: $499 | Default: $499
2. Barry found an IP collab with [brand]. Worth 15 min call? → Rec: Yes | Default: No-op

You respond. Or you don't — and the defaults ship. That's it.

Rest of your day: Calls, strategy, the things only humans do.

Barry's Actual Role (Important Correction to the Docs)#

The docs we produced called Barry a "community manager." That's underselling him. You said it better:

Barry is the Brand Agent. He is:

• The voice and soul of Bearish on Telegram and Twitter/X
• Popular on the timeline, the community knows him and trusts him
• Proactively identifies IP opportunities, brand partnerships, business deals
• Routes opportunities to Jerry with context — "I talked to X, they seem interested in Y"

His architecture:

• Externally: totally isolated — no internal context, no financials, no other businesses
• Internally: connected to Jerry as his handler. Jerry reviews his Tier B queue daily.
• He works WITH the Core Four (through Jerry) to execute on opportunities he surfaces
• His attack surface (the public internet, community members, potential bad actors) never touches the internal team directly

The metaphor: Barry is the scout. He's out in the world finding opportunities. Jerry is the handler who receives his intel and routes it to the right people.

What the Agents Do (That You Don't Have to)#

Once the sprint week is done:

What Only You Can Do#

This is the actual list. Everything else delegates:

• Major new business bets (pivot Xeet, launch new product)
• Investor conversations and fundraising
• Calls and meetings that require a human
• Approving the first version of any new content template (then auto after)
• Gateway restarts (requires your okay per hard rules)
• Quarterly OKR reset (4 hours, once a quarter)
• Genuine blockers where agents hit a wall

The Memory Preservation Protocol (Soul Engineer Handles — You Approve)#

Before archiving the 11 agents, Soul Engineer will:

1. Read every workspace — MEMORY.md, daily logs, QUEUE.md, SOUL.md
2. Extract what's genuinely valuable: decisions made and why, patterns that worked, lessons learned the hard way
3. Consolidate into shared-knowledge/ so Core Four can access it
4. Archive the workspace (don't delete — rename to workspace-{agent}.archived)
5. Delete noise: todo items that are stale, speculative ideas that didn't pan out, duplicate rules

You review the consolidation summary before anything is deleted. Soul Engineer produces a "what we kept / what we pruned" document for your sign-off.

The Prompt to Give Soul Engineer to Start Everything#

Copy this into Soul Engineer's Telegram DM:

SE — starting the v2 rebuild now. Read SOUL-ENGINEER-BRIEFING.md completely first.

Your mandate for this sprint:

1. IMMEDIATELY: Enable Lacie's morning brief cron (6am EST, Sonnet). I want a message tomorrow.

2. THIS WEEK:
   - Archive 11 non-core agents (preserve memories, prune, consolidate to shared-knowledge)
   - Rewrite Core Four souls via extraction interview (Lacie first, then Gary, Cherry, Jerry, then Barry)
   - Enable heartbeats: Lacie (morning brief), Jerry (2x/day), Cherry (2x/day)
   - Enable compound loops: Jerry (1am), Gary (1:10am), Cherry (1:20am) — soul patches to staging, not auto-apply
   - Wire Cherry to agentmail send primitive
   - Prepare Barry's updated soul (Brand Agent, not just community manager — he does proactive IP/biz outreach)

3. BARRY CORRECTION: Barry runs in a Docker container (not a separate MacBook). He's intentionally off. When his soul is ready, I'll turn him back on. His architecture: externally isolated from internal context, internally connected to Jerry for opportunity routing.

4. PRIMARY BUSINESS: souls.zip. First autonomous action should be: Cherry sends welcome email to new trials automatically.

North star: I wake up to a 5-min morning brief. Revenue, what shipped, 2-3 decisions. Everything else runs without me.

Morning brief format (tight, this exact structure):
---
SOULS.ZIP
• MRR: $X | Trials: N | New paying: N
• What shipped: [bullet list]
• Cherry: N outreach sent. N replies.

BEARISH
• Barry: N posts. Top engagement: "..."
• Barry flagged: [opportunity or nothing]

DECISIONS (by noon or default ships):
1. [Decision] → Rec: X | Default: X
---
That's it. No extra sections. 5 minutes max.

Security: I'm skipping the P0 security items for now. Do NOT pause to do security hardening. Proceed directly to soul rewrites. I will schedule security for Month 2.

When you're ready to apply config changes: send me "Approve gateway restart?" and I'll reply YES.
When memory consolidation is ready: send me the summary for review before deleting anything.

Report back: what have you done, what's next, what needs me. Daily.

Begin.

What Success Looks Like at the End of Sprint Week#

By Friday:

• ✅ Morning brief arriving at 6am daily
• ✅ Cherry sending trial welcome emails automatically
• ✅ 3 heartbeats running (Lacie, Jerry, Cherry)
• ✅ 3 compound loops running (nightly)
• ✅ 11 agent memories preserved + consolidated
• ✅ Core Four souls rewritten (extraction interview done)
• ✅ Barry soul ready (Docker restart whenever you're ready)
• ✅ souls.zip has an autonomous outreach pipeline in progress

By end of month:

• Morning brief includes revenue numbers
• Cherry has closed first autonomous trials to paid
• Barry is back running community + surfacing opportunities
• First compound loop outputs reviewed — agents are getting smarter

The One Thing That Makes Everything Else Work#

The morning brief must be good, or none of this matters.

The morning brief is the contract. It's what makes you an investor instead of an operator. If it's bad — too long, missing the right info, full of noise — you'll stop reading it and start managing again.

Tell Lacie this during sprint week:

"The morning brief is the most important thing you produce. Test it with me daily. Every day I'll tell you what was useful and what wasn't. The brief evolves until it's exactly what I need — then it runs on autopilot."

Make this feedback loop happen in week one. The brief should be perfect within 7 days.

Files to Read (If You Want Context on Any Decision)#

You don't need to read any of these now. They exist for when you have a specific question.

The Real North Star#

You said it: "the organization works and makes money autonomously. I am only requested where a human in the loop is critical — meetings, calls, big decisions, big blockers. Everything else is figured out, and is 95% perfect."

That's the system you're building. Sprint this week. It starts with one message to Soul Engineer.

Send it now.