DAL-X│

Jochanni Labs · Decision Governance

No authority.
No execution.

Consequential AI agent executions require authority before they proceed. DAL-X decides if they should - and writes a tamper-evident authority record for every governed execution.

Enforcement Loop (Illustration)

Agent Output

intercepted at intake

Execution Blocked

default state

Review Queue

human reviewer

Authority Granted

decision recorded

Gate Cleared

token validated

Execution

receipt written

The Problem

Your agents are already executing.

Illustrative examples of what agents are trusted to do today. In most deployments the agent logs its decision and the action executes. Nobody authorized it first. A log is not an authority record.

Agent
Action
Target System
Authority
treasury-payment-agent-v1
Wire transfer $340K
payments-api
No Record
clinical-decision-agent-v2
Prescription written to EHR
ehr-execution-api
No Record
contract-generation-agent-v1
Vendor agreement to DocuSign
contract-mgmt-api
No Record
procurement-agent-v1
Purchase order $280K in SAP
procurement-api
No Record
claims-adjudication-agent-v1
Claim payout $22K approved
claims-processing-api
No Record

The agent logged the decision. That is not the same as a human authorizing it.

The Solution

One gate. Every consequential agent execution.

DAL-X sits between AI agents and downstream execution systems that enforce DAL-X token verification. Execution is blocked by default. Authority is required before any consequential execution proceeds.

treasury-payment-agent-v1
claims-adjudication-agent-v1
→

DAL-X

Enforcement Gate

Intercept
Evaluate
Block
Queue
Require Authority
Issue Token
Release
Write Receipt
→
payments-api
claims-processing-api

Execution blocked by default

No submission is ever auto-released unless a rule-based or human authority decision explicitly allows it.

Four authority outcomes

Authorize, Human review, Escalate, or Deny. Blocking is the default enforcement state when valid authority is absent. Every outcome writes a tamper-evident authority record before execution status can change.

Token required at the gate

Downstream systems present the DAL-X token at the enforcement gate. No valid token. No execution. The gate applies to execution paths that enforce DAL-X token verification.

Reference Integration

One payment integration, in its real code.

A treasury agent on the Claude Agent SDK and a separate payments hub that verifies DAL-X authority itself. Together they passed the full DAL-X demo on real systems. Other actions bind the fields their target names; a vendor master account change ran that path on real systems against test data.

01Treasury Payments

treasury-payment-agent

Claude Agent SDK · Hono

See the integration→with the endpoint calls in order

Jochanni Labs · Decision Governance

No authority.
No execution.

DAL-X has run its full demo end to end on real systems: a Claude Agent SDK agent and a payments hub that refuses any payment without DAL-X authority. There is no customer deployment yet. The next step is a paid pilot against a real workflow.