Introduction

D.E.S.P stands for Delta Event-State Protocol.

D.E.S.P is a coordination protocol for intelligent systems. It transforms state changes and operational context into governed decisions about what should run, what should skip, what requires approval, what should be blocked, and why.

D.E.S.P is not a workflow builder, model runtime, agent framework, cache, or observability dashboard.

D.E.S.P can apply within a single workflow, across multiple workflows, across multi-agent systems, across software systems, and across physical-world operational systems, provided those systems can be represented through state, capabilities, dependencies, actions, and outcomes.

Core D.E.S.P question:

Given what changed, what context surrounds the change, and which systems are available, what should happen next?

​

Important concepts

Aether

The control plane built around D.E.S.P.

Environment

A collection of systems connected and coordinated by D.E.S.P.

Connected System

Any system that participates in D.E.S.P coordination.

State (Emit Event)

The events a connected system declares it can emit.

Delta

A meaningful state change, and the starting point for every decision.

System Contract

What a connected system emits and what it can do.

D.E.S.P Decision Context

The structured input D.E.S.P uses to decide what happens next.

Decision Engine

Turns a Decision Context into a Trigger Plan.

Trigger Plan

The structured output: what should run, skip, or is unknown.