# Stripe pack: reading a verdict and its reason codes

Every verdict and reason code the [Stripe Customer Operations pack](/docs/packs/stripe-customer-operations) can produce
(version 2.3.0), what each means and what to do about it. The list is generated from the checks of the five contracts
and from the engine's verdicts on the pack's 73 fixture cases; the last column says whether a fixture case produces
the code, so a "no" is a code a contract can report that no shipped case exercises.

## The shape of a verdict

`GET /v1/actions/{action_id}` returns two lenses, each with a verdict and its reason codes. The **outcome** lens
answers whether the thing happened in the systems of record. The **policy** lens answers whether it was allowed and
done as approved: preconditions, limits, forbidden effects and totals count only there. Read both: an action can have
happened (outcome PASS) and still be wrong (policy FAIL).

The plain read evaluates nothing. Its `lenses` are the verdict as last stored: at recording, by a wait that saw the
action settle, by `POST /v1/actions/verify`, or by the re-check when the window closes. While an action has not been
stored as settled, `status`, `checks` and `summary` are rebuilt from the facts stored now, so they can be ahead of the
lenses: a headline that reads PASS above lenses that still read UNKNOWN or FAIL means the stored verdict is older than
the evidence. `GET /v1/actions/{action_id}/wait` evaluates what has arrived (`timeout=0` answers at once); use it
after a push or a sync.

| You see | It means | What to do |
|---|---|---|
| `status: pending` | The window is still open, or a source the contract reads has not synced past it. The lenses show the provisional verdict of the evidence so far; a provisional FAIL only says an effect has not been seen yet. | Wait, or use `GET /v1/actions/{id}/wait`. `settlement.waiting_on` names the sources it is waiting for. Do not act on a pending FAIL. |
| `PASS` | Outcome: every expected effect was observed in time, from a source trusted enough. Policy: that, and no precondition, limit, total or forbidden effect went against it. | Nothing. A later record can still reverse a settled PASS within the contract's lookahead. |
| `FAIL` | Outcome: the sources were current and an expected effect was missing, or a later record undid the action. Policy: any check went against the action. | Read the reason codes below; each names the check and the system. |
| `UNKNOWN` | The action could not be judged: a source never reported, nothing matched the subject, or a parameter a check reads was not recorded. | It is a setup or recording problem, not a finding about the agent. Fix the cause in the last table and the next action is judged. |

Codes read `kind:source.type` (and `.attribute` for a value comparison). The source is the name the contract uses:
with the default parameters `shopify` is the order source and `zendesk` the help-desk source, and a workspace that
names another system in the wizard sees that name in its codes instead.

## The effect did not happen, or cannot be trusted

