Core Concepts
Understanding these concepts will help you get the most out of Aegis Memory.Memory
A memory is a single piece of information stored in Aegis. Each memory has:Memory Types
| Type | Purpose | Example |
|---|---|---|
standard | Facts and preferences | ”User’s name is John” |
strategy | Reusable patterns | ”For pagination, use while True loop” |
reflection | Lessons from failures | ”Don’t use range() for unknown lengths” |
progress | Session state | ”Completed: auth, routing. In progress: API” |
feature | Feature tracking | ”Login feature: 3/5 tests passing” |
Scope
Scope controls who can see a memory:Namespace
Namespace provides logical separation between projects or tenants:Agent ID
Agent ID identifies which agent created or owns a memory:User ID
User ID associates memories with specific users:Embeddings
Aegis converts memory content into embeddings (vector representations) for semantic search:Effectiveness Score
For ACE patterns, memories have an effectiveness score:- Score > 0: Memory has been helpful
- Score < 0: Memory has been harmful
- Query with
min_effectiveness=0.3to get only proven strategies
Sessions
Sessions track progress across context windows:Features
Features prevent premature task completion:Quick Reference
| Concept | Purpose | Example |
|---|---|---|
| Memory | Single piece of information | ”User prefers Python” |
| Scope | Access control | agent-private, agent-shared, global |
| Namespace | Project/tenant isolation | ”production”, “staging” |
| Agent ID | Agent ownership | ”planner”, “executor” |
| User ID | User association | ”user_123” |
| Embedding | Vector for semantic search | [0.12, -0.45, …] |
| Effectiveness | Vote-based quality score | 0.8 (helpful) |
| Session | Progress tracking | completed, in_progress, next |
| Feature | Verification gates | test steps, pass/fail |