The ikigAI
feedback loop
Run · Catch · Lock
Three verbs. One operating cycle. The thing every module in this program teaches you to run on your own Claude Code infrastructure. Most people stop at "Run." Some get to "Catch." Almost no one closes the loop with "Lock." That's the gap this program closes.
Run
Execute. Put it in the world. Build the email, draft the SMS, write the report. Don't theorise. The loop never starts until something real is in motion. This is where most people are already doing fine — they do the work. The problem comes after.
Catch
Friction surfaced. Something compounded. The AI gave you the same off-brand draft for the third time. You noticed. Most people feel the moment and let it pass — they think it's a one-off. It isn't. The third occurrence is data. The catch is the discipline of recognising a pattern in real time, not three months later when you finally lose patience.
Lock
Turn the pattern into a binding rule with a date, a why, and a trigger. Save it where your Claude Code session will see it next time. The friction becomes operating logic. The lesson stops being your problem and starts being the system's job. Future-you doesn't relive the breakdown — the rule fires before it happens.
The ikigAI methodology is the foundation of Mario's coaching work — it's how he helps founders find the work they're built for. At its heart, ikigAI is a feedback loop: live, notice what energises you, encode it into the shape of your business.
The same loop, pointed at Claude Code infrastructure, becomes Run · Catch · Lock. Same shape, different domain. You're not learning a new framework — you're applying a framework you already know to a tool you already use. That's why it compounds so fast.