Understand It
The model behind Ductor — what each piece is and why it works that way. The track to read before you build anything.
The largest track, and the one to read first if the vocabulary is new. These pages explain what a thing is and why it works that way. No task to complete, no endpoint to call.
Work has to clear
The thesis: price, route, execute, settle, prove. Read this first.
The clearing primitives
Seven nouns that describe everything Ductor does, and how each maps onto the API.
Core concepts
The execution and routing engines — coordinator, DAG model, queue, idempotency.
Architecture
How the Go engine is built: layers, single-writer coordinator, storage, extension points.
A suggested order
The primitives give you the nouns; the concepts give you the machinery that moves them; the architecture explains why the machinery is shaped that way.
Route execution model
Steps, edges, scatter/gather, waits — the vocabulary for describing durable work.
Routing pipeline
How an incoming event becomes a concrete assignment, stage by stage.
Idempotency & exactly-once
What is actually guaranteed under retries and crashes — and where the gap is.
Durability model
Serial state ownership, parallel execution, and the boundary between them.
Then pick a direction
Once the model makes sense, the other tracks are about doing something with it — clicking, calling, extending, or running it.