DAL-X│

Jochanni Labs · Decision Governance

DAL-X
In The Field

Five enterprise deployments. Five domains. Real integration code. One enforcement pattern: no DAL-X authority, no execution.

Scroll to explore
01/Financial Services

Treasury Payment Agent

treasury-payment-agent-v1→payments-api·vendor_payment
Jochanni Labs · Forward DeployedAlex Chen · Sr. Engineer, Treasury Systems

Field Engagement

AC
Alex Chen
We have treasury-payment-agent-v1 running in production. It generates wire transfer instructions and posts them directly to our payments API. 200 to 300 transactions a day.
JL
DAL-X · Forward Deployed
Walk me through the execution path. Where does the agent output actually touch the payments API?
AC
Alex Chen
The agent formats a wire object, signs it with our service key, and POSTs to /api/payments/wire/initiate. Fully automated. No human ever sees the wire before it goes out.
JL
DAL-X · Forward Deployed
That route is the interception point. We put the DAL-X enforcement gate there. The agent still runs - but execution is blocked until a reviewer grants authority and a token is issued.
AC
Alex Chen
So we wrap that route handler with the middleware?
JL
DAL-X · Forward Deployed
Exactly. The agent submits its output to DAL-X ingest first. DAL-X evaluates it, blocks it, puts it in the queue. Reviewer approves, DAL-X issues a single-use token. The agent presents that token at the gate. Only then does the wire execute.

Integration Code

typescript
Next.js Route Middleware
// app/api/payments/wire/initiate/route.ts
export async function POST(req: Request) {
const wire = await req.json()
// No authority check - agent output goes directly to execution
const result = await paymentsClient.initiateWire(wire)
return Response.json(result)
}

Execution Authority Chain

Agent Output

ingest-agent-output

Execution Blocked

default state

Review Queue

human reviewer

Authority Granted

decision record

Gate Cleared

execution token

Execution

receipt recorded

02/Healthcare

Clinical Decision Agent

clinical-decision-agent-v2→ehr-execution-api·prescribe_medication
Jochanni Labs · Forward DeployedDr. Sarah Okafor · Principal Engineer, Clinical AI

Field Engagement

DSO
Dr. Sarah Okafor
Our clinical-decision-agent evaluates patient charts and generates medication recommendations. It writes prescriptions directly to the EHR via our FHIR proxy. The agent flags high-risk cases in a separate dashboard.
JL
DAL-X · Forward Deployed
Does the EHR write wait for the flag review, or do they happen concurrently?
DSO
Dr. Sarah Okafor
Concurrently. The flag is informational. The write isn't gated. Our compliance team flagged it in the last audit.
JL
DAL-X · Forward Deployed
Right. The flag and the gate are two different things. A flag tells you something happened. A gate stops it from happening until authority is confirmed. We need to add the gate.
DSO
Dr. Sarah Okafor
We use Express for the FHIR proxy layer. Can DAL-X sit there?
JL
DAL-X · Forward Deployed
Yes. The Express middleware reads the DAL-X token from the request header. Token absent, expired, or scope-mismatched - the FHIR write is blocked at the proxy. The agent never reaches the EHR without authority.

Integration Code

typescript
Express Middleware
// fhir-proxy/routes/prescriptions.js
app.post('/fhir/MedicationRequest', async (req, res) => {
const { patientId, medication, dosage } = req.body
// AI recommendation writes directly to EHR
// Flag is informational only - no execution gate
const result = await fhirClient.create('MedicationRequest', {
subject: { reference: 'Patient/' + patientId },
medicationCodeableConcept: medication,
dosageInstruction: [dosage],
})
res.json(result)
})

Execution Authority Chain

Agent Output

ingest-agent-output

Execution Blocked

default state

Review Queue

human reviewer

Authority Granted

decision record

Gate Cleared

execution token

Execution

receipt recorded

04/Manufacturing

Procurement Agent

