> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Memories

> What Ordyn remembers about your systems between investigations.

Ordyn gets better at your systems over time. **Memories** is where that context lives and where you can add to it.

## Company context

Write down what an engineer joining your team would need to know: what your services do, which ones matter most, naming conventions, known quirks, who owns what. Every Ordyn agent reads this before it starts work, whether it is triaging an alert, reviewing a pull request, or writing a fix.

Admins edit company context from the **Memories** page. Changes apply to the next run.

## Tell Ordyn in Slack

Reply on an alert thread with context Ordyn should keep, and it remembers it the next time that monitor fires.

```text theme={null}
@Ordyn this is expected during our nightly batch
```

## What Ordyn learns on its own

Ordyn also keeps notes from its own work, such as what a monitor's alerts have turned out to mean and how past problems were resolved. These feed into future triage and investigations so a repeat issue follows a known path instead of starting from scratch.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.