> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/workflow-guides/assurance/corpus-sources.md).

# Corpus Sources

**Open this area:** In the CORTEX menu, select **Assurance & governance → UK source register**.

Record an exact source identity, edition, jurisdiction and rights position before deriving requirements.

**Who uses this:** Author, Reviewer, Administrator.\
**Open in CORTEX:** `/governance/sources`.\
**In-app guide:** `/help?topic=corpus-sources`.

**Expected result:** A retained source metadata revision is available for explicit requirement and applicability review.

## Before you start

* Select the intended workspace and hold current corpus read and management permissions with sufficient handling.
* Have the actual source title, issuing authority, edition, locator, UK jurisdiction and rights position. No prior register record is needed.

## What to do

{% stepper %}
{% step %}

### Identify the source

Enter a unique stable key, title, authority and edition. Record an unknown edition explicitly. If the publication date is unknown, explain that in the date note.
{% endstep %}

{% step %}

### Record scope and rights

Enter an authorised locator, explicit usage rights or unresolved status, source force and status, and one or more UK jurisdictions. Superseded sources need a replacement reference.
{% endstep %}

{% step %}

### Review and save

Record when the metadata was collected, the revision reason and new record handling. The wizard shows required fields and step status before saving.
{% endstep %}
{% endstepper %}

## Check the result

* Are title, authority, edition and locator tied to the exact source?
* Does the jurisdiction match the source rather than the intended future profile?
* Is rights review explicit instead of inferred from a status label?

## If you get stuck

<details>

<summary>Can I save when the publication date is unknown?</summary>

Yes. Leave the date empty and provide an explicit explanation. An unknown edition also needs explicit text.

</details>

<details>

<summary>Does registration let me create a profile?</summary>

No. Register exact active requirements with reviewed applicability for each selected family first; the profile editor shows this prerequisite.

</details>

<details>

<summary>What happens to an older edition?</summary>

A metadata change retains the earlier revision. Exact requirement and profile pins never move automatically.

</details>

## Responsibility and limits

* The service rechecks current access and handling and retains each metadata revision. A conflict leaves the in-memory entry for correction.
* Next, record atomic requirements with exact source revision and applicability. Active requirements and an independently reviewed profile are separate decisions.

{% hint style="info" %}
**Reference and scope:** A register entry does not import a source body, grant content rights or approve a profile.
{% endhint %}

## Related workflows

* [Propose a UK applicability profile](broken://pages/9dda90759042096804890ee158ebd0fa7da34d64)
* [Review guidance after a source or profile change](broken://pages/8e0091ac19a47c02acdc7e9b9a36fafd3917dc3d)
* [Manage accounts, grants and workspace membership](broken://pages/99c8701bc497eefb32769b668198b1f9f5fc6a93)