Add optional methods to the MemoryProvider interface: system_prompt_block(), prefetch(query), queue_prefetch(query), sync_turn(user, assistant), handle_tool_call(name, args), shutdown(). These are defined as separate interface extensions that providers can opt into via type assertion.
Acceptance Criteria
Optional behavior is defined via separate sub-interfaces (e.g., PrefetchProvider, SyncTurnProvider, ShutdownProvider)
MemoryManager checks via type assertion at runtime which optional interfaces a provider implements
Each optional interface has clear doc comments
Default no-op behavior when a provider doesn't implement an optional interface
Imported from beads archie-core-1786637495012-199-eaacf19a · GitHub #220 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08
Add optional methods to the MemoryProvider interface: system_prompt_block(), prefetch(query), queue_prefetch(query), sync_turn(user, assistant), handle_tool_call(name, args), shutdown(). These are defined as separate interface extensions that providers can opt into via type assertion.
### Acceptance Criteria
Optional behavior is defined via separate sub-interfaces (e.g., PrefetchProvider, SyncTurnProvider, ShutdownProvider)
MemoryManager checks via type assertion at runtime which optional interfaces a provider implements
Each optional interface has clear doc comments
Default no-op behavior when a provider doesn't implement an optional interface
---
_Imported from beads `archie-core-1786637495012-199-eaacf19a` · GitHub #220 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam
added the mediumtask labels 2026-10-27 13:37:29 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Add optional methods to the MemoryProvider interface: system_prompt_block(), prefetch(query), queue_prefetch(query), sync_turn(user, assistant), handle_tool_call(name, args), shutdown(). These are defined as separate interface extensions that providers can opt into via type assertion.
Acceptance Criteria
Optional behavior is defined via separate sub-interfaces (e.g., PrefetchProvider, SyncTurnProvider, ShutdownProvider)
MemoryManager checks via type assertion at runtime which optional interfaces a provider implements
Each optional interface has clear doc comments
Default no-op behavior when a provider doesn't implement an optional interface
Imported from beads
archie-core-1786637495012-199-eaacf19a· GitHub #220 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08