For banks, payments processors, broker-dealers, and capital markets. Compile bridge runs inside the customer VPC, primary account data never leaves the cardholder zone, every model run produces a receipt the model-risk team can hand to internal audit.
Artifact SHA, K-score, run timestamps. No PAN, no SSN, no AML pattern hits. Receipts are payload-free.
FIPS 140-3 module in the CDE. Bridge reads, redacts, distills. The bridge cannot make outbound calls except receipt heartbeat.
Every model run signs into a chain. Inputs: artifact + K + verifier results. Internal audit re-checks offline with kolm inspect.
| Standard | What it requires | How kolm meets it |
|---|---|---|
| SR 11-7 (Fed) · OCC 2011-12 | Model inventory, conceptual soundness, ongoing monitoring, outcome analysis | Model card per .kolm + held-out eval suite + signed K-score + receipt chain for outcomes |
| PCI DSS 4.0 Req 3, 4 | Protect stored account data + cryptography in transit | PAN never leaves CDE. Bridge runs inside. CMK encrypts seeds at rest. |
| PCI DSS 4.0 Req 10 | Log + retain auditable record of access | HMAC receipt chain, 90-day default retention, exportable via /v1/account/compliance-package |
| SOX ICFR (Section 404) | Reasonable assurance over financial controls that use models | Same-bytes kolm inspect path means auditors don't trust kolm.ai — they trust the chain on the machine they brought. |
| NIST AI RMF (Govern, Map, Measure, Manage) | Documented risk tiering and evidence per system | K-score as a measurable; gate is the manage function; receipts are the evidence; /compliance/nist-ai-rmf |
| EU AI Act (high-risk) | Technical documentation + post-market monitoring | Spec · manifest · receipts — mapped in /compliance |
kyc-classifier.kolm at K≥0.92 with stable PAN/SSN placeholders. kolm inspect on their laptop re-checks every run from the last 90 days. No call to kolm.ai required.| What if… | What happens |
|---|---|
| Bridge attempts to exfiltrate a PAN | Egress harness drops it, ring-3 records bytes-out > 0, the run refuses to sign — flagged on the SLA dashboard. |
| Model drift between revisions | K-score recomputes at compile; a drop below gate refuses the artifact. Internal audit sees the K-score series in the compliance package. |
| Insider swaps the artifact | Receipt artifact SHA no longer matches bytes. kolm inspect fails closed (exit 5 CHECKSUM_FAIL). |
| Regulator asks for a model card | Compliance package contains: manifest, recipes, eval pass-rate, K decomposition, last 90 days of run-record hashes. |
| Vendor (us) is compromised | Receipts already signed with the customer CMK. We hold no signing key. A breach at kolm.ai cannot tamper with the chain. |
Onboarding docs → risk tier + missing-field flags. PAN/SSN auto-redacted.
Suspicious transaction → structured rationale + regulator-friendly narrative.
Diff against prior period, flag boilerplate vs material change for the disclosure committee.