> 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/analyse/evidence-corrections.md).

# Evidence Corrections

**Open this area:** In the CORTEX menu, select **Intelligence cycle → Analyse**.

Inspect later quality and interpretation events affecting exact analytical or product citations, and retain a deliberate human response.

**Who uses this:** Analyst, Reviewer, Author\
**Open in CORTEX:** `/analyse`\
**In-app guide:** `/help?topic=evidence-corrections`

**Expected result:** An attributable response and next action are retained against the affected content revision; originals and released artifacts remain unchanged.

## Before you start

* Use current access to the Analysis or Product, its exact cited material and annotation history.
* Recording a response requires the owning Analysis or Product write permission. An analysis in peer review must first receive a changes-requested outcome.
* A later interpretation event can be a proposal or review. Inspect its actual review outcome; the notice does not approve the proposed wording.

## What to do

{% stepper %}
{% step %}

## Select the exact revision

Open the Analysis or Product and select its retained content revision.

Evidence corrections affecting revision identifies visible later quality events and changes after an explicitly cited interpretation revision.
{% endstep %}

{% step %}

## Inspect the correction

Expand the correction and follow **Inspect the retained annotation history**.

Read the original, new event, author, limitations and review outcome. Linked Analysis uses its original citation time even when the product was created later.

An open disputed claim also appears for later citations that overlap its exact passage. Inspect its qualification, fact/opinion assessment, reviewed subject-category scheme and profile before deciding the response.
{% endstep %}

{% step %}

## Record a human response

Choose the outstanding correction, explain its effect on the conclusion or product, and record the next action with retained references.

**Retain correction response** appends an attributed response to this exact content revision.
{% endstep %}

{% step %}

## Carry out the follow-up

Use normal authoring, independent review and release/correction processes for any amendment.

An analytical response requests changes; a product response never edits its content or a released package. Later corrections create separate review work.
{% endstep %}
{% endstepper %}

## Check the result

* Was the original passage preserved?
* Have you inspected the correction's actual review outcome?
* Does your assessment explain what changes and what remains uncertain?
* Is the next action practical and traceable?
* Have affected retained/released products received their own deliberate review?

## If you get stuck

<details>

<summary>What happens after a conflict?</summary>

The response draft stays on screen. Inspect or copy it, clear it, refresh the owner and impacts, then reconcile the current version. Do not repeatedly submit the same stale version.

</details>

<details>

<summary>What if refresh fails after a confirmed save?</summary>

The confirmed record version remains displayed separately. Your response has been retained; refresh current authority/history before further work.

</details>

<details>

<summary>Does no visible change mean there were no corrections anywhere?</summary>

No. This is a bounded projection for this exact revision under current access. It does not expose hidden records or establish completeness outside the cited evidence.

</details>

<details>

<summary>What happens to earlier exports?</summary>

They keep their original quotations, annotations, content hashes and bytes. Prepare any correction through the ordinary review and release workflow; a response itself never rewrites or replaces them.

</details>

## Responsibility and limits

* Responses are immutable, attributed and bound to the exact owning content revision and change identity.
* Current source and annotation access is checked before displaying corrections or retained responses; unavailable history never reports a protected count.
* At most 128 changes are projected and 64 responses retained per owning record, within existing audit/storage bounds. Limits never delete history.
* Warnings and responses do not replace release approval, notify external recipients or silently redistribute a corrected artifact.

**Reference and scope:** Supports F10-R05 in the adopted UK profile: correction impact is separate from original evidence, analytical judgement and product release.

## Related workflows

* [Interpret, translate and cite exact evidence passages](broken://pages/17d4702eceeb9b3e2f7a352f4c556efca5e0732c)
* [Assess evidence quality and retain defect actions](broken://pages/d45ef592dbc8b31eb3995d834ca0be65a9ea2042)
* [Develop and independently review an assessment](broken://pages/79db57a6c6245feef3fb58e4fe6d4a507b2a74a0)
* [Author an intelligence Product and inspect its exports](file:///7397340/product/products.md)
* [Review, approve and publish an exact internal release](file:///7397340/product/release.md)