🏆 WEEKLY COMP #7: THE OPERATOR 🏆

Matthew Creamer

6h • 💰 Competitions

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️

Pick your cohort. Technical, Business, or Creator. Your call.

----

🇬🇧 We're back.

Good morning from London. 👋

Thanks for the patience last week. Jake and I needed a few days to breathe before London Tech Week kicked off, and you all responded with nothing but support. We don't take that for granted.

Now let's get back to building.

----

📋 THE CHALLENGE

Build a folder-based AI operator that handles ONE operational workflow end-to-end. You pick the workflow.

This week's deliverable is one operator folder that someone could drop into a Claude project and use to handle a real business workflow without babysitting.

----

🎯 PICK YOUR WORKFLOW

The workflow is yours. Pick something specific. Pick something you'd actually use.

A few sparks to get you thinking:

🎫 Customer support triage (which tier handles this ticket?)
✅ Content review and approval
📨 Lead intake and qualification
💸 Refund request handler
🤝 Partnership pitch evaluator
🎙️ Podcast guest pitch sorter
💼 Freelance project intake
📄 Resume screen for one specific role
📅 Meeting request triage (book, decline, delegate)

The more specific, the better. "Customer support" is too broad. "Refund request triage for an ecommerce store doing under 200 orders per month" is right.

📎 If you want a fully written client brief as a reference, the attached PDF walks through one example.

Don't build the example. Use it as a template for how to think about scoping your own operator.

----

🗂️ THE METHODOLOGY

If this is your first comp, welcome. Here's what you need to know:

This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well.

Your operator is a folder with five things:

📄 identity.md (who the operator is and what workflow they own)
📐 rules.md (the decision logic: criteria, edge cases, escalation rules)
💬 examples.md (decisions in action, including at least one edge case)
📚 reference/ (checklists, templates, rubrics)
📖 README.md (how to use it)

Drop the folder into a Claude project. Claude becomes the operator. Reusable. Shareable. Portable.

----

🔥 THE ANGLE THIS WEEK

An operator is NOT a chatbot.

A chatbot responds. An operator makes a decision, then routes the work.

When the operator gets an input, it shouldn't ask the user what to do. It should decide and act. The user comes back to find the work already done, or correctly flagged for their input.

That distinction is the whole assignment this week. Your rules.md is where you encode the decision logic. "Use good judgment" is not a rule. "If years of experience is under 3, decline unless they've shipped a notable open source project" is.

----

💼 WHY THIS LANDS ON YOUR RESUME

"I built a folder-based AI operator that handles [workflow] end-to-end" is the kind of work companies actually pay for.

The skill you're learning this week is writing decision logic into rules. That's the foundation of automation, and it's a skill that translates directly into ops roles, automation engineering, and AI product work. 🚀

Win or lose, you walk out with something you'd be proud to link from your LinkedIn.

----

📐 THE BAR

Someone with no context should use your folder, feed it three real examples, and trust the output enough to act on it.

If the operator kicks the decision back to the user every time, you've missed the assignment.

----

📝 HOW TO SUBMIT

Drop a public GitHub repo link in the comments. Plus 2-3 sentences on what workflow your operator handles and what kind of decisions it makes.

----

⚖️ JUDGING

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

✅ Does the operator actually make decisions? Or does it kick the question back?

✅ Are the edge cases handled or hand-waved?

✅ Would the output be trustworthy enough to act on?

✅ README quality. Can a stranger figure this out?

----

🎟️ WHO CAN ENTER

Premium and VIP members only. No exceptions.

🆓 Free members watching this thinking "I could win that"? You're probably right. This week's prize is a free Lyceum seat. That's the same program biz owners pay full price to access. Upgrade to Premium and you're in the running.

----

📅 DATES

⏰ Submit by: Saturday, June 13th, 12:00 PM EST

🎉 Winner announced: Monday, June 15th

----

🚀 One last thing.

Week 5 was The Coach. Week 6 was The Researcher. This week is The Operator. Different skill, same methodology.

By the end of next week, anyone who's entered the full Month 2 arc walks out with a portfolio of variety. Coach. Researcher. Operator. Wildcard. Four different specialists. Four different portfolio pieces.

This week the stakes are bigger. The winner gets a free seat in The Lyceum, where Jake walks you through the deep work this comp can't teach in six days.

LFG 🚀

5 comments