Worker

A Worker is anyone who can take Work — a person, a team, an external system, or an AI agent. It is the primitive that makes "human or agent, same rails" literal: one identity with capacity, capabilities, a quality history, a price, and a settlement account, regardless of what is on the other side.

Today a worker reads as a worker registration projected over the existing recipient and immutable agent-definition types — Worker (WorkerRegistration). A recipient is one kind of worker; an AI agent is another. A recipient projects into a worker directly; an agent projects only once a caller pins an immutable agent definition (id, version, and hash), so a worker's identity can never drift under an award.

What every worker shares

Capacity

Concurrency and daily limits — an at-capacity worker is not eligible.

Availability

Static schedules and dynamic sources; for an agent, budget headroom and runtime health.

Eligibility

Pool membership, territories, and CEL attributes.

Settlement account

Where a worker is paid, and charged back against, at settlement.

Ownership

The owning principal is derived from the authenticated caller — never the payload — and every mutation of an owned worker is owner-gated, refused without revealing whether a foreign worker exists.

Bid eligibility

A worker can only bid when it is enabled, ready, within capacity, and — for an agent worker — bound to a pinned definition. A disabled, paused, unpinned, or at-capacity worker is refused with a normalized reason rather than silently dropped. Registry-owned readiness is reported under a monotonic fence, so a stale report is refused visibly — a worker that said "not ready" can never be silently overwritten back to ready by a late arrival.

Where to go deeper