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

# Public states

> The partner-safe state vocabulary and how to read the opaque ones.

Integrations should reason about engagements in the state vocabulary below. The names are stable enough to map partner-side status onto, and no name encodes internal criteria. Where a state represents internal review, it is deliberately opaque: the state shows that an engagement is in review, not why.

## The vocabulary

| State                      | Meaning                                                      | Partner signal                                   |
| -------------------------- | ------------------------------------------------------------ | ------------------------------------------------ |
| `proposal_accepted_paid`   | The proposal is accepted and paid.                           | An engagement is about to exist.                 |
| `engagement_created`       | The engagement record exists.                                | Work can be set up.                              |
| `onboarding_open`          | Onboarding is open for controlled inputs.                    | Begin collecting and submitting inputs.          |
| `document_gate_open`       | Required inputs have been requested and are being collected. | Submit the requested inputs.                     |
| `document_gate_blocked`    | Required inputs are insufficient.                            | Something is missing; act on the input side.     |
| `ready_for_soteris_review` | Inputs are complete and queued for Soteris.                  | Handoff to Soteris is imminent.                  |
| `agent_ready`              | Preparation can begin.                                       | Automated preparation is queued.                 |
| `agent_running`            | Automated preparation is in progress.                        | Work is being prepared; no action needed.        |
| `clarification_requested`  | A clarification is needed to continue.                       | Respond to the clarification.                    |
| `soteris_review`           | Soteris is reviewing.                                        | In professional review; no partner action.       |
| `cpa_gate`                 | An opaque review state.                                      | Under review authority; no released outcome yet. |
| `deliverable_review`       | The deliverable is under final review.                       | Final review before release.                     |
| `final_payment_pending`    | Release is pending final settlement.                         | Complete final payment.                          |
| `closed_paid`              | The engagement is settled.                                   | Work is complete.                                |
| `archived`                 | The engagement is archived.                                  | Read-only record.                                |

<Info>
  `cpa_gate` and `soteris_review` signal that an engagement is under review authority and that no released outcome exists yet. Neither state discloses what is being evaluated or against what bar. Treat both as wait signals, not as inputs to partner-side logic. Who is allowed to act in each state is defined in [Actor boundaries](/workflow/actor-boundaries).
</Info>