> 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/products/domestic-packages.md).

# Domestic Packages

**Open this area:** In the CORTEX menu, select **Release & sharing → UK recipient packages**.

Bind a reviewed derivative to named UK-party recipients, current processing permission, and separate protected-source release decisions.

**Who uses this:** Author, Reviewer, Administrator\
**Open in CORTEX:** `/releases/domestic`\
**In-app guide:** `/help?topic=domestic-packages`

**Expected result:** An independent reviewer approves the exact minimal ZIP bytes while private lineage remains accessible only through its original permissions.

## Before you start

* Obtain an effective marking-approved derivative and normal access to its exact sources and UK agreement.
* Obtain explicit package permissions, actual recipient authority for the approved UK party, and verified UK destination. Recipient eligibility grants no private source access.
* Obtain an approved dissemination processing purpose covering the exact derivative and audience. Real legal and organisational evidence must be supplied by responsible owners.

## What to do

{% stepper %}
{% step %}

## Create the exact request

From an approved derivative, choose **Prepare UK recipient package**, or open **Product → UK recipient packages**.

The page shows UK package write, marking-approved derivative, named UK-party recipient, and approved Dissemination processing prerequisites, with links to prepare missing records.

Select the exact derivative, then complete the three validated steps:

1. Recipients and actual authority
2. Approved processing
3. Final review and reason

Missing inputs and red or green step status update before **Continue**.

Select one to twenty distinct current recipients through the shared exact-email lookup and record 10–1,000 characters of actual UK-party authority and destination evidence for each.

Inspect the assessed resources, obtain an approved processing activity covering the exact derivative and audience, explain the request in 10–2,000 characters, and save.

Current eligibility and scope are checked again by the service.
{% endstep %}

{% step %}

## Approve each protected-source release use

If protected sources are present, give the request ID and original ordinary use reference to the authorised custodian.

In the same protected case, they propose **Domestic release**, load this request's actual audience and method, and obtain independent cumulative-exposure review.

The package editor verifies each new use ID and saves the related bindings.

Private case identifiers and identity records are not copied into the package.
{% endstep %}

{% step %}

## Prepare recipient bytes

Record a reason and prepare the ZIP.

Current agreement, derivative, source permissions, recipients, processing purpose, and every protected-source release decision are checked.

Inspect the narrative, citations, metadata, handling instructions, and permitted-use conditions, or download the exact ZIP for internal review.
{% endstep %}

{% step %}

## Approve independently

An authorised reviewer who contributed neither source/derivative content nor this request/preparation approves the exact prepared ZIP.

Approval checks current scope again and keeps the original prepared bytes.

Preparation and approval do not send a package or acknowledge receipt.
{% endstep %}

{% step %}

## Handle changes

An amendment clears current preparation, approval, and use bindings but retains earlier decisions and bytes.

A changed derivative requires a new request.

On conflict, refresh and compare; entered notes survive.

Loss of access clears private page content and notes.
{% endstep %}
{% endstepper %}

## Check the result

* Does every recipient actually represent the approved UK party at the verified UK destination?
* Does the processing decision cover both displayed resources?
* Does each protected-source decision belong to the original case and this exact audience?
* Has the independent reviewer inspected the exact recipient ZIP?

## If you get stuck

<details>

<summary>Why did preparation or approval fail?</summary>

Check the exact current derivative and agreement, independent reviewer, approved processing purpose, current recipient access, and every separate related use decision.

Changed or stopped approvals and expired permissions fail closed; refresh and reassess rather than bypassing source controls.

</details>

<details>

<summary>Can a source-assessment permit be reused for this package?</summary>

No. A separate approved Domestic release use must belong to the same protected case and bind this exact request audience, method, and content.

Changing recipients or authority evidence requires new review.

</details>

<details>

<summary>Does amendment erase an earlier ZIP?</summary>

No. Previous bytes and decisions remain retained.

This page does not recall files, transfer material, or record recipient acknowledgement.

</details>

## Responsibility and limits

* Internal review continues to require normal lineage access. The ZIP has only `recipient.json`, `recipient.txt`, and `manifest.json`; private source, case, organisation, and workspace identifiers, risk notes, recipient lists, and authority evidence are excluded.
* Requests retain up to 32 revisions and eight MiB; each package is bounded to 512 KiB. Full history is never discarded to make room.
* Use the connected delivery workflow to publish exact approved bytes to named recipients, record explicit receipt, and issue correction/withdrawal notices. Preparation or a download attempt is never proof of receipt.

**Reference and scope:** F16-R05 and F17-R02/R05: protected lineage is retained internally; an assessment-use permit cannot authorise a different disclosure audience or method.

## Related workflows

* [Receive UK packages and act on notices](broken://pages/4e971212ce4cca41bd50cd3746392614ca983e84)
* [Review a derivative for UK sharing](broken://pages/0f2353fa172e1221893de98a680eecbabeae16c1)
* [Prepare a UK sharing agreement](broken://pages/d01ab7701685aeb8c20c3f2edef3d644081ce5d4)
* [Protect source identity and review each use](file:///7397340/collection/source-protection.md)
* [Record processing purposes and privacy applicability](file:///7397340/assurance/processing-activities.md)
* [Review, approve and publish an exact internal release](broken://pages/470978e3be0758fbc43448d1d7b8fc918bd9675f)
* [Manage accounts, grants and workspace membership](file:///7397340/assurance/access.md)