Concord
Contracts for the actions AI agents take.
Durable execution tells you what ran. Concord records what the action meant, who authorized it, which systems it touched, and how to undo it when something goes sideways.
Oversight of agent actions is an openly unsolved problem, by the published account of research groups inside the companies shipping agents. Concord is a proposal for the missing layer.
Concord is the action layer of a larger governance stack. How it fits with Lattice: The worker and the action.
One command shape across agent loops, deterministic jobs, connector calls, approvals, artifacts, memory, and compensation.
Read this in one sitting
Why agents need a contract
Durability preserves execution. It does not preserve intent. This piece frames the gap Concord closes.
Read part 1 02Contract, not runtime
Draws the boundary between Concord, DBOS, LangGraph, OPA, OTel, and Postgres with interactive demos.
Read part 2 03A day in the life
Traces a hotel booking end to end, then toggles between full Concord, minimal Concord, and no contract.
Read part 3