# order-good-standing

Paid (standard Exact-EVM rail, variable by state — `get-pricing` with `product: "good-standing"`). Orders a certificate of good standing (existence/status certificate) for an active managed entity from its state — the document banks, payment processors, and counterparties ask for. The asset state is unchanged.

## Input

| Field | Required | Notes |
|---|---|---|
| `entity` | yes | Handle of an entity you own, e.g. `"US-WY:daski-labs-llc"`. |
| `filingPlanId` | yes | Copy the current ID from detailed `get-pricing` for this product. |
| `filingAddresses` / `filingFiler` | per plan | Explicit public-address and filer choices from the plan requirements. |
| `filingProfileId` | per plan | Owner-scoped profile from `get-entity-status` when managed contact/official fields are required. |
| `assetId` | no | Immutable UUID — disambiguates re-formed names. |
| `formData` | no | Usually empty or minimal — the state contract from `get-pricing` says if anything is needed. |

## Example

```jsonc
{ "entity": "US-WY:daski-labs-llc" }
```

## Timing the order

Certificates are dated by the state, and counterparties commonly require one issued within the last 30–60 days — order close to when it is needed, not speculatively. If the entity has open attention items (RA renewal due, compliance filing due), clear those first: a state will not certify an entity that is delinquent on its filings. Each order is a fresh purchase — this skill is deliberately **not** idempotent; calling it twice buys two certificates.

## Behavior

- Re-screens the entity's stored parties before any supplier spend (a hold shows the neutral review message).
- Runs like any filing: `working` while the state issues the certificate (days, state-dependent — see `get-pricing` turnaround); progress via push + email.
- The certificate is stored under the entity's documents, so it stays available under `list-entity-documents` long after the expiring link below lapses.

## Result artifacts — `good_standing_details`, `good_standing_certificate`

```jsonc
{
  "entity": "US-WY:daski-labs-llc",
  "assetId": "5f0c2f6a-…",
  "documents": ["e3f4a5b6-…"]        // documentId for list/download
}
```

`good_standing_certificate` is the certificate PDF as a URL artifact (expiring link, ~15 minutes — re-fetch any time via `download-entity-document`). A completion email goes to the entity's `contactEmail`.

## Failure modes & refunds

- Not `active` (suspended, expired past usefulness, `ra_cancelled`, terminal): refused — a certificate cannot be ordered for an entity that is not in good order with its RA and filings. Check `get-entity-status` `attentionItems` for what to fix first.
- Unavailable, stale or revoked filing plans and ambiguous supplier evidence: paused for operator review; no automatic refund is promised.
- After the order is committed with the state: operator-resolved via support.

## Next step

- Done — the asset stays `active`, nothing about the entity changes.
- `download-entity-document` whenever you need the PDF again.

## Filing plan and addresses

Before buying, obtain the current `filingPlanId` from detailed `get-pricing`
and pass it with the request. Include explicit `filingAddresses` and
`filingFiler` choices when the plan requires them. Do not repeat managed
address, filer, officials or registered-agent fields in `formData`.
When `filerRequirements.profileRequired` is true, also pass the owner-scoped
`filingProfileId` and filer option returned by `get-entity-status`. The request
pins that profile's roster. Missing historical evidence requires support review.
The selected method is retained across retries; an unavailable or revoked plan
pauses work instead of silently switching methods.