ProbeLem

Do not touch what you cannot see. ⚡

In electrical work... the most dangerous thing leaves no trace.

Voltage has no face.

You cannot smell 440V.

You cannot hear a backfeed waiting behind an open contact.

A conductor can look dead. A panel can look silent.

But silent is not the same as safe.

The multimeter is not just a tool. It is the safety barrier between assumption and injury.

Full article including the one layer most ETOs overlook is live on Patreon.

👉 patreon.com/ProbeLem

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!

ProbeGnosis: The Knowledge You Can Only Earn

Some electrical knowledge is taught in school.

Some is written in manuals.

But some knowledge can only be earned...

inside the engine room,
in front of a live panel,
with a fault you have never seen before,
and a multimeter in your hand.

That is what I call ProbeGnosis.

Probe... to investigate, to test, to push the prod of the multimeter into the problem.

Gnosis... direct, experiential knowledge. Not secondhand. Not theoretical. The kind you only gain by doing.

For me, ProbeGnosis is the deep layer of ProbeLem.

It is how I turn real shipboard troubleshooting experience into principles that can be remembered, taught, and reused.

ProbeLem is the combination of my procedure and my personality. That is how my brain works. I learn from real faults, real measurements, and real consequences... then I coin words so the lesson can be remembered, taught, and reused.

That is how I know.

That is how I teach.

Like the Space-Time Jutsu... when I came onboard for the first time and found a nuisance MCCB tripping issue the crew had been dealing with for over a year since the previous installation. The root cause was hiding in plain sight: a UVT coil impedance mismatch.

The case file became the lesson.

The lesson became the product.

That is the vision of ProbeLem:
to build the electrical troubleshooting body of knowledge I wish existed when I was starting out.

Not just content.

Field-earned clarity.

When I think through any electrical problem, I run a three-step mental checklist:

Identify. Probe. Correct / Steer / Iterate.

I call it the Probing Loop.

It's not a framework I read somewhere. It's a pattern I noticed in my own process after hundreds of real troubleshooting events.

I named it so I could teach it.

I teach it so others don't have to rediscover it from scratch.

That's ProbeGnosis in action.

Keep on probing!

— Lem

NB. The long read is in the comments if you want to go deeper.

You learned DRAWING vs SCHEMATIC in Episode 1.

Now Episode 2 hits harder. 🔥

Wiring Diagrams. Single Line Diagrams. Layout Diagrams.

3 document types. 3 different purposes.
Grab the wrong one during a fault?
You're already behind.

Episode 2 of ProbeCourse is now on YouTube —
exclusive for Probe Master members. 🔒

👇 Watch it here:
https://youtu.be/xNIQU4_mJvg

How to Solve Any Problems

The Probing Loop vs. The Doom Loop

I'm a traveling Fleet ETO... and I'm documenting the real-world electrical knowledge I wish existed when I was starting out.

I simplified Karl Popper's 5-step scientific method into something I can loop in my head under pressure. Identify (the Problem) > Probe (Investigate) > Correct/Steer.

The Probing Loop:
1. Identify the Problem - not the symptom. The actual problem.
2. Probe - Logic test first (paper), then Reality test (experiment).
3. Correct/Steer - compare outcome to desired result. Adjust and loop again.

The opposite is the Doom Loop:
Assume, Swap, Force, Blame, Repeat. It feels like action. It converges on nothing.

The Doom Loop consumes. The Probing Loop converges.

Which loop are you running?

Full article with the field proof below
👇👇👇

The internet dropped one evening in August 2021.

The Captain called me. Two access points down. No crew Wi-Fi. No calls home.

I spent days tracing cables, testing ports, swapping hardware... and eventually landed on this: the Wireless Access Points (WAPs) and Wireless LAN Controller (WLC) had rolled back to factory default. Root cause? Unknown. It just did.

IT was informed. And then... silence.
Three weeks later, we got an email. "Sorry for the delay."

But here's the thing; the crew never lost internet for three weeks. Because three days after the failure, I had it back online. Using a decommissioned AP from storage, a console cable I fabricated by hand from spare parts, and CLI commands I had studied months earlier just out of curiosity.

One Sunday within the workaround period, the crew watched Manny Pacquiao's boxing match live on the Dayroom TV.
One crew member later suggested we keep my workaround permanently. He said it felt faster than the original setup.
I had to explain it wasn't sanctioned. But I kept the remark in my mind.

I'm a traveling Fleet ETO... and I'm documenting the real-world electrical knowledge I wish existed when I was starting out.

This is ProbeBack: archival cases from before ProbeLem existed. Documented the way an ETO documents things... for the job record, not for an audience. Publishing it now as part of the archive.
Full case is on Patreon for members. The problem, the probing process, the workaround, the fix, and the lessons I pull from it four years later.

👉 https://www.patreon.com/posts/when-wi-fi-died-154032529?utm_medium=clipboard_copy&utm_source=copyLink&utm_campaign=postshare_creator&utm_content=join_link

Keep on Probing! 🔍💪