Work
A unit of value to be done — a lead, a ticket, an AI task, an order. The cargo the clearing lifecycle carries.
Work is a unit of value to be done — Work (Routable)
in the API. It is cargo-agnostic by design: a lead, a support ticket, an AI task,
an order, an inference request. The cargo changes; the machine does not. A
Routable carries a free-form type string and a payload, not a hardcoded schema,
so one pipeline clears every kind of work.
Work enters a pool — a market with rules: eligibility criteria, capacity budgets, SLA targets, dedup windows, quality gates, and a market mechanism. Before it is priced or routed, the trust plane runs — fraud scoring, deduplication, consent validation, quality scoring — so bad work is rejected or flagged before it costs anyone money.
Routable and pools exist today.Lifecycle
When work is cleared through a market, its session moves through
MarketSessionStatus:
MarketSessionStatusThe market is created and workers are being solicited to bid.
MarketSessionStatusBids arrive and are cleared by the session's algorithm.
MarketSessionStatusA winner is selected and the routing decision is committed.
MarketSessionStatusOff-ramps when no clearing is possible.
Where to go deeper
The Clearing Primitives
Seven primitives describe everything Ductor does — Work, Worker, Bid, Route, Receipt, Settlement, and Warranty — and how each maps onto the API.
Worker
Anyone who can take Work — a person, a team, an external system, or an AI agent — unified into one identity with capacity, capabilities, and a settlement account.