kolm / case studies
Composite cases drawn from design-partner work. Names of the operators are withheld; the artifacts, K-scores, receipts, and measured throughput numbers are real and reproducible.
Replaced a cloud API redactor on a HIPAA-covered workload. The .kolm runs on the plan's existing call-center boxes, never leaves the network, and the receipts go straight into their model-risk binder.
A bank's small-claims router was already in production. They needed a model-risk artifact the OCC examiner could replay. kolm receipts became the evidence trail; the model logic did not change.
An AmLaw 200 firm's procurement team blocked the original SaaS deployment over the cloud-egress clause. The same model, compiled and signed as a .kolm, runs on their hardware and survives both procurement and IT-security review.
Every case study answers the same three questions: was the model good enough (K-score, accuracy, leak rate); did anything leave the environment (egress, third-party calls, telemetry); did the audit trail replay months later. If we cannot publish a number, we say so.
We do not publish customer names. We do publish the artifact CID, the receipt sample, and the harness output, so the engineering details of every case are independently verifiable against the public registry.