> 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-requirements.md).

# Corpus Requirements

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

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

Pin the exact source revision, record one software requirement, then decide jurisdictional applicability and traceability.

**Expected result:** A retained requirement revision is explicit about source, decision, owner and verification targets; Active entries can support a profile.

## Before you start

* Select a registered source revision in the intended workspace with corpus read and management permissions.
* Citation use of the selected exact revision must be allowed. The prerequisite panel checks it and links to source and rights review when needed.

## What to do

{% stepper %}
{% step %}

## Pin source and statement

Enter a unique stable key, choose an exact retained source revision, write one atomic software requirement and cite its source section or locator.
{% endstep %}

{% step %}

## Decide applicability

Choose a UK jurisdiction, record the decision scope and choose Pending, Applicable or Not applicable.

An Applicable or Not applicable decision needs a reason; Pending may remain Draft.
{% endstep %}

{% step %}

## Trace and save

Choose Draft, Active or Withdrawn.

Active needs a reviewed applicability decision, at least one software reference and at least one verification target. Give a revision reason; taking ownership is a separate choice on revision.
{% endstep %}
{% endstepper %}

## Check the result

* Does the exact source section support one atomic statement?
* Is the applicability decision within the source jurisdiction and backed by a reason?
* Does each Active reference name a target without claiming a passing result?

## If you get stuck

<details>

<summary>Can I save a partial requirement?</summary>

Yes. Draft allows Pending applicability and no software or verification targets. The key, statement, source locator, jurisdiction, scope and reason are still required.

</details>

<details>

<summary>Why can I not activate it?</summary>

Choose Applicable or Not applicable with a rationale, add at least one software reference and verification target, and confirm citation rights for the exact source revision.

</details>

<details>

<summary>What happens after a source revision?</summary>

Earlier requirement and profile pins remain exact. Revise the requirement deliberately to cite a different retained source revision; current access and rights are rechecked.

</details>

## Responsibility and limits

* The service rechecks citation rights, source revision, handling and current actor at save. It retains earlier requirement revisions and source pins.
* Only an Active requirement with explicit applicability can support a proposed profile; profile approval and adoption remain separate.

{% hint style="info" %}
**Reference and scope:** A register status does not establish source-body rights, legal compliance or independent profile approval.
{% endhint %}

## Related workflows

* [Register UK source metadata](broken://pages/a7659e00bc5eb65830f0fbc515162a2de9935324)
* [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)