Nine workflow shapes where the math swings hardest: any task that’s 80%+ deterministic, has data you can’t leak, runs on a budget, and needs an audit trail. Pick a shape closest to yours and read what kolm changes about it.
Each page links to a worked example, the verifier shape, the receipt format, and the eval set we used to gate the K-score. Industry pages (healthcare / finance / defense) cover regulated buyer concerns; use-case pages cover the engineering shape.
A signed .kolm artifact your coding agent (Cursor, Claude Code, Cline, Aider) calls between turns over MCP. K-score gated at compile, runtime egress = 0, deterministic.
The 90%-deterministic features paying frontier prices. Compile each one once; pay for it once; ship the artifact in your own infra.
Hermes-class behavior on a phone shipped since 2021. Offline, sub-100ms, no per-token bill, signed receipts.
Jetson, Coral, NPUs, IL5 devices. Air-gapped, signed-firmware-style updates, 50MB-3GB artifacts, deterministic latency.
HMAC-chained receipts anchor to Sigstore / Rekor, optionally Arweave / OP_RETURN. Outputs you can prove came from a specific artifact.
Drop-in proxy for OpenAI / Anthropic. Captures verified (input, output) pairs. Compiles to a signed local LoRA at threshold. The frontier bill pays for the artifact.
Triage, intake, coding, summary, without PHI leaving the boundary. BAA path, on-prem inference, evidence chain.
SR 11-7, BSA/AML triage, document review. Signed audit log, reproducible evaluator, model risk management evidence.
Air-gap, FedRAMP path, IL5 considerations, classified intake. The artifact runs where your network ends.