> Discover all available Postdom documentation from the machine-readable index: https://postdom.com/llms.txt

Reference · execution lifecycle

# Run states

A post has one overall state. Each destination retains its own queued, sent, published, or failed evidence.

Eleven wire values

## Post states

Post state summarizes the scheduled unit. Recoverable human states remain separate from execution outcomes.

| State | Entered when | Next | Agent handoff |
| --- | --- | --- | --- |
| draft | The strictest destination is in L0 Manual. | scheduled | A human must publish now or reschedule. |
| requires_approval | The request needs an individual human decision. | scheduled · changes_requested · rejected · missed_approval | Wait for the supervisor. |
| changes_requested | A human returns structured post feedback. | No configured agent revision call | Return the exact state and feedback to a human. |
| rejected | A human rejects the pending post. | No configured transition | Stop and report the decision. |
| missed_approval | The scheduled approval deadline passes unresolved. | scheduled | A human may publish now or reschedule. |
| missed_schedule | Execution begins more than 15 minutes after the schedule. | scheduled | A human may publish now or reschedule. |
| scheduled | A human, eligible plan, or valid L3 policy authorizes execution. | publishing · requires_approval · draft · missed_schedule · failed | Wait until due, then read the exact state. |
| publishing | The worker acquires the active execution lease. | published · partial · failed | Continue reading destination outcomes. |
| published | Every destination is published. | Stable recorded success | Report success and continue to measurement. |
| partial | Published and failed destinations coexist. | May reconcile after recoverable local failure | Return every destination outcome and error. |
| failed | Every destination fails, or execution fails locally. | May reconcile after recoverable local failure | Return failure evidence to a human. |

Four wire values

## Destination states

Destination evidence determines published, partial, failed, or still-publishing post state. Never replace these values with `action_required`.

| State | Entered when | Next | Agent handoff |
| --- | --- | --- | --- |
| queued | Reserved in storage; no configured production path currently creates it. | Modeled: sent · published · failed | Do not expect it from the current provider result. |
| sent | The provider accepts the destination request. | published · failed | Keep reading for authoritative evidence. |
| published | The provider confirms destination publication. | Stable recorded success | Preserve IDs, URL, and publication time. |
| failed | The provider or local watchdog records failure. | May become published after recoverable timeout evidence | Return the error code and detail. |

Limited reconciliation

## Recovery boundary

Partial or failed posts may reconcile only after a recoverable local failure. Ordinary platform rejection does not imply an automatic retry.

`provider_down`

Response code recorded on the durable result. Late provider evidence may update the outcome.

`publish_timeout`

Response code recorded on the durable result. Late provider evidence may update the outcome.

`recovery_pending: true`

Boolean marker recorded as recovery_pending: true on the durable result. Late provider evidence may update the outcome.

Post and destinations

## Mixed outcome

The post-level `partial` value summarizes different terminal destination outcomes. Identifiers and values below are synthetic.

_EXAMPLE RESPONSE EXCERPT · SYNTHETIC VALUES_

```
{
  "status": "partial",
  "publishes": [
    { "platform": "instagram", "status": "published" },
    { "platform": "youtube", "status": "failed" }
  ]
}
```

 VERIFIED · 26 AUGUST 2026  **Post store · Destination state derivation · Webhook recovery guard**

Recovery is limited to recorded local failure conditions.