-
Notifications
You must be signed in to change notification settings - Fork 0
feat: implement concrete memory backend adapter #206
Copy link
Copy link
Labels
prio:highImportant, should be prioritizedImportant, should be prioritizedscope:large3+ days of work3+ days of workspec:memoryDESIGN_SPEC Section 7 - Memory & PersistenceDESIGN_SPEC Section 7 - Memory & Persistencetype:featureNew feature implementationNew feature implementation
Description
Summary
The MemoryBackend protocol, factory, config, and retrieval pipeline all exist, but there is no concrete backend adapter implementation. The protocol needs at least one real backend to be functional.
Design Spec Reference
- §7.5 Memory Backend Protocol
- ADR-001 Memory Layer Decision
Scope
- Implement a concrete
MemoryBackendadapter (reference ADR-001 for the selected technology — evaluate current viability at implementation time) - Ensure compatibility with
MemoryCapabilitiesprotocol - Ensure compatibility with
SharedKnowledgeStoreprotocol if the backend supports it - Integration tests with the retrieval pipeline (
retriever.py)
Notes
- The specific memory technology should be re-evaluated at implementation time — ADR-001 documents the initial decision but library ecosystems evolve
- Must support Python 3.14+
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
prio:highImportant, should be prioritizedImportant, should be prioritizedscope:large3+ days of work3+ days of workspec:memoryDESIGN_SPEC Section 7 - Memory & PersistenceDESIGN_SPEC Section 7 - Memory & Persistencetype:featureNew feature implementationNew feature implementation