Cross-Industry Workflows
How AI agents interoperate across industries using shared domain schemas.
The Three-Agent Walkthrough
Consider a real-world pipeline: Hospital → Insurer → Payment Gateway. Each system is built by a different team, in a different industry, using different technology. Yet they need to exchange structured data.
Step 1: Hospital Emits Patient Data
The hospital agent uses yon.health to structure patient demographics.
{
"$domain": "yon.health",
"record": "PATIENT",
"data": {
"id": "P-2026-0042",
"dob": "1985-03-15",
"sex": "female"
}
}The hospital agent didn't need to know anything about insurers or payment gateways. It structured its output according to yon.health — a shared vocabulary.
Step 2: Insurer Processes the Claim
The insurance agent receives the health data, validates it against yon.health, and structures its output using yon.insurance.
{
"$domain": "yon.insurance",
"record": "CLAIM",
"data": {
"claim_id": "CLM-2026-1847",
"patient_ref": "P-2026-0042",
"procedure_code": "99213",
"amount": 450.0,
"currency": "USD",
"status": "approved"
}
}ℹ️Note
The insurer validated the patient data against yon.health field definitions
before processing. If patient_id were missing, the claim would be rejected
at the edge — not midway through processing.
Step 3: Payment Gateway Settles
The payment agent receives the insurance claim, validates it against yon.insurance, and settles using yon.ecommerce.
{
"$domain": "yon.ecommerce",
"record": "TXN",
"data": {
"id": "TXN-2026-9283",
"claim_ref": "CLM-2026-1847",
"amount": 450.0,
"currency": "USD",
"method": "ach",
"status": "settled"
}
}What Made This Possible?
No integration meetings. No shared codebases. No API contracts negotiated between teams. Each agent:
- Fetched the relevant domain schema from the registry
- Validated incoming data against the schema
- Structured its output according to the next domain in the chain
The shared vocabulary — the domains — was the only integration layer.
Note: These JSON payloads are illustrative — they show how domain-validated data might be exchanged between agents. The wire format is application-specific; domains define the vocabulary, not the transport.
Second Example: Logistics → Trade Finance
The same pattern applies across any industry boundary:
Logistics agent
Emits shipment data using yon.logistics
Trade finance agent
Consumes it and structures a letter of credit using yon.fintech
Customs agent
Validates both using yon.legal
Each agent only needs to know its own domain and the domain of its input.