My mechanic, my Garmin, and the mystery of the racing heartbeat

A mystery in the morning numbers

It started in January. Scattered weekday mornings where my heart rate ran well above its usual, sitting right there in the data my Garmin collects. Not workout mornings. Not big-meeting mornings. I checked my calendar against the dates and found nothing. My doctor took it seriously enough to look and found a heart in good order. Stress, probably, she said, which is a diagnosis shaped like a shrug. The mystery stayed open from January to May: some mornings my heart raced, and I couldn't say which mornings or why.

The other log I was keeping

Those same months, I was living a second, unrelated story: the car. An intermittent shudder under braking at highway speed, the kind of fault that never performs at the shop. Three visits between January and May. Somewhere in visit one I started recording my conversations with my mechanic, because his explanations are precise and I forget them by the parking lot. I asked if he minded me recording. He said go ahead.

So I have him, in his own words, walking me through what a warped rotor does and does not do, what the caliper looked like, what the repair would cost if it was the cheap thing and what it would cost if it wasn't. And I have the instruction he gave me at the end of visit two: next time it does it, note exactly when.

One place instead of two apps

Paredra syncs my health data. My heart rate, the readiness numbers, the activity log, arriving day after day into the same space as my recordings and my notes. The mechanic conversations were already in there, searchable. Which meant that when I finally sat down with the mystery one Sunday, I wasn't juggling apps and exporting spreadsheets. Everything was in one place, and all of it was mine.

I searched for the shudder and got the March conversation back, with his note-exactly-when instruction. Then I put the racing-heart mornings next to my own notes and my calendar, date by date. Every single one was a morning I had taken the highway in that car. The weeks it sat at the shop while I drove a loaner: clean. After the May repair, new rotors, new caliper: not one flagged morning since.

I'd been white-knuckling a brake I didn't trust, twice a day, for five months, and calling it nothing. My body kept a record of it. So did my watch.

My watch knew when. My mechanic knew why. The answer appeared the day both records sat in the same place, and the one who found it was me.

What it does not do

Paredra didn't find this. It doesn't cross-reference heart rate against repair history, doesn't flag patterns, doesn't send an alert suggesting you check your brakes. No interpretation, no diagnosis, no advice: my cardiologist rules on my heart and my mechanic rules on my car. What Paredra did was narrower, and it turned out to be the missing piece. It kept the transcripts and the numbers together, searchable, in a space I own, so that a question spanning both could be answered by one person in one sitting. The noticing was mine to do. For the first time, it was possible to do it.

Health data syncs from Garmin and Oura today. If your numbers live somewhere else, they don't reach Paredra yet.

At the next oil change I told my mechanic the whole story. He thought about it for a second and said: you drove five months on brakes you didn't trust? Get an appointment sooner next time. Noted, and recorded.

I asked my mechanic before recording our conversations, and you should too. Check the recording rules where you live. Paredra is not a medical device and gives no medical advice: it keeps your numbers and your notes together, and the interpreting stays with your doctor. Your recordings and your health data stay in your own space, and we never train models on your content.