A breaker that protects the wire, and a device that protects you

A circuit breaker is a bouncer for the conductor. It watches for too much current — a 20-amp breaker lets go somewhere past 20 amps of sustained load, because that is the point where the wire behind the wall starts to cook. It is doing exactly its job, and that job has almost nothing to do with the person holding the drill.

Here is the uncomfortable arithmetic. It takes roughly 15 to 20 amps to trip that breaker. It takes a fraction of one amp across the chest to stop a human heart. A current small enough to be a rounding error to the breaker is more than enough to kill you. The breaker will never notice. That gap — between what damages copper and what damages a body — is the entire reason the ground-fault circuit interrupter exists.

So the GFCI is not a smaller, more sensitive breaker. It is measuring something completely different.

The trick: current that goes out must come back

In a healthy circuit, every electron that leaves on the hot conductor returns on the neutral. The two currents are equal and opposite at every instant. Send 8 amps out the hot, and 8 amps come back on the neutral. Always. That balance is not a coincidence; it is conservation of charge. Current has nowhere else to go.

Unless it does.

If a frayed cord, a wet connection, or a hand bridges the hot conductor to something grounded — a pipe, a wet floor, a metal enclosure — then a little of the outgoing current peels off and takes that path to earth instead of returning on the neutral. Now the books don't balance. Maybe 8 amps go out and only 7.995 come back. The missing five-thousandths of an amp didn't vanish. It went through whatever was touching ground. Possibly a person.

A GFCI is built to catch exactly that mismatch.

What's actually inside the device

Both the hot and the neutral conductor pass together through a small ring — a current transformer, essentially a donut of iron with a sensing coil wound around it. When the current in the two conductors is equal and opposite, their magnetic fields cancel inside that ring. The sensing coil sees nothing. Silence.

The moment current starts leaking to ground, the two no longer cancel. A net magnetic field appears in the ring, proportional to the difference between hot and neutral — the part that isn't coming back. That difference induces a tiny voltage in the sensing coil. A small solid-state circuit amplifies it, compares it to a threshold, and if it's over the line, it fires a solenoid that snaps the contacts open.

Notice what the device never measures: how much current is flowing. You can run a 1,500-watt heater through a GFCI all day and it stays closed, because 12-plus amps out and 12-plus amps back still balance perfectly. The GFCI is indifferent to load. It only cares about the imbalance. That is also why a GFCI does not need a ground wire to do its job — it isn't sensing the ground connection, it's sensing the absence of returning current. This is why GFCIs are the code-sanctioned way to protect older two-wire receptacles that have no equipment ground at all.

Why the number is 5 milliamps

The threshold isn't arbitrary, and it isn't an electrical engineering convenience. It's a biology number wearing an electrical costume.

Research on the human body's response to current runs roughly like this. A current of about 1 milliamp is the threshold of perception — you feel a tingle. Somewhere around 10 to 20 milliamps you reach the let-go threshold: the current causes your forearm muscles to clamp involuntarily, and you can no longer release your grip on the thing shocking you. Above that, sustained current through the torso can drive the heart into ventricular fibrillation, where the muscle quivers instead of pumping. The exact figures vary with the person, the path, the duration, and whether the skin is wet — never trust a single tidy number here — but the shape of the curve is well established and frightening.

The people who wrote the safety standard placed the trip point below the let-go threshold. A North American Class A GFCI, under UL 943, must trip when the leakage reaches somewhere between 4 and 6 milliamps — call it 5. The logic is brutal and clear: catch the fault while you can still let go, before your muscles lock you onto the wire. And the device doesn't just trip eventually; the standard defines an inverse-time curve, so larger faults trip faster — a serious leak opens the circuit in a small fraction of a second, well before the current has time to do its worst.

That is the whole design philosophy in one sentence. The GFCI is tuned not to protect the circuit, but to interrupt the fault in the narrow window between you can feel it and you cannot get free.

Why it trips when 'nothing is wrong'

Understanding the mechanism explains the most common field complaint: the GFCI that trips with nothing obviously faulted. Because the device is reading a five-milliamp difference, it is exquisitely sensitive, and the real world leaks.

Long cable runs have capacitance between conductors; some current sneaks across that capacitance and never makes it back on the neutral. Motors and electronic power supplies have small designed leakage to ground through their filters. Moisture in an outdoor box, a slightly wet connector, insulation that has aged — each contributes a few stray milliamps. Stack several of these on one protected circuit and the normal leakage can creep toward the trip threshold all on its own. Add a refrigerator's startup or a damp morning and it crosses the line. The device is not malfunctioning. It is doing precisely what it was built to do: refusing to ignore current that isn't coming home.

That's also why one weak GFCI breaker feeding a long string of outdoor receptacles is a recipe for nuisance trips, and why splitting the load or moving to dead-front receptacles closer to each location so often cures it. The fix follows directly from the mechanism — reduce the accumulated leakage the sensor has to live with.

What this changes about how you work

Knowing what the GFCI actually senses changes your troubleshooting from guessing to reasoning. A tripping GFCI is telling you, specifically, that current is escaping to ground somewhere on the load side. That's a real diagnosis, not a faulty device. You go looking for the leak — a pinched cable, a wet junction, a failing appliance — instead of swapping the GFCI and hoping. And you stop expecting the device to do things it was never built for: it won't protect the wire from overload, and it won't care how much power you draw, because neither of those is the question it asks.

The deeper point is that almost every protective device on a job site is answering a different question. The breaker asks is the conductor overheating? The GFCI asks is current returning the way it left? An AFCI listens for the high-frequency signature of an arc. Confuse the questions and you'll size, place, and troubleshoot the wrong way — and you'll blame good hardware for honest work.

Where Voltly fits

Voltly is built for the moment you're standing at the panel turning the mechanism over in your head — running an ampacity check, a voltage-drop number on a long GFCI-protected run, a box fill, a conduit bend — all offline, all from NEC tables, no signal required. It won't find the leak in the wall for you. But when the reasoning matters more than the rote answer, having the calculations and the code reference in your pocket means you can spend your attention on the part only a person can do: figuring out where the current is going. If that's the way you'd rather work, voltly.lumenlabs.works is where to start.