Agent Memory types
Memory type describes the kind of guidance the agent should retrieve. It is separate from the memory's scope and source. A Global preference and a vendor-scoped preference are still different in reach, even though their type is the same.
| Type | Use it for | Example |
|---|---|---|
| Rule | A condition with a clear expected outcome | “When the vendor is Acme and the line is freight, use the Freight account.” |
| Procedural | A repeatable sequence or method | “Check the PO line first, then use the receipt quantity before routing the invoice.” |
| Preference | A default choice when more than one valid option exists | “Prefer the project allocation from the PO when both the PO and vendor history provide one.” |
Pick the narrowest useful type
Use Rule when the team wants a direct mapping. Use Procedural when the agent must follow several checks in order. Use Preference when the guidance should break a tie but not override a stronger source or validation rule.
Keep one outcome per memory. If a rule includes a second behavior for a different vendor or exception, split it into another memory and choose its own scope.
Read the source behind a memory
The Memories list also carries provenance:
- Created by identifies a manual memory and its author.
- Authored by Clark · approved by identifies guidance that came through the review workflow.
- Seeded from ERP history identifies a candidate grounded in historical ERP records.
- Imported from settings identifies guidance carried over from an older settings path.
Source is a trust and review cue, not a memory type. ERP-history candidates and correction-based proposals still need a human decision before they become active. See Approve proposed memories.
Type does not change platform controls
An active memory can guide extraction, coding, matching context, or email classification when it is relevant. It cannot bypass validation, approval routing, or required fields. If a memory conflicts with a validation rule, resolve the configuration or the memory instead of expecting the agent to skip the check.
For the reach of the memory, see Memory scope. To write one, see Create your first memory.