The same boundary discipline, in six settings.

Banking & financial services

KYC and KYB case workflows, fraud triage and exposure views run where account and transaction data lives. Reviewers see ranked flags with reasons, and compliance can show examiners the ledger. Card numbers stay masked in the plan itself.

K·01 + K·03 · agent beside core banking stores→

Healthcare

Operational analytics over admissions and staffing while patient records stay in the hospital's environment. Aggregation floors suppress results below a minimum cohort size, and locality plus access logs are designed to support HIPAA and DPDP obligations.

K·02 + K·03 · agent inside the hospital environment→

Manufacturing

Anomaly models run beside the sensor stores at the plant's data layer. The agent initiates every connection and needs no inbound ports; its egress stays under your firewall rules, and air-gapped patterns are a design target.

K·02 + K·03 · agent beside the plant historian→

Retail & supply chain

Demand and inventory forecasts computed beside the systems that hold them. Suppliers and logistics partners collaborate on governed views inside your boundary; your records have no path out.

K·01 + K·03 · partners read governed views in-boundary→

SaaS providers

Serve analytics to customers who keep data in their own environments; the agent runs there. You ship intelligence without taking custody of tenant records, and each tenant reads its own ledger.

K·02 + K·03 · agent in each tenant environment→

Public sector

Raw records that must stay in their jurisdiction stay there, and the agent runs in-jurisdiction. Locality, lineage and access logs are properties of the run itself, which is what a residency review wants to see.

K·02 + K·03 · agent deployed in-jurisdiction→