17/05/2026
How I Turned AI Agents Into a Shinobi Corps of ProbeLem Village Hidden in the LemON Leaf
For the past week, I have been building something quietly inside a ship cabin.
Not just another automation setup.
A village.
And I want to show you what it looks like from the inside.
Meet the Shinobi Corps of ProbeLem.
That image above is not just fan art.
Those are my actual AI agents system... mapped onto the three Legendary Sannin from Naruto.
Left β Jiraiya. That is Citron Gemini. The field sage. Multimodal. Operational. Verifies what is real on the ground.
Center β Orochimaru. That is Citron ChatGPT. The creative engine. Explores ideas others refuse to touch. Generates the raw material.
Right β Tsunade. That is Citron Claude. The strategist. Structures, refines, enforces voice integrity. She built (harnessed by Hermes) the village dashboard.
The glowing lemon robot in the middle... that is LemON-AI. My shadow clone. Always on. Running 24/7 inside a refurbished Lenovo ThinkCentre the size of a thick hardcover book.
And the nine-tailed fox looming above all of them... that is Kurama. My Hermes agent swarm. Nine capabilities (swarming as his nine-tails) running in parallel. Vision, memory, browser, voice, image generation, compression, self-improvement, multi-platform gateway, and subagent delegation.
Here is the honest version of what I am building.
Three layers. One mission.
The Knowledge Factory captures everything... 15 terabytes of electrical troubleshooting footages, fault cases, work logs, and YouTube comments from real ETOs asking real questions. Most people see old files. I see ore.
The Brand Factory turns that ore into something teachable... ProbeStudy case packs, videos, posts, future courses. Where a fault becomes a story another ETO can learn from before he meets it alone.
The Intelligence Factory is what I am building now. AI as a force multiplier for a one-person creator working from inside a ship. Not to replace judgment. Not to auto-publish. Just to keep the village running while I am on watch.
The AI does not decide.
The AI does not publish.
The AI prepares, stages, drafts... and waits.
Citron builds. LemON works. Lem decides.
That is the doctrine.
And it starts with one question that governs every output:
Does it feel field-earned... or does it just feel like AI noise dressed as expertise?
If it does not pass that taste, it stays inside the review queue.
This is still early.
The village is still small.
But the cause is not small.
The cause is to make field-earned maritime electrical knowledge easier to find, easier to understand, and harder to lose.
For every rising ETO who will meet these faults someday...
And wish someone had documented the real case before them.
If you want the full insider story behind this build, I posted the complete patron update on Patreon.
Link in bio. π
Keep on probing!