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

# Statuses and terms

> Reference for the Signals and Actions states shown in PlainRouter.

## Signal health

| API value           | UI label            | Meaning                                                                                       |
| ------------------- | ------------------- | --------------------------------------------------------------------------------------------- |
| `setup_required`    | Setup required      | Signal collection or hostname activation is incomplete.                                       |
| `awaiting_data`     | Awaiting data       | Setup is active, but no event has been recorded.                                              |
| `active_unmeasured` | Measurement pending | Events exist, but required delivery, EMQ, or reconciliation measurements are incomplete.      |
| `needs_attention`   | Needs attention     | At least one warning or critical diagnostic is active.                                        |
| `healthy`           | Healthy             | Event activity and all required measurement categories are recent and have no active warning. |

## Signal infrastructure

### Signal tracker

| Value      | Meaning                                    |
| ---------- | ------------------------------------------ |
| `pending`  | Setup has started but is not fully active. |
| `active`   | The tracker can receive events.            |
| `inactive` | The tracker is not active.                 |

### Collection hostname

| Value                | Meaning                                                   |
| -------------------- | --------------------------------------------------------- |
| `pending_validation` | PlainRouter is waiting for DNS or certificate validation. |
| `active`             | The hostname and HTTPS certificate are active.            |
| `failed`             | Hostname provisioning or validation failed.               |
| `deactivated`        | The hostname is no longer active.                         |

## Destination delivery

| Value                    | Category | Meaning                                                 |
| ------------------------ | -------- | ------------------------------------------------------- |
| `queued`                 | Pending  | Waiting for destination delivery.                       |
| `sent`                   | Pending  | Sent and awaiting the destination result.               |
| `retrying`               | Pending  | Retrying a transient failure.                           |
| `accepted`               | Accepted | Meta accepted the event.                                |
| `failed:auth`            | Failed   | Meta rejected the access token.                         |
| `failed:permanent`       | Failed   | A non-retryable payload or destination error occurred.  |
| `failed:unknown`         | Failed   | Delivery stopped after an unclassified failure.         |
| `expired`                | Terminal | The event is outside Meta's seven-day freshness window. |
| `skipped:consent`        | Terminal | Advertising user-data consent was denied.               |
| `skipped:no_destination` | Terminal | No active destination was configured.                   |
| `skipped:duplicate`      | Terminal | The destination had already received the event.         |

The dashboard's acceptance-rate denominator includes recent non-test deliveries in the delivery ledger. Its pending count groups `queued`, `sent`, and `retrying`. Its failed count groups the three `failed:*` states.

## Performance measurability

| Status           | Reason          | Meaning                                                                             |
| ---------------- | --------------- | ----------------------------------------------------------------------------------- |
| `measurable`     | `null`          | At least one report exists in the requested window and the latest report is recent. |
| `not_measurable` | `no_history`    | No usable reconciliation report exists for the requested window.                    |
| `not_measurable` | `stale_history` | The latest reconciliation report is more than 48 hours old.                         |

## Policy decisions

| Value              | Meaning                                                                                                                    |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------- |
| `require_approval` | A person must decide in the approval queue.                                                                                |
| `block`            | At least one safeguard prevents the proposal from proceeding.                                                              |
| `allow`            | Policy permits the current phase to proceed. Executable work must receive `allow` again during the execution-time recheck. |

## Action batch statuses

| Value                           | Meaning                                                                                              |
| ------------------------------- | ---------------------------------------------------------------------------------------------------- |
| `pending`                       | Waiting for human approval.                                                                          |
| `approved_without_execution`    | Human-approved suggest-only recommendation. Terminal and not executed.                               |
| `rejected`                      | Human-rejected recommendation. Terminal.                                                             |
| `blocked`                       | Stopped by policy or a safety condition. Terminal.                                                   |
| `approved`                      | Human-approved for an execution-enabled path and queued for a fresh policy check.                    |
| `auto_approved`                 | Automatically approved by an execution-enabled policy mode.                                          |
| `executing`                     | An execution-enabled batch is in progress.                                                           |
| `executed_pending_verification` | A provider write has a durable receipt, but exact verification is still pending. Not Landed.         |
| `compensating`                  | PlainRouter is restoring provider state and verifying the restoration.                               |
| `measuring`                     | A closed provider-measurement run is active. Explicitly Not Landed.                                  |
| `completed`                     | All actions have exact verified provider receipts. Counted as Landed unless marked measurement-only. |
| `failed`                        | Execution failed.                                                                                    |
| `rolled_back`                   | Prior state was restored after failure or anomaly.                                                   |
| `rollback_incomplete`           | At least one attempted restoration failed and needs attention.                                       |

## Action statuses

| Value                           | Meaning                                                                    |
| ------------------------------- | -------------------------------------------------------------------------- |
| `pending`                       | The action belongs to a batch awaiting a decision.                         |
| `approved_without_execution`    | Suggest-only approval. Terminal and not executed.                          |
| `rejected`                      | A person rejected the action. Terminal.                                    |
| `executing`                     | Provider execution is in progress.                                         |
| `executed_pending_verification` | The action has a committed receipt but is not yet exactly verified.        |
| `verified`                      | The receipt-addressed provider state matches the approved action.          |
| `compensating`                  | Verified restoration is in progress.                                       |
| `measuring`                     | The action belongs to a closed provider-measurement run and is Not Landed. |
| `execution_uncertain`           | Provider commit state could not be resolved safely.                        |
| `failed`                        | Execution or verification failed.                                          |
| `rolled_back`                   | The provider change was restored and the restoration was verified.         |
| `blocked`                       | Policy or an execution boundary stopped the action before execution.       |

## Core terms

<AccordionGroup>
  <Accordion title="Gateway-verified">
    A conversion counted as accepted through PlainRouter's stored delivery and reconciliation records. It does not mean independently audited business revenue.
  </Accordion>

  <Accordion title="Meta-reported">
    A conversion count captured in a stored reconciliation report from Meta for the connected dataset and report date.
  </Accordion>

  <Accordion title="Observed gap">
    Gateway-verified count minus Meta-reported count. It is a count difference, not CPA or incrementality.
  </Accordion>

  <Accordion title="Evidence provenance">
    The source tool, scope, exact fields, observation time, window, and measurability recorded with an Actions proposal.
  </Accordion>

  <Accordion title="Human-supplied target">
    A platform entity selected by a person. It establishes selection only and does not prove current target state.
  </Accordion>

  <Accordion title="Suggest only">
    The default Actions mode in which every passing proposal requires human review and approval terminates without execution.
  </Accordion>

  <Accordion title="Landed">
    A production action batch in which every action has a durable provider receipt and an exact matching verification read. Approval or a provider write alone is not Landed.
  </Accordion>

  <Accordion title="Executed pending verification">
    A committed provider action that has not yet reached exact verification. PlainRouter may continue scheduled receipt-addressed reads, but the action remains Not Landed.
  </Accordion>

  <Accordion title="Compensation">
    A safety restoration against the exact receipt target. PlainRouter considers it successful only after a provider read verifies deletion, archive, or the required restored state.
  </Accordion>

  <Accordion title="v1 non-recomputable">
    A historical audit segment whose predecessor links are preserved but whose hashes cannot be fully recomputed from durable row fields.
  </Accordion>

  <Accordion title="v2 recomputable">
    The durable canonical audit segment whose stored rows can be cryptographically recomputed within the current database snapshot.
  </Accordion>
</AccordionGroup>
