Jobs

Jobs is the run/operate surface — where your recurring work runs, and where you watch it, trust it, and schedule it.

If Pulse is where you read results, Jobs (/jobs) is where you watch work run. A job is a workflow set up to run — on demand or on a schedule. The Jobs page lists your jobs with their trigger, latest run, and a trust bar; opening one shows its full run history and live monitoring.

What lives here

• Run history — every run of a job, with status, cost, latency, and the verifier verdict on each row. Open a run for the full step-by-step trace, or retry from a failed step.
• Live monitoring — watch a run in progress, step by step, including approval and input gates.
• Trust rollup — a per-job trust bar summarizing recent runs as clean / repaired / failed, plus the current clean streak. It answers "can I rely on this job unattended?" at a glance.
• Schedules — recurring and one-off schedules for the job. Pencel catches up missed fires on startup, guards against overlapping runs, and can pause a job after repeated failures.

Jobs vs. Workflows vs. Runs

These three are easy to conflate:

Term	What it is
Workflow	The definition — the authored steps. You edit it in the Workflows surface (author-only).
Job	A workflow set up to run — with a trigger/schedule and history. You operate it here on the Jobs page.
Run	A single execution of a job. See Runs for statuses, gates, and auto-repair.

A guided task you finalize lands here as a job. When a job completes, its result is published as a card in Pulse.

What's next

• Runs — statuses, approval gates, verified outputs, auto-repair
• Triggers & Schedules — Heartbeat and cron cadences
• Pulse — where a job's results land as cards
• Workflows — authoring the definition behind a job