🏆 WEEKLY COMP #4: THE AGENCY 🏆

💰 $325 CASH 💰

That's a full year of Premium. Win this and your membership pays for itself.

But the real prize this week isn't the cash. Keep reading.

📋 THE CHALLENGE

You just got hired again. Meet Diana, owner of a 4-person boutique real estate team in Austin. 60-80 transactions a year, mostly residential, mix of buyers and sellers.

📎 Download the full client brief attached to this post.

Short version: She doesn't want software. She wants a system she can teach her team to use in a week.

Your job is to build the AI operating system for her team. This isn't one specialist. This is a small team of AI specialists organized into a multi-folder ICM architecture, with a clear handoff protocol between them.

🗂️ WHAT YOU'RE BUILDING

Last week was one specialist. This week is a team of them.

Required folders:

📍 00_orchestrator/ — The router. Where every request starts. Decides which specialist gets the job.

📍 01_lead_qualifier/ — First contact with new prospects. Captures intent, budget, timeline.

📍 02_property_research/ — Deep research on specific properties or neighborhoods.

📍 03_client_communication/ — Drafts emails, texts, follow-ups in the voice of the agent.

📍 04_transaction_coordinator/ — Handles the deal once it's live. Checklists, deadlines, document tracking.

Each folder must include:

📄 identity.md
📐 rules.md
💬 examples.md
🔗 handoff.md (NEW for Week 4 — how does this folder pass work to another folder?)

Plus a root-level README.md explaining the architecture, the typical flow, and how to onboard a new team member.

🔥 WHY THIS ONE IS DIFFERENT

Weeks 1, 2, and 3 were warmups. This is the comp where the work you ship genuinely starts to look like the real thing.

The handoff protocol is the test. Anyone can build five folders. The hard part is defining what each one needs from the previous one and what it passes to the next one. That's where multi-agent systems actually live or die.

💼 THE REAL PRIZE

The cash is nice. The portfolio piece is the real win.

This comp is your introduction to interpretable context methodology. You'll ship a starter version of a multi-folder system. Real architecture, real handoffs, real folders you can clone and show off.

This is the surface layer. The Lyceum is where you go deep. Twelve weeks of building production-grade ICM systems with Jake walking you through the parts this comp can't teach in six days: orchestration patterns, context evaluation, edge cases, what to do when the system breaks, how to scale it from one team to a hundred.

Think of this week as the on-ramp. You're getting hands on the methodology so you know whether you want to keep going. 🚀

📝 HOW TO SUBMIT

Public GitHub repo required this week. The folder structure is the deliverable.

Drop your repo link in the comments along with a 100-word writeup covering:

🛠️ What you built
🎨 One design decision you made and why
➕ One thing you'd add if you had another week

🆕 Didn't set up GitHub for Week 3? This is the week. Drive folders will be accepted but GitHub will score higher because it's how this work actually gets shared in the real world.

⚖️ JUDGING

Jake, Myself, and the mods. Four things we're looking at:

✅ Does the architecture make sense? Could someone hand this to a real estate team and have them use it?

✅ Are the handoff protocols actually defined or are they hand-waved?

✅ Is the README good enough to onboard a stranger

✅ Did you make real design decisions or did you just fill out the template?

🎟️ WHO CAN ENTER

Premium and VIP members only. No exceptions.

🆓 Free members watching? Upgrade and you're in. One year of Premium is $325. The prize is $325.

The math works in your favor on Week 1 of being a paying member.

📅 DATES

⏰ Submit by: Sunday, May 17th, 12:00 PM EST