Skip to main content
Incident Memory is the set of saved notes Anna can write during root-cause analysis (RCA) and read at the start of a later investigation. It is the incident-focused part of workspace memory, and it preserves useful operational knowledge without influencing how Pulse classifies new events.

​
What gets written

Incident Memory is agent-written. CloudThinker does not automatically extract a fixed record from every completed Incident. Entries can include the affected service, evidence, action taken, a verification command, and an outcome. The agent writes only material it judges useful for later RCA.

​
How recall works

  1. Anna writes incident memory files during an RCA run.
  2. At the start of a later RCA, CloudThinker reads valid, recent entries from the workspace memory tree.
  3. The selected entries appear in Anna’s incident-memory context before hypothesis work begins.
  4. Anna compares the current evidence with those lessons instead of treating a past resolution as proof.
Recall re-enters Resolve at the Analyze stage. Pulse may maintain separate cluster memory, but it never reads raw incident-memory files when classifying events.
The current Incident UI does not show an “Informed by similar incidents” badge or a per-memory recall list. Memory changes the RCA context behind the scenes.

​
Verification outcomes

An incident-memory entry can carry one of three outcomes: When a runbook includes a verification command, Anna can schedule one follow-up check and update the outcome. Resolve does not run a universal post-remediation process for every Incident. Failed lessons are never presented to Anna as valid guidance. Failed recollections can remain as counter-examples so a later RCA does not repeat the same assumption.

​
Availability and limits

  • Incident memory must be available for your workspace before entries can be written or recalled.
  • Only entries that pass the memory format and safety checks are eligible for recall.
  • Recall is capped and ordered by recent updates, so Anna never reads the entire history.
  • Cancelled or failed RCA runs contribute memory only if the agent already wrote a valid entry.
  • Re-running RCA does not mechanically replace an older entry; Anna can revise, combine, or supersede memory when evidence changes.

​
Use memory well

  • Record the evidence that distinguishes the root cause from a symptom.
  • Add a concrete verification command to remediation runbooks where practical.
  • Treat recalled context as a hypothesis lead, not as a diagnosis.
  • Review a failed verification before reusing the same Scoped Action.

Investigation and RCA

See where memory enters the three-phase investigation.

Runbooks

Add the procedures and verification commands Resolve can use during response.

Workspace Memory

What agents remember platform-wide, and how to correct a remembered note.