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

# Pulse

**Open this area:** In the CORTEX menu, select **Assurance & governance → Pulse & audit**.

Review authorised events, deadlines and processing outcomes, with personal read markers distinct from workflow decisions.

**Who uses this:** Analyst, Collector, Requirement owner, Reviewer\
**Open in CORTEX:** `/pulse`\
**In-app guide:** `/help?topic=pulse`

**Expected result:** You can identify the actual record and retained event requiring attention without treating a bounded feed as a whole-node ledger.

## Before you start

* Have Pulse enabled and the explicit access needed for Pulse and its underlying records.
* Choose the module and event or deadline question you intend to inspect.
* Remember that current record state and the state recorded by an earlier event can differ.

## What to do

{% stepper %}
{% step %}

## Select the authorised view

In Pulse choose Authorised module, Event kind, Personal read state and any current state/deadline filters. Set the upcoming window when relevant and select Refresh Pulse.
{% endstep %}

{% step %}

## Read the window accurately

Event pages show an exact range within the selected record window and disappear when all matching events fit on one page. Record navigation says up to ten authorised records and whether another window exists; it does not claim a record total.

Previous and Next only read another page or window and do not change retained records.
{% endstep %}

{% step %}

## Inspect the underlying record

Follow the record title for its current workflow or Inspect retained audit for exact events, actor, time, reason and recorded version.

A derived deadline is labelled separately from an audit event.
{% endstep %}

{% step %}

## Record your personal reading

Use Mark event read only after inspecting the relevant event. The marker is personal and durable; take any required collection, review, release or requirement action in that record's real workflow.
{% endstep %}

{% step %}

## Recheck the outcome

Refresh the record and Pulse after your actual action. Confirm a retained result rather than interpreting a read marker as completion, approval or receipt.
{% endstep %}
{% endstepper %}

## Check the result

* Which record window do these counts cover?
* Is this an actual event or a derived deadline?
* Am I distinguishing historic recorded state from current state?
* Has the required operational action been performed separately?

## If you get stuck

<details>

<summary>Why is an expected event not shown?</summary>

Check module, filters, event page and record window, then open the underlying record's retained audit if authorised. Missing from this bounded feed does not establish that no event exists.

</details>

<details>

<summary>Why did Pulse stay on the same page?</summary>

Changed filters are drafts until you select Refresh Pulse. A temporary page read leaves the last confirmed page available so you can retry. If current Pulse access is forbidden or unavailable, CORTEX removes the protected events, authorised-module context and audit details; restore access before refreshing.

</details>

<details>

<summary>Why did a deadline disappear after completion?</summary>

Deadline views derive from current stored state and exclude completed or cancelled work. Inspect the record history for the actual transition instead of treating the changed feed as deletion.

</details>

<details>

<summary>Why did marking read not clear my task or receipt?</summary>

The marker records only your personal reading. Open the actual task, review or release and perform the permitted decision there; acknowledgement remains explicit on the release.

</details>

## Responsibility and limits

* Users decide which recorded events need action and follow the relevant workflow authority.
* Pulse is not a SIEM, external notification service or comprehensive denied-access ledger. A personal read marker does not acknowledge a released package.

**Reference and scope:** Implementation guidance supporting continuity and reassessment in JDP 2-00 (4th ed.), 2.20, 3.8 and 6.14–6.24. An activity feed does not supply automatic watch conditions or operational decisions.

## Related workflows

* [Define and manage an intelligence requirement](file:///7397340/direction/requirements.md)
* [Acknowledge the exact package and close the feedback loop](file:///7397340/feedback/feedback.md)
* [Preserve an exact revision and manage holds](broken://pages/0185ca5a2331760fb4c59665b8dde7f4d80e0fc6)