| Code | Lens | Workflows | What happened | What to do | In a fixture |
|---|---|---|---|---|---|
| `expected_effect_missing:messaging.customer_notified` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | No customer notification was recorded / The customer was not told of the corrected invoice. The window closed, the source was current, and the record the contract expects was not there. | The agent's step did not happen, happened on another object, or happened outside the window. Your messaging system pushes `customer_notified` with an evidence key, on the subject the action names, with `occurred_at` inside the window. Check that the push happened and that an Owner or Admin attested the `messaging` source for that evidence key. | yes |
| `expected_effect_missing:shopify.order_cancelled` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | The order was not cancelled after the refund. The window closed, the source was current, and the record the contract expects was not there. | The agent's step did not happen, happened on another object, or happened outside the window. Open the Shopify connection (or the system you named as the order source) and check it has synced since the agent acted; then look at the order. | yes |
| `expected_effect_missing:stripe.credit_note` | outcome and policy | [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | No Stripe credit note exists for this invoice / No Stripe credit note reduces this invoice. The window closed, the source was current, and the record the contract expects was not there. | The agent's step did not happen, happened on another object, or happened outside the window. Open the Stripe connection: it must be healthy, hold the permission for the object (refunds, credit notes, subscriptions, invoices) and have synced since the agent acted. Then look at the object in Stripe itself. | yes |
| `expected_effect_missing:stripe.refund` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | No Stripe refund exists on this order's payment. The window closed, the source was current, and the record the contract expects was not there. | The agent's step did not happen, happened on another object, or happened outside the window. Open the Stripe connection: it must be healthy, hold the permission for the object (refunds, credit notes, subscriptions, invoices) and have synced since the agent acted. Then look at the object in Stripe itself. | yes |
| `expected_effect_missing:stripe.subscription_canceled` | outcome and policy | [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription) | Stripe does not show the subscription cancelled. The window closed, the source was current, and the record the contract expects was not there. | The agent's step did not happen, happened on another object, or happened outside the window. Open the Stripe connection: it must be healthy, hold the permission for the object (refunds, credit notes, subscriptions, invoices) and have synced since the agent acted. Then look at the object in Stripe itself. | yes |
| `expected_effect_missing:zendesk.status_change` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | The support case was not resolved / The case does not read solved in the help desk. The window closed, the source was current, and the record the contract expects was not there. | The agent's step did not happen, happened on another object, or happened outside the window. Open the help-desk connection (or the system you named as the help-desk source) and check the case; a case linked to the action's subject must exist (`ticket_to_order`, `ticket_to_subscription`, `ticket_to_invoice`). | yes |
| `effect_below_trust:messaging.customer_notified` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | No customer notification was recorded / The customer was not told of the corrected invoice. The record was received, but it is not eligible: its evidence trust class is below what the contract asks for. | A fact pushed by a key that also records actions, or by an evidence key nobody attested for the source, never satisfies these contracts. Push with an evidence key and have an Owner or Admin attest the source for that key (in the app: the evidence screen of Refund setup's real workflow, or Connections, "Evidence pipeline"), or connect the system with its connector. | no |
| `effect_below_trust:shopify.order_cancelled` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | The order was not cancelled after the refund. The record was received, but it is not eligible: its evidence trust class is below what the contract asks for. | A fact pushed by a key that also records actions, or by an evidence key nobody attested for the source, never satisfies these contracts. Push with an evidence key and have an Owner or Admin attest the source for that key (in the app: the evidence screen of Refund setup's real workflow, or Connections, "Evidence pipeline"), or connect the system with its connector. | no |
| `effect_below_trust:stripe.credit_note` | outcome and policy | [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | No Stripe credit note exists for this invoice / No Stripe credit note reduces this invoice. The record was received, but it is not eligible: its evidence trust class is below what the contract asks for. | A fact pushed by a key that also records actions, or by an evidence key nobody attested for the source, never satisfies these contracts. Push with an evidence key and have an Owner or Admin attest the source for that key (in the app: the evidence screen of Refund setup's real workflow, or Connections, "Evidence pipeline"), or connect the system with its connector. | yes |
| `effect_below_trust:stripe.refund` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | No Stripe refund exists on this order's payment. The record was received, but it is not eligible: its evidence trust class is below what the contract asks for. | A fact pushed by a key that also records actions, or by an evidence key nobody attested for the source, never satisfies these contracts. Push with an evidence key and have an Owner or Admin attest the source for that key (in the app: the evidence screen of Refund setup's real workflow, or Connections, "Evidence pipeline"), or connect the system with its connector. | yes |
| `effect_below_trust:stripe.subscription_canceled` | outcome and policy | [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription) | Stripe does not show the subscription cancelled. The record was received, but it is not eligible: its evidence trust class is below what the contract asks for. | A fact pushed by a key that also records actions, or by an evidence key nobody attested for the source, never satisfies these contracts. Push with an evidence key and have an Owner or Admin attest the source for that key (in the app: the evidence screen of Refund setup's real workflow, or Connections, "Evidence pipeline"), or connect the system with its connector. | yes |
| `effect_below_trust:zendesk.status_change` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | The support case was not resolved / The case does not read solved in the help desk. The record was received, but it is not eligible: its evidence trust class is below what the contract asks for. | A fact pushed by a key that also records actions, or by an evidence key nobody attested for the source, never satisfies these contracts. Push with an evidence key and have an Owner or Admin attest the source for that key (in the app: the evidence screen of Refund setup's real workflow, or Connections, "Evidence pipeline"), or connect the system with its connector. | yes |
| `verified_condition_not_met` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | The summary code of a FAIL: facts exist and not every expected effect was observed. It is always followed by one `expected_effect_missing` or `effect_below_trust` code per missing effect. | Read the codes that follow it. | yes |

## Something happened that must not

| Code | Lens | Workflows | What happened | What to do | In a fixture |
|---|---|---|---|---|---|
| `duplicate_effect:stripe.credit_note` | policy | [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | More than one credit note was issued / More than one credit note was issued against the invoice. More records of this kind were found in the window than the contract allows. | The agent did it twice (a retry that reached the system, a second tool). Reverse the extra one in the system of record and record that as its own action. | yes |
| `duplicate_effect:stripe.refund` | policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | More than one refund was issued. More records of this kind were found in the window than the contract allows. | The agent did it twice (a retry that reached the system, a second tool). Reverse the extra one in the system of record and record that as its own action. | yes |
| `duplicate_effect:zendesk.status_change` | policy | [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | The case was solved more than once in the window: it was reopened and closed again. More records of this kind were found in the window than the contract allows. | The agent did it twice (a retry that reached the system, a second tool). Reverse the extra one in the system of record and record that as its own action. | yes |
| `effect_attr_mismatch:stripe.credit_note.amount` | policy | [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | The credit note amount differs from the approved amount / The credit note amount differs from the approved adjustment. The record exists, and one of its values differs from what the action said was approved. | Compare the action's parameter with the record. For an amount, check the unit the action was recorded in: major units, or `units: {amount: minor}` on the mapping rule of a tool that sends cents. For the cancellation timing, check what the agent was approved to do and what it sent to Stripe. | yes |
| `effect_attr_mismatch:stripe.refund.amount` | policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | The refund amount differs from the approved amount. The record exists, and one of its values differs from what the action said was approved. | Compare the action's parameter with the record. For an amount, check the unit the action was recorded in: major units, or `units: {amount: minor}` on the mapping rule of a tool that sends cents. For the cancellation timing, check what the agent was approved to do and what it sent to Stripe. | yes |
| `effect_attr_mismatch:stripe.subscription_canceled.cancel_at_period_end` | policy | [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription) | Stripe cancelled with a different timing than approved (immediately versus end of period). The record exists, and one of its values differs from what the action said was approved. | Compare the action's parameter with the record. For an amount, check the unit the action was recorded in: major units, or `units: {amount: minor}` on the mapping rule of a tool that sends cents. For the cancellation timing, check what the agent was approved to do and what it sent to Stripe. | yes |
| `effect_observed:shopify.fulfillment_created` | policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | A shipment was created after the order was cancelled. A record the contract forbids for this workflow was found in the window. (The same code under another workflow, where the record is expected, is part of a PASS.) | Find out why the agent produced it, and undo it in the system of record if it should not stand. | yes |
| `effect_observed:stripe.invoice_voided` | policy | [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | The invoice was voided instead of adjusted. A record the contract forbids for this workflow was found in the window. (The same code under another workflow, where the record is expected, is part of a PASS.) | Find out why the agent produced it, and undo it in the system of record if it should not stand. | yes |
| `effect_observed:stripe.refund` | policy | [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | A refund was issued with the cancellation; refunds are approved separately / A cash refund was issued as well as the credit / A cash refund was issued on an unpaid invoice. A record the contract forbids for this workflow was found in the window. (The same code under another workflow, where the record is expected, is part of a PASS.) | Find out why the agent produced it, and undo it in the system of record if it should not stand. | yes |
| `effect_observed:zendesk.escalation` | policy | [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | The case was escalated after the agent marked it resolved. A record the contract forbids for this workflow was found in the window. (The same code under another workflow, where the record is expected, is part of a PASS.) | Find out why the agent produced it, and undo it in the system of record if it should not stand. | yes |

## The action was outside what was approved

| Code | Lens | Workflows | What happened | What to do | In a fixture |
|---|---|---|---|---|---|
| `precondition_unmet:stripe.invoice_status` | policy | [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | The invoice was not paid when the credit was issued; an open invoice is adjusted instead / The invoice was not open when it was adjusted; a paid invoice takes a credit note that credits the customer. The latest state of the object before the action was not the state the contract requires, or no state was on record. | The agent acted on an object it should not have (already cancelled, already paid, not open). If no state was on record, the object is older than the connector's first sync reached. | yes |
| `precondition_unmet:stripe.subscription_status` | policy | [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription) | The subscription was not active when the agent cancelled it. The latest state of the object before the action was not the state the contract requires, or no state was on record. | The agent acted on an object it should not have (already cancelled, already paid, not open). If no state was on record, the object is older than the connector's first sync reached. | yes |
| `limit_exceeded:amount` | policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | The refund exceeds the amount an agent may approve / The credit exceeds the amount an agent may approve / The adjustment exceeds the amount an agent may approve. The amount the action carries is above the limit an agent may approve. | Route amounts above the limit to a person, or raise the limit in the pack's parameters. If the amount looks a hundred times too large, the tool sent cents: declare `units: {amount: minor}` on its rule. | yes |
| `aggregate_exceeded:stripe.credit_note.amount` | policy | [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | The agent's credits over 24 hours exceed the approved total / The agent's adjustments over 24 hours exceed the approved total. Each action may be within its own limit, but the total over the lookback is above the contract's maximum. | Look at the other actions of the same agent or on the same order in the last 24 hours. | yes |
| `aggregate_exceeded:stripe.refund.amount` | policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | Refunds on this order over 24 hours exceed the approved amount. Each action may be within its own limit, but the total over the lookback is above the contract's maximum. | Look at the other actions of the same agent or on the same order in the last 24 hours. | yes |
| `param_not_allowed:resolution_kind` | policy | [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | The resolution kind is not one the agent may apply. A parameter of the action is not one of the values the contract allows. | Send one of the allowed values, or add the value to the contract and save a new version. | yes |

## It was undone later

| Code | Lens | Workflows | What happened | What to do | In a fixture |
|---|---|---|---|---|---|
| `reversed:shopify.fulfillment_created` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | A shipment was created after the refund. A later record shows the action was undone after it had settled. | The verdict changed after the fact: A shipment was created after the refund | yes |
| `reversed:shopify.order_reopened` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | The order was reopened. A later record shows the action was undone after it had settled. | The verdict changed after the fact: The order was reopened | no |
| `reversed:stripe.credit_note_voided` | outcome and policy | [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | The credit note was voided. A later record shows the action was undone after it had settled. | The verdict changed after the fact: The credit note was voided | yes |
| `reversed:stripe.refund_failed` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order) | The refund failed or was reversed. A later record shows the action was undone after it had settled. | The verdict changed after the fact: The refund failed or was reversed | yes |
| `reversed:zendesk.reopen` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | The support case was reopened / The case was reopened. A later record shows the action was undone after it had settled. | The verdict changed after the fact: The support case was reopened / The case was reopened | yes |

## It could not be judged

| Code | Lens | Workflows | What happened | What to do | In a fixture |
|---|---|---|---|---|---|
| `param_missing:amount` | policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) | The contract requires this parameter because a check reads it, and the action does not carry it, so the check did not run. The policy lens is UNKNOWN where it would have been PASS; a failure another check found stays a failure. | Record the parameter with the action. If your tool has no such argument, record the action from your own code, where you can state it. | no |
| `param_missing:cancel_at_period_end` | policy | [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription) | The contract requires this parameter because a check reads it, and the action does not carry it, so the check did not run. The policy lens is UNKNOWN where it would have been PASS; a failure another check found stays a failure. | Record the parameter with the action. If your tool has no such argument, record the action from your own code, where you can state it. | no |
| `param_missing:resolution_kind` | policy | [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | The contract requires this parameter because a check reads it, and the action does not carry it, so the check did not run. The policy lens is UNKNOWN where it would have been PASS; a failure another check found stays a failure. | Record the parameter with the action. If your tool has no such argument, record the action from your own code, where you can state it. | no |
| `missing_fact_source` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | A source the contract cannot be judged without has never reported in this workspace. | Connect it (Stripe is required for every workflow but case resolution), or push its facts. | yes |
| `identity_unmatched` | outcome and policy | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) | No fact at all exists for the action's subject or anything linked to it. | The subject id the action carries is not the id the systems of record use. Check the id, and the links the workflow needs. | no |

## Codes of a PASS

An expected effect that was found is reported too, on both lenses, so a verdict always says what it rests on. Under
the workflows listed these codes need nothing done.

| Code | Expected under |
|---|---|
| `effect_observed:messaging.customer_notified` | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) |
| `effect_observed:shopify.order_cancelled` | [refund_order](/docs/packs/stripe-customer-operations/refund-order) |
| `effect_observed:stripe.credit_note` | [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [adjust_invoice](/docs/packs/stripe-customer-operations/adjust-invoice) |
| `effect_observed:stripe.refund` | [refund_order](/docs/packs/stripe-customer-operations/refund-order) |
| `effect_observed:stripe.subscription_canceled` | [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription) |
| `effect_observed:zendesk.status_change` | [refund_order](/docs/packs/stripe-customer-operations/refund-order), [cancel_subscription](/docs/packs/stripe-customer-operations/cancel-subscription), [issue_credit_note](/docs/packs/stripe-customer-operations/issue-credit-note), [resolve_customer_case](/docs/packs/stripe-customer-operations/resolve-customer-case) |

## Answers that are not verdicts

Some things a first integration meets are refusals of the API, not verdicts. They change nothing that was recorded.

| Answer | When | What to do |
|---|---|---|
| `401 invalid_session` | An API key was sent as `Authorization: Bearer`. | Send the key in `X-API-Key`. |
| `404 unknown_contract` on `POST /v1/actions` | The `contract_version` is not one the workspace has, or the pack is not installed. | Read the version from `GET /v1/packs/stripe_customer_operations/recorder-mapping`. |
| `409 contract_not_active` on `POST /v1/actions` | The `contract_version` is a draft nobody selected (what the install leaves) or an archived version; `details` names the status and `active_version`. | Select the installed contract (`POST /v1/contracts/{id}/select`, or the pack's Activate step), or record against `active_version`. |
| `409 conflict` on `POST /v1/actions` | The `action_id` is already recorded with another subject, contract or value of a parameter (another amount, customer or payment), or the first record did not carry a parameter a check reads and this one does, or the request time is after the first one's window. | It is a different action: give it its own id. The same action said again (a retry, a second tool for the same order) is not a conflict. |
| `403 insufficient_scope` on `POST /v1/facts` | The key is a recorder key. | Push with an evidence key. |
| `403 source_not_allowed` on `POST /v1/facts` | The evidence key is not bound to the source it pushed. | Create the key with that source in `fact_sources`. |
| `409 source_served_by_connector` on `POST /v1/facts` | A connector already serves that source (a push for `stripe` with Stripe connected). | Nothing to push: the connector's record is the evidence. |
| `unmapped_consequential_tools` in the pack's coverage | A tool listed as consequential, or reported through `observed-tools` and not read-only when first reported, has no rule in the recorder mapping. | Add a rule for it, or list it under `read_only_tools` in the mapping ([recorder setup](/docs/packs/stripe-customer-operations/recorder-and-opentelemetry)). |
