Priority levels
Use priority levels to mark importance without making recall noisy.
Priority is an importance signal, not a guarantee that a memory always appears.
Priority guide
| Priority | Use for |
|---|---|
0 | core identity, safety, or rules that almost always matter |
1 | important preferences, project constraints, and high-value workflows |
2 | normal project knowledge |
3+ | background notes and lower-importance context |
Keep priority honest. If everything is priority 0, recall becomes noisy and important rules stop standing out.
A common shape:
- global agent rules:
0or1 - user preferences:
1 - active project constraints:
1or2 - ordinary implementation notes:
2 - historical context:
3+