procurement-agent-v1→procurement-api·issue_purchase_order
Jochanni Labs · Forward DeployedJames Kowalski · Platform Engineer, Supply Chain Systems

Field Engagement

JK
James Kowalski
Our procurement agent monitors inventory and automatically issues purchase orders to suppliers when thresholds are hit. It writes directly to our SAP ERP via our internal HTTP proxy.
JL
DAL-X · Forward Deployed
What's the dollar range on these POs?
JK
James Kowalski
The agent is supposed to stay under $50K. But last quarter it issued a $340K PO to the wrong supplier because of a data quality issue. We caught it in time, but it was close.
JL
DAL-X · Forward Deployed
That's exactly what the authority gate stops. Amount threshold enforcement, supplier validation, anomaly detection - all evaluated at ingest before the PO touches SAP.
JK
James Kowalski
We run Go services. Our ERP proxy is a chi router. How does DAL-X slot in?
JL
DAL-X · Forward Deployed
A middleware function on your router. It reads the DAL-X token from the request header and validates it at the enforcement gate. Token missing or target mismatch - the ERP write is blocked before it happens.

Integration Code

go
Go HTTP Middleware
// procurement/handlers.go
func (h *Handler) IssuePO(w http.ResponseWriter, r *http.Request) {
var po PurchaseOrder
if err := json.NewDecoder(r.Body).Decode(&po); err != nil {
http.Error(w, "bad request", 400)
return
}
// AI-generated PO writes directly to ERP
// No dollar limit enforcement. No authority gate.
result, err := h.erpClient.CreatePurchaseOrder(r.Context(), po)
if err != nil {
http.Error(w, err.Error(), 500)
return
}
json.NewEncoder(w).Encode(result)
}

Execution Authority Chain

Agent Output

ingest-agent-output

Execution Blocked

default state

Review Queue

human reviewer

Authority Granted

decision record

Gate Cleared

execution token

Execution

receipt recorded

05/Insurance

Claims Adjudication Agent

claims-adjudication-agent-v1→claims-processing-api·approve_claim_payout
Jochanni Labs · Forward DeployedPriya Sharma · Engineering Manager, Claims Platform

Field Engagement

PS
Priya Sharma
We automated claims adjudication last year. The agent evaluates claims under $25K, applies coverage rules, and issues payouts via our payment processor. About 2,000 claims a week.
JL
DAL-X · Forward Deployed
When the agent issues a payout, is there any record of who authorized it?
PS
Priya Sharma
The agent logs its decision. But there's no human authorization record. Our compliance team flagged it in the last audit cycle.
JL
DAL-X · Forward Deployed
That's the gap DAL-X closes. Every payout needs a decision record - either a human reviewer approved it, or it passed a rule-based auto-approval path. In both cases, DAL-X writes the immutable record before execution.
PS
Priya Sharma
We're TypeScript. How do we wire this into the adjudication flow?
JL
DAL-X · Forward Deployed
The validateExecution call wraps your payout trigger. You pass the execution token from the ingest response. If the token clears all gate checks, the payout runs. If not, execution throws. A receipt is written in both cases - approved and denied.

Integration Code

typescript
TypeScript SDK - validateExecution
// claims/adjudicate.ts
async function adjudicateClaim(claim: Claim): Promise<void> {
const decision = await claimsAI.evaluate(claim)
if (decision.approved) {
// AI approval goes directly to payout processor
// No authority record. Compliance gap.
await payoutProcessor.initiate({
claimId: claim.id,
amount: decision.approvedAmount,
currency: 'USD',
payee: claim.claimant,
})
}
}

Execution Authority Chain

Agent Output

ingest-agent-output

Execution Blocked

default state

Review Queue

human reviewer

Authority Granted

decision record

Gate Cleared

execution token

Execution

receipt recorded

One Pattern. Every Domain.

The integration is always the same.

Submit to DAL-X. Get blocked. Reviewer grants authority. Token issued. Present token at the gate. Gate clears. Execution happens. Receipt written. Timeline proved.