Auria.
Career infrastructure for caregivers.
I work as a caregiver on the Seattle Eastside. The best CNAs I know carry entire client relationships — families ask for them by name — and still get treated as interchangeable. Auria makes the caregiver the customer: a verified record they own, a ladder they can see, and matching that explains itself.
The Problem
Home care runs on caregivers whose track records live in someone else's filing cabinet. Years of verified work and specialty hours don't transfer, don't compound, and don't price the next hour of their labor. Auria is the alternative I'm validating: an event-sourced career record the caregiver owns, a published wage ladder, and matching that explains itself. It's a demo — it arranges no care yet, and every page says so.
A Record That Computes Itself
Every visit is an event in an append-only log — the VisitEvent table is the single source of truth. Verified hours, specialty hours, attendance, and tenure are computed on every read; no stored totals column exists anywhere. Even a missed shift is an event: scheduled, zero minutes, tagged missed.
Matching That Shows Its Work
Rule-based, no ML. Hard filters emit plain-English exclusion reasons, then a 100-point weighted score whose per-component sentences render verbatim in the family's why-card. Families see at most five curated matches — there is no browse-all feed of caregivers to scroll through like inventory.
Discrimination Has No Code Path
Three layers deep: the schema has no protected-class columns, zod enums reject anything outside the canonical option lists, and scoring can only read stored fields. A preference that shouldn't exist can't be stored, can't be typed, and can't be scored.