> 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/memory.md).

# Memory

**Open this area:** In the CORTEX menu, select **Sources & evidence → Evidence memory**.

Search authorised material, inspect its provenance and choose a precise retained extraction rather than an unattributed quotation.

**Who uses this:** Analyst, Collector, Author, Reviewer.\
**Open in CORTEX:** `/memory`.\
**In-app guide:** `/help?topic=memory`.

**Expected result:** You can explain which original, derivative and passage supports the next analytical or authoring action.

## Before you start

* Have current Memory access within the selected workspace and full handling of the material.
* Identify a useful literal term, requirement, source or processing state for the search.
* New citations require Ready material and a current scan when required; original download also requires its own permission. Historical pins remain readable under current access.

## What to do

{% stepper %}
{% step %}

## Refine the authorised search

In Evidence memory, enter literal keywords and select state, requirement or source filters. Use Find filter options to obtain named context, then Search.

Clear all filters removes any requirement or source from the route and requests the first unfiltered page of currently accessible material. Empty guidance and the exact count describe the last confirmed query; Acquire material appears only when the same successful read confirms current upload, Direction and Source access.

The pager appears only beyond one result page and states the exact authorised range. Editing filters leaves the current results unchanged until Search; Previous and Next use the last applied filters.

A temporary failure keeps the last confirmed material, filters and page for retry. A route scope change or loss of Memory, Direction or Source access clears protected rows, context choices and the acquisition action.
{% endstep %}

{% step %}

## Inspect provenance

Open the material and confirm acquisition notes/time, source and requirement versions, original filename, length and SHA-256. Examine the actual processing and scan state before deciding what the record supports.
{% endstep %}

{% step %}

## Choose the exact extraction

Select the retained derivative and relevant segment. Read its locator, warnings and surrounding text. Older extractions remain available so an existing citation can be reconstructed even after reprocessing.
{% endstep %}

{% step %}

## Create a citation in its workflow

In an RFI, Synapse, Analyse or Product evidence picker, find the material, choose the extraction and segment, select the passage bounds and resolve the preview.

Refining the bounded 25-result search keeps an exact selection and preview only after a fresh authorised read confirms the same Ready material, requirement, source, handling, original and extraction. A changed record, denied or failed read, or requirement change clears the selection and dependent preview.

Confirm the server-derived text before adding it; the final save rechecks access and provenance.
{% endstep %}

{% step %}

## Retrieve the original only when needed

If Download preserved original is available, supply the reason and use that control. Treat the downloaded bytes under their marking.

Preparation is audited and advances the record version; refresh before a subsequent mutation.
{% endstep %}
{% endstepper %}

## Check the result

* Am I looking at the intended original and exact derivative?
* Does the selected passage preserve necessary context?
* Have processing warnings and source limitations been considered?
* Is the citation being resolved through the evidence picker?

## If you get stuck

<details>

<summary>Why did Evidence memory keep the earlier page?</summary>

A temporary search, paging or filter-option failure did not confirm a replacement view. The warning identifies the last confirmed authorised material, filters and exact page.

Retry Search, Find filter options or the same page control; browsing changes no retained record. If the requirement or source route changes, or current Memory, Direction or Source access is lost, CORTEX clears protected rows, named context and the acquisition action before retrying the new scope.

</details>

<details>

<summary>Why does a keyword search not find an older passage?</summary>

Memory searches current metadata and the latest extracted text with literal matching. Refine the filters or open the known material and select its retained older derivative; this is not semantic search over every historical passage.

</details>

<details>

<summary>Why is known current material absent from a literal search?</summary>

First clear or refine the state, requirement and source filters and confirm you still have current workspace and handling access. Do not upload or reprocess the material merely to make it searchable.

Record the affected material and workspace through the protected support route and ask the node operator to run the stopped-node search-projection integrity inspection; never place protected titles, passages or search terms in ordinary logs.

</details>

<details>

<summary>Why can I read an old citation but not save it in a new edit?</summary>

Existing retained pins can remain readable during later processing. A new save resolves its selections again and may require Ready material; wait for the stored outcome and refresh instead of replacing the exact reference with pasted text.

</details>

<details>

<summary>Why did the evidence picker keep or clear my selection after Search?</summary>

A refined search can omit the selected item from its first 25 matches. CORTEX keeps it separately only when a final current read confirms the same authorised Ready material and exact extraction.

It clears the selection and any dependent quotation preview when the record, source, original or extraction changed, the requirement changed, access was denied or the search failed. Review and select the current result again deliberately; do not treat a retained picker selection as a source-quality judgement.

</details>

<details>

<summary>Why is original download unavailable when extracted text is visible?</summary>

Original retrieval has its own permission, scan and processing-state rules. Check those states and ask the responsible operator about policy; permitted plain-text history is not permission to retrieve quarantined bytes.

</details>

## Responsibility and limits

* Assess meaning, reliability and context separately from hash integrity; a hash does not corroborate an observation.
* Handle downloaded originals under organisational policy. Later access revocation cannot recall a file already obtained.

**Reference and scope:** Implementation guidance supporting evaluation and processing in JDP 2-00 (4th ed.), 3.35–3.40. Exact passage selection supplies traceability, not an independent truth judgement.

## Related workflows

* [Preserve an original and review processing](/workflow-guides/collection/ingest.md)
* [Interpret, translate and cite exact evidence passages](/sources-and-evidence/interpretation.md)
* [Assess evidence quality and retain defect actions](/workflow-guides/analyse/evidence-quality.md)
* [Develop and independently review an assessment](/workflow-guides/analyse/analysis.md)
* [Author an intelligence Product and inspect its exports](/workflow-guides/products/product-drafts.md)