Who built this

The one section that isn't impersonal.

Everywhere else, kerkit speaks for itself — no "I," no "we." This section breaks that pattern on purpose. After the structural argument, a single first-person voice is what makes the claims land as more than good copy.

I built kerkit because I was the one tracking a chemotherapy treatment inside Argentina's obra social system — checking which authorization had expired, which prescription needed renewing, which of a dozen emails from the insurer I couldn't afford to miss. I wasn't trying to build an SDK. I was trying to keep up. The domain model, the privacy architecture, the authorization logic here didn't come from a whiteboard. They came from doing this badly with the wrong tools first, and then building the tools the job actually needed.

I maintain kerkit alone right now. I'm saying that directly, not as an apology — it's why issue responses won't always be fast, and it's exactly why I built the project so it doesn't depend on that: locale packs live apart from the core, and well-scoped contributions don't need to wait on me first. If you're building something like this, I'd rather you start from what I've already proven than wait for permission.

And, most importantly, if you're building something that takes care of caretakers, reach out. I want to help.