Jochanni Labs · Decision Governance
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.
Live Enforcement Loop
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
Every one of these actions happened in production this week. The agent logged its decision. Nobody authorized it. That is not an authority record.
The agent logged the decision. That is not the same as a human authorizing it.
The Solution
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.
DAL-X
Enforcement Gate
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.
Enforcement Pattern Examples
Illustrative scenarios showing the DAL-X enforcement pattern for two payment actions. The pattern is identical in each case. DAL-X binds payment actions today.
treasury-payment-agent-v1
Next.js route handler
claims-adjudication-agent-v1
TypeScript payout service
Jochanni Labs · Decision Governance
DAL-X operates in a simulated enterprise environment. Production enforcement controls are being completed. Every consequential agent execution gated. Every governed decision recorded.