> 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/sources-and-evidence/map/map-packages.md).

# Map Packages

**Open this area:** In the CORTEX menu, select **Sources & evidence → Map & spatial context**.

Inspect signed package approvals and provider reviews, then import, verify, activate, or retire retained MBTiles custody.

**Who uses this:** Administrator.\
**Open in CORTEX:** `/map/packages`.\
**In-app guide:** `/help?topic=map-packages`.

**Expected result:** The intended exact package is retained and explicitly selected with current integrity, expiry, coverage, and licence context visible.

## Before you start

* Have the node-wide `mapping.packages.manage` grant; a selected workspace and `mapping.import` are separate analyst concerns.
* Confirm the package ID is present in signed deployment configuration and the approved bytes have been placed in the protected intake directory by the node operator.
* Read the configured provider review, licence, expiry, geographic coverage, and storage requirements.

## What to do

{% stepper %}
{% step %}

## Inspect approved configuration

Open Map packages from the workspace map.

Confirm environment, provider reviews, and the safe approved package summary. Intake paths, filenames, and credentials are never displayed or supplied by this page.
{% endstep %}

{% step %}

## Import the exact approved ID

Choose an ID from **Approved package** and select **Import approved bytes**.

CORTEX copies from configured intake custody and verifies exact size, SHA-256, SQLite integrity, MBTiles metadata, bounds, zoom, and tile limits before retaining it.
{% endstep %}

{% step %}

## Verify retained custody

Select **Verify retained packages** after restore, storage maintenance, or suspected corruption.

Review every state and failure reason. Verification may remove an invalid active selection; it never downloads, replaces, or deletes bytes.
{% endstep %}

{% step %}

## Activate deliberately

Choose a retained **Imported** or **Retired** package and select **Activate verified package**.

Activation verifies retained packages again and replaces only the active package for the same source.
{% endstep %}

{% step %}

## Retire without deletion

Choose the package and select **Retire package**.

Confirm **Retired** state. The package remains in custody and history until an external approved retention procedure governs its bytes.
{% endstep %}

{% step %}

## Confirm user-visible behavior

Return to the workspace map, read the source status and attribution, and test expected in-coverage and missing tiles.

Missing coverage or failed integrity must not cause an online fallback.
{% endstep %}
{% endstepper %}

## Check the result

* Is the package ID and source the signed approved choice?
* Do size, coverage, zoom, publication, and expiry match the review?
* Did verification complete before activation?
* Is the expected package active for only its source?

## If you get stuck

<details>

<summary>Why is the package absent from the selector?</summary>

Only IDs from current signed deployment configuration are shown. Ask the node operator to approve the package and deploy that configuration; do not enter a path, URL, or substitute ID.

</details>

<details>

<summary>Why did import fail?</summary>

Check that the exact approved bytes exist in the configured protected intake directory and match the approved size, SHA-256, MBTiles structure, bounds, and zoom. Correct custody or configuration outside the UI, then retry the same ID.

</details>

<details>

<summary>Why did verification clear an active package?</summary>

The retained bytes, approval, or expiry no longer passed validation. Keep the local outline in use, investigate the reported state, and activate only after a current exact package verifies.

</details>

<details>

<summary>Does retirement delete the package?</summary>

No. Retirement removes it from active selection and retains its bytes and inventory history. Follow the approved external retention procedure for any later disposal.

</details>

## Responsibility and limits

* The package custodian controls exact approved local assets and retained selection; this grant does not permit analysts to import workspace evidence.
* The operator maintains separate environment custody, backups, protected intake, and licence evidence. CORTEX does not fetch or delete package bytes automatically.

**Reference and scope:** Operational assurance guidance for the CORTEX node. Package approval, licensing, and custody remain accountable operator responsibilities.

**Related workflows:** [Explore and retain governed geographic evidence](file:///7397340/analyse/map.md); [Work through connection and deployment limits](broken://pages/e2892068271c3c1f3c4471ca5a8f532a8174ba43); [Manage accounts, grants and workspace membership](broken://pages/99c8701bc497eefb32769b668198b1f9f5fc6a93).