Skip to main content
A Job is the durable business record for one Objective. It survives Host disconnects, long waits, and execution restarts. A conversation, workflow, Agent run, or MCP Task may project a Job, but none is the Job itself.
The public Job endpoints and exact status vocabulary are planned.
  • Intake records the User’s request and interprets the Objective and Constraints.
  • Resolving researches and develops a Plan and Provider Offers.
  • Awaiting input pauses rather than guessing about material ambiguity.
  • Awaiting Approval waits for explicit authority for an exact proposal.
  • Executing performs ledgered actions through bounded Capabilities.
  • Verifying evaluates Evidence against a versioned policy.
  • Recovery reconciles ambiguity or pursues a remedy after failure.
  • Completed means successful Verification created an Outcome.

​
Revisions

Changing a Constraint increments the Job revision. Plans, Approvals, and actions carry the revision from which they were derived. A stale operation fails closed and must be replanned or presented again.

​
Terminal states

Cancellation or termination can be permitted from nonterminal states. Neither means the Objective was achieved. Human Exception is controlled review, not silent completion.
Last modified on August 13, 2026