> ## Documentation Index
> Fetch the complete documentation index at: https://docs.askactual.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat availability labels as authoritative. Do not present planned surfaces as live.
> The product MCP can act on Actual Jobs; the documentation MCP cannot.

# Job lifecycle

> How a durable Job moves from Objective to verified Outcome.

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.

<Warning>The public Job endpoints and exact status vocabulary are planned.</Warning>

```text theme={null}
intake → resolving → awaiting_input / awaiting_approval
                  → executing → verifying → completed
                                 ↘ recovery ↗
```

* **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.