Desk Behavior

The Operator Desk is the operator’s execution entry point. It shows queued jobs, the active job, and recent completions. It is where an operator starts their work each day.

The Desk is not a full execution environment — that is the Jobs surface. The Desk is the queue and cockpit.

Operator workflow entry

When an operator logs in and goes to their Desk, they see:

The queue — whether any jobs are ready to be claimed
The active job — whether a job is currently in progress
Recent completions — the last few completed jobs
Trust signals — how many ⭐ signals have been earned from completed work (internal visibility only)

From here, an operator claims a job and moves to the Jobs surface to execute it.

What appears on the Desk

Only jobs that have been explicitly created by an admin or approved operator governance flow appear here.

A request being submitted does not create a job. A task being approved does not automatically create a job. The job only appears on the Desk after the Create Job action has been taken.

This means:

If a customer submits a request, the operator does not immediately see it in their Desk
The request must move through intake → task → approval → assign → Create Job
Only then does it appear as a claimable job

This is the governed handoff between the governance zone and the execution zone.

Why some things may not appear

Common reasons a job is not visible in the Desk:

Situation	Why it’s not visible
Request submitted but task not reviewed	Task is in the governance queue, not yet a job
Task approved but Create Job not run	The explicit bridge to execution has not been crossed
Job created but assigned to a different operator	Jobs are scoped to their assigned operator
Access state is `limited` or `suspended`	Desk is blocked for limited/suspended operators

If the operator can see a task in their Task Inbox but not a job in their Desk, the admin or operator governance flow has not completed the Create Job step yet.

Desk panels

Ready to Claim — shows a queued job when one is available and ready to be started. The operator can click “Claim & start” to begin.

Active Job — shows a job currently in progress. The operator can open it in the Jobs surface for full execution, or complete it from the Desk if the service is simple.

Recent Completions — shows the last few completed jobs with timestamps.

Trust Signals — shows the operator’s total ⭐ signal count and the state (none or present). Labeled as internal visibility only. Earned from completed work.

From Desk to Jobs

When an operator claims a job or views an active job, they are redirected to the Jobs surface. The Desk is the entry point; the Jobs surface is where the detailed execution workflow happens.

Desk (queue/status) → Jobs surface (execution, evidence, completion)

Route

/operators/[slug]/desk

Guardrails

Preserve the distinction between planned, partial, and live.
Avoid marketing language.
Keep IDs, namespaces, and lifecycle terms precise.