The same alarm came back. The failure had changed.
A radar case where a returning alarm required a new evidence trail, not a repeat of the previous repair.
Read the case study
ProbeLemEvidence before assumptions
Marine electrical troubleshooting, documented from the field.
I am Lem, a traveling Fleet ETO. ProbeLem follows the real work of finding electrical faults at sea, understanding what caused them, and proving the equipment is ready to return to service.
Documentary fieldwork, case studies, and practical tools for the people who keep equipment running.
FIELD LOGDOCUMENTED
WORKFLOWSYMPTOM → TRACE → PROOF
CONTEXTFIELD
STATUSEVIDENCE-LED
The field library
Choose how you want to follow the work.
Every channel serves a different depth, while the evidence and the first-person field perspective stay consistent.
Watch
Field troubleshooting docu-vlogs
Follow real electrical work at sea, from the first symptom to the evidence that closes the fault.
Open YouTube ReadCase studies and ProbeNotes
Read the reasoning behind the work, including the measurements, false leads, and final proof.
Open Substack Go deeperMember field library
Access extended cases, learning resources, and the Probe Enthusiast community.
Open PatreonFeatured fieldwork
Start with a real case and follow the evidence.
These links lead to the original publications. Public case studies stay open, while member-only depth remains clearly marked.
Two alarms, one boiler, and a spare that needed proof.
The public opening explains why physical fit was not enough. The complete field record continues for members.
Open the member caseNoise, signal, and focus.
A field reflection on what a manual note about shielding can teach us about protecting the signal that matters.
Read the field reflectionThe ProbeLem method
A reading becomes useful when it is connected to context.
The goal is not to make every measurement pass or fail. The goal is to preserve the evidence, apply the right source, and make the next decision defensible.
Explore ProbeLem SkillVault v1Observe the symptom
Start with what the equipment is actually doing, not what the fault is assumed to be.
Trace the evidence
Follow the circuit, compare readings, and keep every conclusion tied to a source.
Prove the recovery
Verify the operating outcome before calling the job complete.