A job is a specific assignment given to a work desk: a unit of work with a name, inputs, a deadline, and an expected output.
The job is to the desk what a task is to a session — the bounded unit of work the operator tracks, assigns, and reviews. Where the desk emphasizes the persistent operational context, the job emphasizes the discrete piece of work moving through it.
Jobs and queues
A work desk typically holds multiple jobs in a queue. The desk charter defines the queue discipline: first-in-first-out, priority ordered, or deadline sorted. The CEO agent is responsible for assigning jobs to the correct desk and for deciding queue order when multiple desks are available.
A job enters the queue, waits for the desk to reach it, receives context and tooling from the desk, executes, and produces an output. The desk then returns the output to the CEO agent or directly to the requesting party.
Job boundaries
A job has a clear boundary: it has an input, a definition of done, and a delivery mechanism. Jobs that do not have clear boundaries — where "done" is undefined or the output contract is vague — are the most common source of CEO agent failures.
The fix is in the intake step: refuse the job until the input, the definition of done, and the delivery mechanism are explicit. A job that cannot be described cannot be executed reliably.
Related terms
The job is the work unit inside the work desk. The desk is the persistent context; the job is the discrete assignment moving through it. The CEO agent is the layer that assigns jobs to desks and reviews the outputs.
For the full field note, see Work Desks and Specialty Agents.