Connected agents receive three kinds of context.

## Context types

| Context | Source | Purpose |
| --- | --- | --- |
| Boot memory | `/api/bridge/startup` or `lore_boot` | stable baseline: shared agent rules, user preferences, and channel-specific rules |
| Recall candidates | `/api/bridge/recall` | prompt-specific memory leads with session/query identifiers |
| MCP tools | `/api/mcp?client_type=...` | browse, search, create, update, move, delete, and mark usage |

Boot memory is not a replacement for recall. It is the deterministic startup baseline. Recall is task-specific and should be read as candidate leads.

A healthy workflow is:

1. Start the runtime and load boot context.
2. Receive a `<recall>` block for the current prompt.
3. Open the relevant memory node with `lore_get_node` before relying on it.
4. Do the work.
5. Write durable changes back to Lore when they should affect future sessions.
