> For the complete documentation index, see [llms.txt](https://docs.controltheory.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/memory.md).

# Memory

What Möbius has learned about your workspace, and how you review and correct it

Memory is what Möbius knows about your workspace beyond the telemetry in front of it: which patterns are expected noise, which problems have happened before and what fixed them, which components depend on which, and the instructions you want it to always follow. Möbius uses it every time it looks at a new signal, and you can see all of it, and correct any of it, on the workspace's **Memory** page.

Open it from **Settings → Memory** in any workspace.

### Where memory comes from

Memory grows out of how your team works incidents. You don't have to maintain it by hand.

* **Closing incidents.** Close an incident as **Not an issue** and Möbius learns that pattern as expected noise; close one as **Inaccurate** and it learns that the signal behind it shouldn't open an incident on its own. Close one as **Fixed** and it remembers the problem and the fix together. The note you leave with any of them becomes part of what it remembers. A **One-off** close (real, but it cleared up on its own) teaches nothing, so if the problem comes back Möbius raises it again. This works the same whether you close in the portal or from your own assistant with your API token. See [Closing an incident](/controltheory-documentation/dstl8-docs/incidents.md#closing-an-incident).
* **Incidents that clear up after a change.** When an incident goes quiet shortly after a deploy or configuration change to the affected components, Möbius suggests that change as a possible fix.
* **Möbius's own work.** When Möbius decides a detection was noise, or its [analysis of an incident](/controltheory-documentation/dstl8-docs/incidents.md#analysis) turns up something durable — a dependency, how a component normally behaves — it suggests it here for you to review.
* **Chat.** Ask Möbius to remember something, or type `/remember`, and it's saved here as yours. See [Möbius Chat Slash Commands](/controltheory-documentation/dstl8-docs/slash-commands.md).
* **Guidance you write.** Instructions Möbius must always follow, added on the Memory page.

### What's on the Memory page

The top of the page shows how many facts Möbius has, how many are confirmed, how many are **awaiting your review**, and how many repeat incidents memory has avoided. Below that:

* **Learning timeline** — facts added, confirmed and retired per week, for the last 12 weeks.
* **Dependency map** — the dependencies Möbius has learned, as a graph. An arrow points from a component to what it depends on; hover over an arrow to read the fact behind it. Drag, zoom and pan freely, and use the reset button in the corner to fit everything back into view.

The facts themselves are grouped into tabs, each with a count:

| Tab              | What it holds                                                                                                                                    |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Needs review** | Everything Möbius has suggested that nobody has confirmed yet, across all kinds. Shown only while something is waiting.                          |
| **Known issues** | Problems that have happened before, each with the fixes that resolved it. When one comes back, Möbius links the new incident to the earlier one. |
| **Noise**        | Patterns that look alarming but are expected. Möbius won't open new incidents for confirmed ones.                                                |
| **Dependencies** | Which components depend on which. Möbius uses these to trace a problem back to where it started.                                                 |
| **Components**   | Lasting facts about a component: what it does, how it normally behaves, who owns it.                                                             |
| **Guidance**     | Instructions Möbius always follows. Guidance never expires.                                                                                      |

Use the search box to narrow the current tab by a fact's wording, or by the name of a component it's about. Long lists show 25 facts at a time; **Show more** loads the next ones.

Links to a fact — from an incident's analysis, for example — open the Memory page on the right tab with that fact highlighted.

### Reading a fact

Each fact shows its statement, a status, and where it came from, for example *learned when you closed Checkout errors as fixed*, *from chat by you*, or *suggested by Möbius · needs your review*. Facts Möbius has seen confirmed more than once say so (*confirmed 3× by recurrences*), along with when that last happened. Facts tied to specific incidents, events or log patterns link to them.

| Status           | Meaning                                                                            |
| ---------------- | ---------------------------------------------------------------------------------- |
| **Needs review** | Suggested, not yet confirmed. Möbius uses it, but treats it as unverified.         |
| **Confirmed**    | Approved by someone on your team, or confirmed by the same thing happening again.  |
| **Retired**      | No longer used. Kept for reference; turn on **Show retired** to see retired facts. |

### Reviewing and correcting facts

Suggested facts have an **Approve** button, which confirms the fact and moves it out of **Needs review**. Every fact also has a menu:

* **Edit statement** — reword it. A statement should be a lasting fact about your system, so Dstl8 will ask you to reword one that contains a date, an ID or a one-off count.
* **Pin as guidance** — turn any fact into an instruction Möbius always follows.
* **Retire** — stop Möbius using a fact that's wrong or out of date. Retired facts stay on the page under **Show retired**.
* **Restore as proposed** — bring a retired fact back for review.
* **Delete** — remove a retired fact permanently.

### Guidance

Guidance is memory in the form of instructions: things Möbius must follow in every investigation, such as *"The nightly batch job causes error spikes in api-gateway around 2am — never open an incident for it by itself."*

On the **Guidance** tab, **Add Guidance** opens a short form for a label and the instruction, and **Pin as guidance** on any fact turns it into one. You can also save guidance while closing an incident as **Not an issue**: tick **Remember this as expected noise** and Dstl8 fills in a starting point for you. Guidance never expires and Möbius never changes or removes it; only people do.

### Organization-wide facts

Something you ask Möbius to remember from a page that isn't inside a workspace is saved for your whole organization. Organization-wide facts appear on every workspace's Memory page under their own **Organization-wide** heading. Editing or retiring one there changes it for every workspace.

### How memory stays accurate

Memory looks after itself so it doesn't fill up with stale or duplicate facts:

* When the same problem comes back, or the same noise is closed again, the matching fact is confirmed again, and a suggested fact that keeps being confirmed across several incidents can become confirmed on its own.
* Suggestions that nobody confirms, and that never come up again, are retired automatically after a few months.
* A fact that keeps being contradicted by what actually happens is retired.
* Facts that say the same thing about the same components are merged into one.
* On an incident's analysis, a thumbs-up on a hypothesis confirms the suggested facts it relied on, which keeps them from being retired. It doesn't approve them — that's still your call on the Memory page.

None of this touches guidance, and anything retired can be restored.

### Forgetting something

To have Möbius forget something you told it, say so in chat, or type `/forget` with the fact's wording. Möbius finds the matching fact you added and retires it: it stops using it, and the fact stays on the Memory page under **Show retired** in case you want it back. You can also retire any fact directly from its menu.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.controltheory.com/controltheory-documentation/dstl8-docs/memory.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.