A Folder-Based AI Operator
Drop identity.md, rules.md, examples.md, and reference/ into a Claude project and Claude becomes the operator: paste a prospect's inquiry, get a routed decision with the work already done.
CLIEF NOTES WEEKLY COMPETITION #7 / THE OPERATOR
MAX MUSCLES handles problem-first health intake and routing for a solo personal trainer. This page shows the decision flow, the rules that drive it, the scoring math, the edge cases, and exactly where to verify each judging criterion.
WHAT IS THIS?
Drop identity.md, rules.md, examples.md, and reference/ into a Claude project and Claude becomes the operator: paste a prospect's inquiry, get a routed decision with the work already done.
This site runs the real thing: the guided intake, safety checks, and route scoring run in the page, and the final 30-day starter plan is generated live by the Claude API under the same operator rules. Every result is written for that prospect on the spot - take the assessment and watch it happen.
THE DECISION FLOW
Every prospect inquiry takes this exact trip. If the first message is incomplete, Max asks the missing intake questions first. The output is always one of three routes.
A raw message, DM, email, or guided assessment chat. Messy input is expected.
Max asks what is wrong right now and why they reached out now, not just what result they want.
Pattern, schedule, sleep, stress, cravings, pain, limitations, and other likely contributors.
Major surgery, heart, kidney, breathing, major limitation, medication, and related red flags.
Problem clarity, safety, readiness, evidence completeness, and plan usefulness.
FLAG or REDIRECT can override SEND. The output is built before the user returns.
Clear main problem, enough evidence, ready, no blocking safety concerns
Medical or functional complexity, or the evidence points to a human review step
Not ready, browsing only, refuses intake, or doctor-first issue outside plan scope
THE Q.U.E.S.T. METHOD
Q
What is the actual problem, and why does it matter now?
U
How the issue shows up in real life, plus schedule, habits, and readiness signals.
E
Probe likely drivers, run the safety screen, and decide what can be built safely.
S
Weighted rubric: problem clarity, safety, readiness, completeness, and plan usefulness.
T
One of three routes, with the output built and the next step drafted.
RULES AT A GLANCE
Every decision criterion in rules.md is executable. These are the hard stops and the cautions.
Route precedence: safety rules override score. Missing safety information also blocks a SEND PLAN route.
SCORING SYSTEM
| Dimension | Weight |
|---|---|
| Problem Clarity | 25% |
| Medical / Functional Safety | 30% |
| Readiness to Follow Through | 20% |
| Evidence Completeness | 15% |
| Plan Fit / Usefulness | 10% |
| Score | Route |
|---|---|
| 85-100 | SEND PLAN - full package if no safety block exists |
| 60-84 | FLAG - review or partial-plan territory |
| 40-59 | FLAG - human approval required |
| 0-39 | REDIRECT - not ready, too incomplete, or doctor-first context |
EDGE CASES
The operator digs until it knows whether the real driver is sleep, stress, cravings, pain, low energy, or structure failure. Example 1
Sleep problems do not get generic advice. Shift-work cases get flagged if the evidence points to complexity. Example 2
Joint pain plus surgery history does not get a hard no or a reckless yes. It gets a safe partial plan and coach review. Example 3
Browsing, shortcut-seeking, or peptide-only curiosity gets redirected instead of converted into fake certainty. Example 5
JUDGING CRITERIA
| Criterion | Where to look |
|---|---|
| Does it actually make decisions? | Three explicit routes with precedence in rules.md - or just take the assessment: the intake routes you, then Claude generates your personalized 30-day plan live under the operator's rules. |
| Are edge cases handled? | Problem-first logic in rules.md plus worked cases in Example 1, Example 2, and Example 3. |
| Trustworthy enough to act on? | Every route ships finished work: full plan, safe partial plan with review notes, or a reason-specific redirect. Safety rules hard-stop risky sends. |
| README quality | README.md - 2 minutes to understand, includes verification steps. |
THE OPERATOR FOLDER
USE IT IN CLAUDE
Grab the repo as a ZIP from GitHub.
In Claude, create a new project named "MAX MUSCLES Operator".
Add identity.md, rules.md, examples.md, and everything in reference/ as project knowledge.
Drop in a real inquiry. Max scores it, routes it, and hands you the finished output.
SEE IT DECIDE
Two minutes. Watch the operator identify the main problem, route you, and build the right starter output.
Start Free Assessment Read the 6 Examples