sis-memory-orchestrator

Memory orchestration coordinates writes, retrievals, and privacy enforcement across substrates like Qdrant, Mem0, and Letta through a seven-subagent layer. It enforces a deterministic workflow with Privacy Guardian, Substrate Selector, and Auditor to maintain an auditable trail for sovereign deployments.

Yes, substrate orchestration routes memory writes and recalls across filesystem vaults, mempalace, Qdrant, Letta, Mem0, AgentDB, and screenpipe backends. A Substrate Selector subagent manages routing to ensure consistent attestation and operation tracking across all pluggable backends.

Sovereign memory management enforces privacy by default and attests all memory operations to maintain an auditable trail for a single user or fleet of tools. You need it when deploying memory substrates requiring governance, deterministic workflows, and cross-substrate benchmarking with privacy guarantees.

Cross-substrate benchmarking coordinates periodic substrate benchmarks through an optional benchmark integration within the orchestration layer. It routes performance tests across backends like Qdrant, Mem0, and filesystem vaults, enabling optimization and decay management for sovereign deployments.

Yes, decay management and lifecycle optimization are supported through optional integrations in the orchestration workflow. The Graph Maintainer subagent coordinates decay management alongside periodic benchmarking to optimize memory operations across all configured substrates.

The deterministic workflow enforces a fixed seven-subagent sequence including Privacy Guardian, Substrate Selector, Indexer/Retriever, Graph Maintainer, and Auditor. This strict orchestration order may limit flexibility for custom workflows but ensures consistent attestation and privacy enforcement across all substrates.