# file-amendment

Paid (standard Exact-EVM rail, variable — `get-pricing` with `product: "amendment"`). Files a legal-name, principal-address, or mailing-address amendment for an active managed entity under the state's `formData` contract.

## Input

| Field | Required | Notes |
|---|---|---|
| `entity` | yes | Handle of an entity you own, e.g. `"US-WY:daski-labs-llc"`. |
| `formData` | yes | The state's amendment contract from `get-pricing`. The supplier form is **free-form prompt-style**: `what_are_you_amending_`, `provide_specific_details_for_amendment_`, and `enter_information_if_changing_company_name_` for name changes. Keys are supplier-verbatim. |
| `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. |

## Name changes

- Every legal-name change, for any entity type, puts the new legal name in `enter_information_if_changing_company_name_`. A rename described only in `what_are_you_amending_` (such as `"Company name"`) or in `provide_specific_details_for_amendment_` (such as "rename the company to …") is refused at the quote, because the entity's handle and stored legal name would not follow the state's record. An address change may still mention a name, or say the name is not changing ("no name change").
- `enter_information_if_changing_company_name_` takes only the full new legal name: a word of its own and its entity designator at the end (`"Daski Systems LLC"`, `"Acme, Inc."`, `"Acme & Co."`). Give the name alone. A value with a label after a colon, an arrow or a spaced dash, one that starts with "Rename to" or "Change to", or one that adds words to the current name is refused (`"New name: Daski Systems LLC"`, `"Rename to Daski Systems LLC"`, `"Daski Labs LLC -> Daski Systems LLC"`). Leave the field out when the name is not changing.
- The new name counts only when `what_are_you_amending_` or `provide_specific_details_for_amendment_` also describes the rename, for example `what_are_you_amending_: "Company name"`. A name in the field of a request that describes only an address change is refused, not filed as a rename.
- A value there names no new name when it is:
  - a placeholder: `"N/A"`, `"None"`, `"No change"`, `"Not applicable"`, `"-"`;
  - wording that the name is not changing: `"Name unchanged"`, `"Name remains Daski Labs LLC"`;
  - the current name alone, labelled or with such a note: `"Name: Daski Labs LLC"`, `"Daski Labs LLC (current)"`;
  - a note without a designator that names nothing or only an address: `"See details"`, `"Address change only"`, `"PO Box 12"`, `"New address: 9 Oak Ave"`, `"c/o Jane Doe"`.

  The amendment is then filed without a rename, the handle and stored legal name stay as they are, and the field reaches the supplier as written. If the free text still describes a rename, the quote is refused until the field gives the new name.
- Any other value is refused at the quote (`input-required` at execution) and never filed as a rename. Examples: `"Pending"`, `"This LLC"`, or a name without its designator such as `"Northwind Holdings"`.
- These rules apply the same way at the quote, at execution and after a correction. A correction without a rename clears any rename the order queued earlier.
- The post-amendment handle is pre-checked against live entities **before any spend**. A collision comes back as `input-required`: `A live entity already holds 'US-WY:daski-systems-llc'. Choose a distinguishable name.`
- On completion the `entity` handle changes — you are told the new handle in the artifact **and by email**. The immutable `assetId` never changes; when scripting across a rename, address by `assetId`.
- An order validated before these rules may have queued a placeholder (`"N/A"`, `"None"`), a name without its designator, or one with no word of its own as its new name. It completes without the rename: the handle and stored legal name stay, `identifierChanged` is `false`, and our operations team checks the state's filed document.
- A Wyoming `DAO LLC` keeps both designators: the new name must include `"DAO"` or `"LAO"` and an LLC designator such as `"LLC"`, or the quote is refused.

## Supported scope

Only entity legal-name, principal-address, and mailing-address changes are accepted. `what_are_you_amending_` must name the subject, for example `"Company name"`, `"Principal address"`, `"Mailing address"`, `"Principal office"`, `"Office relocation"`, `"Headquarters"` or `"Principal place of business"`. `"Relocation"`, `"Move"` or `"Change of location"` alone counts when the details name the address or office. `"Other"`, a bare `"Office"` and any registered-office subject are refused, as are details about the registered office or the state of organization under an office or move subject. Official, ownership, registered-agent, jurisdiction-of-organization, and other party changes are rejected before supplier spend because the free-text supplier form cannot carry a structured, screenable roster. The check reads the free text without the entity's current and new legal names, so "Summit Partners LLC moves its principal office to Casper." is an address change. Any party word still counts, even in a statement that the parties are not changing: leave out wording such as "members unchanged" or "no change to the registered agent", which is refused. `"N/A"`, `"None"` or `"No change"` alone in `enter_information_if_changing_state_or_country_of_organization_` counts as no jurisdiction change. Smart-contract and public-identifier amendments, such as a DAO's contract address, wallet or `0x…` identifier, are also refused at the quote, as is a request worded as converting the entity into a DAO (for example "become a DAO" or a new name such as "Acme DAO LLC"); file those directly with the state or a qualified filing service.

## Example

```jsonc
{
  "entity": "US-WY:daski-labs-llc",
  "filingPlanId": "copy-current-plan-uuid",
  "formData": {
    "what_are_you_amending_": "Company name",
    "enter_information_if_changing_company_name_": "Daski Systems LLC",
    "provide_specific_details_for_amendment_": "Change the legal name from Daski Labs LLC to Daski Systems LLC."
  }
}
```

## Result artifacts — `amendment_details`, `amendment_document`

```jsonc
{
  "entity": "US-WY:daski-systems-llc",     // the NEW handle after a name change
  "assetId": "5f0c2f6a-…",                  // unchanged, always safe to address by
  "identifierChanged": true,
  "previousEntity": "US-WY:daski-labs-llc", // present only when the handle changed
  "documents": ["b5c6d7e8-…"]
}
```

`amendment_document` is the accepted filing PDF as a URL artifact (expiring link). A completion email — naming the new handle when it changed — goes to the entity's `contactEmail`.

## Failure modes & refunds

- Correctable input problems (unsupported amendment subject, a rename without its new name in `enter_information_if_changing_company_name_`, a value there that is neither a legal name nor a placeholder, handle collision, `formData` violations, state rejections): `input-required` — fix via task input, no refund needed.
- Unavailable, stale or revoked filing plans and ambiguous supplier evidence: paused for operator review; no automatic refund is promised.
- After the filing is committed with the state: operator-resolved via support.

## Next step

- `get-entity-status` (by `assetId` if you renamed) to confirm the new legal name and handle.
- Done. The asset stays `active`.

## 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.