crestapps-core-ai-memory

CrestApps.Core AI Memory

Memory stores long-lived facts about the authenticated user (preferences, projects, roles) and recalls them in later conversations. It is not for transient chat state.

Registration

builder.Services.AddCrestAppsCore(crestApps => crestApps
    .AddAISuite(ai => ai
        .AddOpenAI()
        .AddAIMemory(memory => memory
            .AddEntityCoreStores()))   // or .AddYesSqlStores()
    .AddIndexingServices(indexing => indexing
        .AddEntityCoreStores()
        .AddElasticsearch(
            builder.Configuration.GetSection("CrestApps:Elasticsearch"),
            elasticsearch => elasticsearch.AddAIMemory()))
    .AddEntityCoreSqliteDataStore("Data Source=app.db"));

builder.Services.Configure<AIMemoryOptions>(options =>
{
    options.IndexProfileName = "user-memories"; // an index profile of type AIMemory
    options.TopN = 5;
});

• AddAIMemory(...) calls AddCoreAIMemory(), which registers IAIMemorySafetyService, IAIMemorySearchService, AIMemoryIndexingService, AIMemoryOrchestrationHandler, AIMemoryPreemptiveRagHandler, the options and the four memory tools.
• The store builder call registers IAIMemoryStore (and ICatalog<AIMemoryEntry>). YesSql hosts also create the index table with CreateAIMemoryEntryIndexSchemaAsync(...).
• A backend's AddAIMemory() registers the AIMemory index-profile source, its profile handler and the keyed IMemoryVectorSearchService. Without it, memory is stored but never searched semantically.
• AIMemoryOptions.IndexProfileName must name an existing index profile of type AIMemory; otherwise indexing logs a warning and skips.

Turning Memory On