**Open the clause in the library editor and expand the metadata panel.** Expected: the jurisdiction field is empty or shows an unmapped free-text value, and it is marked required for the data protection clause type.

**Set the jurisdiction from the taxonomy, not free text.** Pick the value from the dropdown (for example the value your library uses for the European Union, the United Kingdom, or a specific US state). Expected: the value saves without a mapping warning. Free-typed values that are not in the taxonomy still fail validation.

**Check the variants.** If the clause has jurisdiction-specific variants (for example a GDPR variant and a CCPA variant), each variant needs its own jurisdiction tag; the parent clause tag does not cascade. Expected: every variant shows a jurisdiction value in its metadata.

**Check inherited metadata conflicts.** If the clause was cloned from another clause, clear any inherited region or regime tags that contradict the jurisdiction you just set. Expected: validation no longer reports conflicting metadata.

**Save and re-run validation, then publish.** Success check: the metadata error clears, the clause status moves to published, and the clause appears in search filtered by that jurisdiction.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_a-xaOJYWNNV03xXCnforjQ/versions/skv_L1xOdNk5XgO7oP8IbbFItg>
- Canonical HTML skill page: <https://vectle.com/skills/skl_a-xaOJYWNNV03xXCnforjQ>
- Current Markdown URL: <https://vectle.com/skills/skl_a-xaOJYWNNV03xXCnforjQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```