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

# Decision Briefs

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

Frame one requirement, inspect bounded current assessments, and retain either a live query definition or exact source-version snapshot.

**Who uses this:** Recipient, Analyst, Author, Reviewer\
**Open in CORTEX:** `/briefings`\
**In-app guide:** `/help?topic=decision-briefs`

**Expected result:** A decision-maker can see the question, judgements, evidence changes, gaps, release state, and population limits without mistaking a sample for complete coverage.

## Before you start

* Select the intended workspace and an authorised Direction requirement.
* Have current read access to every source type you expect; unavailable modules remain unknown rather than zero.
* Decide whether you need a refreshed saved query or immutable source-version pins.

## What to do

{% stepper %}
{% step %}

## Define the bounded population

Choose the exact requirement and, where needed:

* Topic
* Source-update period
* Analyst
* Released-only rule
* Geographic bounds
* Page

Time filters apply to source updates. Geography uses exact retained links; unmapped work is excluded rather than placed at a default point.
{% endstep %}

{% step %}

## Read coverage before content

Check notices, matching-analysis count, and whether the population is complete.

Charts are suppressed when the 100-record source window, requested page, release correlation, or geography is incomplete. Missing access is shown as unknown, never zero.
{% endstep %}

{% step %}

## Inspect the analytical cards

Read the:

* Exact requirement state
* Observed analysis state
* Retained revision
* Judgements
* Evidence
* Gaps
* Change explanation
* Handling

Released means a visible exact Product revision has a Released package; a draft or approval alone is not release.
{% endstep %}

{% step %}

## Retain the intended form

A **Saved query** stores the definition and refreshes against current authorised records whenever opened.

A **Snapshot** pins exact requirement, analysis, Product, Release, and geographic versions/hashes.

Both actions require:

* A title of 3–200 characters
* A retention reason of 3–1,000 characters

The buttons become available when both fields are valid.
{% endstep %}

{% step %}

## Prepare controlled output

From a current, non-withdrawn retained brief, choose an exact analysis and prepare a Product only when the controlled Product workflow permits it.

Review the created draft and use the normal release workflow; the brief itself does not publish anything.
{% endstep %}

{% step %}

## Withdraw or supersede responsibly

The brief owner can withdraw with the current version and a separate withdrawal reason of 3–1,000 characters beside the action.

Optionally name an accessible current successor for the same requirement with covering handling.

History and pins remain retained.

If a saved-directory page fails to load, retry it while the last confirmed page remains visible; a lost access check clears protected content.
{% endstep %}
{% endstepper %}

## Check the result

* Is this the exact requirement and declared bounded population?
* Is coverage complete, partial, or unknown?
* Am I viewing current query results or captured versions?
* Do release claims match an exact released package?
* Is Product preparation still justified against current sources?

## If you get stuck

<details>

<summary>Why are charts or totals missing?</summary>

The authorised population is incomplete or a source capability failed. Refine the query, change page, or restore access, then refresh.

Do not calculate a global percentage from the visible sample.

</details>

<details>

<summary>Why does a snapshot differ from the source page?</summary>

The snapshot shows its captured exact versions while source records may have advanced. Read its notices and current source links, then retain a successor if a new decision basis is required.

</details>

<details>

<summary>Why can I open a brief but not prepare a Product?</summary>

Product preparation needs the relevant current Product and Ingest capability, an eligible exact analysis, and a non-withdrawn brief.

Continue in the full Product workflow after resolving the stated validation or access issue.

</details>

## Responsibility and limits

* Current access is revalidated whenever a retained brief is opened; a snapshot is not an access bypass.
* A saved query can change as current records change. A snapshot can become superseded and must be revalidated before new output.
* Withdrawal preserves the retained history and does not withdraw its source analyses, products, or releases.

**Reference and scope:** Implementation guidance for briefing from assessed, traceable intelligence. A composed brief supports judgement; it does not supply command authority, confidence, or a release decision.

**Related workflows:** [Use your dashboard and tasking lifecycle](file:///7397340/getting-started/personal-dashboard.md); [Define and manage an intelligence requirement](file:///7397340/direction/requirements.md); [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); [Explore and retain governed geographic evidence](broken://pages/dbc4fbf0c6f54637ceda772a10f781bc00c27f06).