search-canonical-memory

To read the active canonical memory without side effects, you can use a provider-agnostic facade that dispatches queries to the configured provider's read skill. It returns the provider's response verbatim, ensuring strictly read-only access without any write operations.

Canonical memory provider resolution is the process of discovering the configured memory provider within a host project. It is needed to establish a unified read path that abstracts the underlying provider, enabling provider-agnostic access to the active canonical memory content.

Yes, you can query the canonical memory from any host project. The read-only access mechanism is designed for portability, allowing you to invoke memory queries across different host environments without being tied to a specific provider implementation.

Canonical memory search returns raw results verbatim from the configured provider's read skill. It does not format or transform the output, ensuring that the unified read path delivers the exact provider response without any additional processing layers.

The main limitation of a read-only canonical memory facade is that it cannot write, update, or modify memory entries. It is strictly restricted to dispatching read queries, meaning any side-effect-inducing operations must be handled by separate write-specific components.