Revisioned Job Definitions

Define the workflow once.
Run it without rebuilding the prompt.

Jobs turn recurring work into a reusable product surface. Instead of remembering a long prompt, users complete a validated form and launch a frozen workflow with explicit skills, policies, team options, and expected outputs.

Workflow as a contract

A form for the user.
A frozen recipe for the runtime.

Every launch records the exact Job Definition revision and snapshot hash. Retries keep the retained definition policy, so a later edit cannot silently change an earlier run.

RUN JOB / RESEARCH BRIEFrevision 7
Launch Job
DEFINITION CONTRACTrunnable
SKILLresearch-orchestratorrev. 3
TEAMresearch + citation judgeoptional
OUTPUTSbrief.md · evidence.jsonrequired
RETRYsame frozen policymax 3
SNAPSHOT SHA-25643ab90…8e12pinned at launch
What the definition retains
01

Input form

Text, numbers, choices, conditional fields, attachments, transcripts, voice profiles, and catalog references.

02

Execution recipe

A versioned task template, specialist skill, model policy, and optional authorized agent-team preset.

03

Output contract

Named required artifacts, media types, publication behavior, and bounded execution limits.

04

Run controls

Mission continuation, queue steering, attachments, artifacts, recovery, and server-enforced retry rules.

Repeatable, not automatically scheduled: Job Definitions standardize recurring workflows and make them easy to rerun. Calendar or event scheduling requires a separate integration or trigger.

Reusable operational knowledge

Replace prompt folklore with a versioned workflow.

Give recurring work a clear form, a governed execution recipe, and an output contract that can be inspected after every run.

Explore AgenZync