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

# Send a correction

> Send one correction, one piece of public evidence, or one missing feature into your own vendor subtree. Names in, never ids. Rationale required.

One thing at a time. Three kinds, in rising order of effort and falling order of frequency.

## The three kinds

| Kind              | When                                               | What it needs                                                                                             |
| ----------------- | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| `evidence`        | A public page proves a feature or a capability.    | `evidenceUrl`, plus the target: `product` + `feature`, or `product` + `group` + `capability`.             |
| `correction`      | A fact Sovrnti holds is wrong.                     | The target (omit `product` for the vendor), the `field`, and the `claimedValue`.                          |
| `missing-feature` | The product does something Sovrnti has not mapped. | `product`, `group`, `capability`, then `name`, `description`, `availabilityStatus`, and optionally `sku`. |

Correctable fields, per target:

| Target  | Fields                                                         |
| ------- | -------------------------------------------------------------- |
| vendor  | `name`, `aliases`, `foundedDate`, `stockTicker`, `hqGeography` |
| product | `name`, `aliases`, `description`                               |
| feature | `name`, `description`, `availabilityStatus`                    |

`availabilityStatus` is one of GA, Beta, Alpha, In development, Planned.

**`rationale` is required on all three kinds**, minimum 20 characters. `supersedes` is optional on all three.

## What you get

```json theme={null}
{
	"id": "cmt0a1b2c3d4e5f6g7h8",
	"status": "received",
	"targetLabel": "Feature",
	"targetKey": "feat-workspace-cmek",
	"targetName": "Customer-managed encryption keys"
}
```

Keep the `id`. It is what `supersedes` takes, and what [Your submissions](/mcp/tools/sovrnti_builder_list_submissions) reports on.

## What makes a submission worth reading

A bare fact is worth little. Sovrnti reads the rationale: what a sovereignty buyer does differently if the fact is true.

"Customer-held keys are GA on Business Standard" is a fact. "A French bank can keep mail on Workspace without a key-escrow exception, which removes the main objection in their risk register" is a rationale. Write the second.

Public evidence beats assertion. A URL is optional on corrections and missing features, but a submission with no public page lands as a vendor claim and is weighed as one.

## Submissions are immutable

To change one, send another with `supersedes` set to the old id. The original stays on the record.

## How to use it

Ask your assistant:

```text theme={null}
Our data residency page proves EU-only storage. Send it as evidence on that feature.
```

## Troubleshooting

* `builder-identity-required` — your account has no active builder identity. Claim access at [sovrnti.io/builders](https://sovrnti.io/builders).
* `insufficient-scope` — revoke the connection and reconnect; the authorization flow will re-request `Builder.Write.Self`.
* `builder-target-out-of-scope` — the name you gave resolves outside your own vendor.
* `builder-requires-user-token` — you connected with a machine token. Builder tools are personal (R-04); reconnect as yourself.
* `builder-target-ambiguous` — the name matched more than one thing. The error lists the candidates; pick one and resend.
* `builder-target-needs-product` — name a `product` before a `group` or a `feature`.
* `builder-target-needs-group` — name a `group` before a `capability`.
* `builder-field-not-correctable` — that field is not in the table above. Groups and capabilities have no correctable fields. A correction there is a taxonomy argument. Send it on the product with `field: "description"`, and it is read as a flag.

## See also

* [Review your profile](/mcp/tools/sovrnti_builder_review_profile) — call this first.
* [Your submissions](/mcp/tools/sovrnti_builder_list_submissions) — what happened to it.
* [For builders](/builders/overview) — what the four statuses mean.