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

# Corpus Profiles

**Open this area:** In the CORTEX menu, select **Assurance & governance → Preservation & archive**.

Build a jurisdiction-specific draft from exact active source requirements and record its coverage and change impact.

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

## Expected result

An independently reviewable draft pins the selected requirements and retains the actual scope and unresolved inputs.

## Before you start

* Select the intended workspace with current corpus read and management permissions and sufficient handling.
* Register source publications and active applicability requirements first. Each selected family needs at least one exact requirement for the chosen jurisdiction or the United Kingdom.
* Gather the policy baseline, rights review, effective dates and any outstanding organisational inputs. A second current corpus manager is needed for approval.

## What to do

{% stepper %}
{% step %}

## Define scope

On **Profile scope**, enter the stable key, title, exact UK jurisdiction, one or more families, purpose and effective dates.

The page marks required fields and explains a policing-family jurisdiction mismatch immediately.
{% endstep %}

{% step %}

## Choose catalogues if needed

**Catalogues** is optional for a draft.

If selected, choose supported editions and complete every controlled term and condition. The step shows validation before you move on; a catalogue cannot create source provenance.
{% endstep %}

{% step %}

## Pin requirement evidence

On **Requirement evidence**, select 1–32 active exact source requirement revisions, with at least one for each family.

Use a stable control key and record any overlap resolution supported by the responsible interpretation.

The prerequisite panel links to the source register if the required records do not yet exist.
{% endstep %}

{% step %}

## Review and save

Record the source coverage and rights review, outstanding inputs, change and adoption impact, and reason.

Step colors and missing-input lists show what remains.

Saving retains a Draft; another current corpus manager must independently approve it before adoption.
{% endstep %}
{% endstepper %}

## Check the result

* Does each family have an active applicable requirement?
* Does each source actually cover the jurisdiction?
* Are handling, rights and outstanding policy inputs explicit?
* Has a different manager independently reviewed this exact draft?

## If you get stuck

<details>

<summary>Why can I not save a draft?</summary>

Choose a jurisdiction and family, enter the required scope and review text, and pin at least one active applicable requirement for each family. The current step lists missing fields. Optional catalogues can be left disabled.

</details>

<details>

<summary>Why can I save but not approve?</summary>

Approval needs a different current corpus manager, current source and requirement review, resolved overlaps, and no outstanding organisational or policy inputs.

</details>

<details>

<summary>What happens after a conflict or access loss?</summary>

A normal validation error or conflict keeps the in-memory draft for correction or comparison. Confirmed loss of access clears sensitive page content; ask the responsible manager to review access before re-entering it.

</details>

## Responsibility and limits

* Saving rechecks selected requirement revisions, handling and current access. Approval and adoption also recheck current source status and review. A stale or inaccessible source can stop those later actions.
* An amendment retains earlier revisions and needs a fresh change assessment and approval. Existing adopted records keep their original exact profile and source context.

{% hint style="info" %}
**Reference and scope:** A profile records reviewed organisational applicability. It cannot supply missing source, legal or rights decisions.
{% endhint %}

## Related workflows

* [Read guidance for the exact retained UK profile](broken://pages/c5895cc2858a609d80981bd8bbaa2d3b1f519a29)
* [Approve catalogues and find controlled terminology](broken://pages/65d2d11d104bb4f5129171cdcd948324805f1029)
* [Record authority before new source use](file:///7397340/collection/source-authority.md)
* [Preserve an exact revision and manage holds](broken://pages/0185ca5a2331760fb4c59665b8dde7f4d80e0fc6)
* [Manage accounts, grants and workspace membership](broken://pages/99c8701bc497eefb32769b668198b1f9f5fc6a93)