How agenttoolkit/altk-evolve works
Evolve is an agent-memory system: agent clients retrieve task-relevant guidance and submit trajectories, which are processed into reusable entities and stored for later retrieval. Its broader product includes multiple storage backends, an MCP/API and web UI, configurable hooks, versioned processing profiles, Phoenix trajectory sync, and retention/compliance operations. The graph reflects README-described capabilities and relationships supported by the supplied source index or excerpts; unsampled implementation details are not inferred.
Main entry points: evolve_client.py Evolve client · base.py Memory backend · manager.py Profile execution · service.py Retention service
Components 21
Interfaces
- MCP server
altk_evolve/frontend/mcp/mcp_server.py - HTTP API
altk_evolve/frontend/api/routes.py - Evolve client
altk_evolve/frontend/client/evolve_client.py - Web UI
altk_evolve/frontend/ui/src/App.tsx
Learning
- Profile execution
altk_evolve/processing/manager.py - Profile registry
altk_evolve/processing/registry.py - Profile repository
altk_evolve/processing/repository.py - Guideline learning
altk_evolve/llm/guidelines/clustering.py - Guideline retrieval
altk_evolve/llm/guidelines/retrieval.py
Memory
- Memory backend
altk_evolve/backend/base.py - Filesystem backend
altk_evolve/backend/filesystem.py - Postgres backend
altk_evolve/backend/postgres.py - Milvus backend
altk_evolve/backend/milvus.py - Namespace database
altk_evolve/db/sqlite_manager.py
Governance
- Memory hooks
altk_evolve/hooks/manager.py - Retention service
altk_evolve/retention/service.py - Retention engine
altk_evolve/retention/engine.py
Integrations
- Trajectory sync
altk_evolve/sync/phoenix_sync.py
Other components
- AI agent
- Operator
- Arize Phoenix
Connections 24
- AI agent → MCP server: uses tools
README.md - MCP server → Evolve client: serves memory
README.md - Operator → Web UI: manages memory
README.md - Web UI → HTTP API: uses API
- HTTP API → Evolve client: handles operations
altk_evolve/frontend/api/routes.py - Evolve client → Memory backend: uses backend
altk_evolve/frontend/client/evolve_client.py - AI agent → Trajectory sync: submits trajectory
README.md - Arize Phoenix → Trajectory sync: provides traces
altk_evolve/sync/phoenix_sync.py - Trajectory sync → Evolve client: stores results
altk_evolve/sync/phoenix_sync.py - Evolve client → Guideline learning: consolidates guidance
altk_evolve/frontend/client/evolve_client.py - Evolve client → Guideline retrieval: retrieves guidance
altk_evolve/frontend/client/evolve_client.py - Guideline retrieval → Guideline learning: uses clusters
altk_evolve/llm/guidelines/retrieval.py - Evolve client → Profile execution: executes profiles
altk_evolve/frontend/client/evolve_client.py - Profile execution → Profile registry: resolves plugins
altk_evolve/processing/manager.py - Profile execution → Profile repository: reads and writes
altk_evolve/processing/manager.py - Memory backend → Memory hooks: dispatches hooks
altk_evolve/backend/base.py - Memory backend → Namespace database: stores namespace data
altk_evolve/backend/base.py - Memory backend → Filesystem backend: implemented by
- Memory backend → Postgres backend: implemented by
altk_evolve/backend/postgres.py - Memory backend → Milvus backend: implemented by
- Evolve client → Retention service: opens retention
altk_evolve/frontend/client/evolve_client.py - Retention service → Retention engine: executes policies
altk_evolve/retention/engine.py - AI agent → Evolve client: requests guidance
README.md - Operator → Retention service: runs policies
README.md