Why we tore down Kalivar and built it again

The first version of Kalivar shipped on Laravel because Laravel was what we knew. The platform did what platforms do when they keep shipping: features stacked, edge cases became special cases, and the rule that justified the platform's existence (the anonymization contract between attorneys publishing cases and physicians reviewing them) lived in a dozen guards scattered across controllers, jobs, and email templates. It worked. It worked the way an old house works when every owner adds a wing and a porch and assumes the wiring will be fine.

Today, Kalivar runs on a platform we rebuilt from scratch.

The rebuild is not a UI refresh. We kept what worked: the workflow physicians use to write an opinion, the moment an attorney decides whether to pay for an introduction, the contract that says contact details stay sealed until that payment clears. We replaced the parts that made the contract hard to defend.

The contract, enforced structurally

In the original Kalivar, "anonymized" was a description of what the application was supposed to do. In the new Kalivar, it is a constraint the schema knows about. Every case narrative submitted by an attorney passes through a PHI detection layer before publication. Anything that resembles a patient identifier (name, MRN, hospital reference, an unredacted face on an imaging file) surfaces a revision prompt before the case reaches any expert. The detection layer is a safety net under the attorney's professional obligation, not a replacement for it. The obligation has not changed.

Every physician now has a stable anonymous handle drawn from a physician-themed word pool of 30 adjectives and 50 Greek-style nouns: Astute-Aristion-4123, Methodical-Eudemos-8821, 1,500 combinations before the four-digit suffix. The handle replaces the physician's name in every attorney-facing surface until an introduction is paid for. The old platform showed nothing at all in that slot, which meant an attorney had no way to recognize prior work from the same expert without paying for an introduction first. That was a tax on familiarity, not on access.

Once the introduction is paid for, contact is released. Same contract as before. The handle is the change.

Matching, against the taxonomy hospitals already use

The first Kalivar had its own list of medical sub-specialties: an internal, ad-hoc taxonomy that grew by request. The new Kalivar uses the 140-row NUCC sub-specialty list, the one hospital credentialing systems and federal programs work from. Cases get matched against the same vocabulary used to credential the experts being matched. Borderline matches fall, and the matches that do come through are tighter.

Follow-on introductions are free, retroactively

This is the unannounced subsidy in the rebuild. Once an attorney has paid for an introduction with an expert, every subsequent case-link with that same expert costs nothing. We applied the rule retroactively to every introduction that was ever paid for on the original Kalivar. An attorney who paid for an introduction a year ago and held on to that expert's contact since then can now bring every new case to that expert through the platform at no fee.

The reason: the introduction fee is a fee for trust formation. Once trust exists, charging for the connection is a tax on the relationship the platform was supposed to make possible.

What carried over

Every account, every case, every opinion, every introduction. Fee schedules, expertise areas, and practice addresses preserved verbatim. Sub-specialties were fuzzy-matched into the NUCC list; anything that did not map cleanly is missing from a physician's profile and needs to be re-selected on first sign-in, which takes five to ten minutes. Witness experience, residency, and fellowship were preserved as free text, with optional structured fields physicians can fill in for better display.

What did not carry over: the original passwords. The new platform uses a stronger hashing scheme than the Laravel default, and we won't compromise on it. Every existing user is asked to reset their password once, with a unique link sent to the email on file.

What we're not claiming

This rebuild does not make legal-medical expert exchange easy. It does not eliminate the judgment a physician applies when reading a case, or the judgment an attorney applies when deciding to publish one. It does not relieve the attorney of the obligation to anonymize before submission. The redaction layer is a safety net under that obligation, not a delegation of it.

What it does: make the anonymization contract a thing the schema knows about. Make the expert pool searchable through the same vocabulary the experts are credentialed in. Make the price of trust honest by charging once for the connection and making subsequent links free. Make the welcome email, the dashboard, and every URL in between feel like one product designed by one team rather than years of accumulated patches.

If you've used Kalivar before, your account, your work, and your history are all there. If you haven't, the new platform is here. The contract, as ever, holds.

— The Kalivar team