3 commits

Author	SHA1	Message	Date
Mikael Hugo	3e6827e7dc	docs: remove stale direct db and mcp guidance	2026-05-07 03:33:14 +02:00
Mikael Hugo	b384c8e0df	docs: clarify memory system is SF-internal, not MCP-exposed ... Add architecture decision: Memory is not exposed as MCP server. - SF is an MCP client only (consumes external MCP tools) - Memory is internal SF infrastructure (uses SQLite, fire-and-forget async) - Memory exposed as SF tools only (capture, query, graph) - No external MCP exposure needed (memory is autonomous learning, not a service) This keeps SF's learning system private and prevents: - External memory pollution - Uncontrolled confidence scoring - Inconsistent learning patterns - Loss of autonomy (memory decisions stay internal) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>	2026-05-07 01:41:33 +02:00
Mikael Hugo	b6ea800e2e	docs: comprehensive SF memory system architecture reference ... Add MEMORY-SYSTEM-ARCHITECTURE.md documenting: - All 10 memory modules (store, embeddings, relations, etc.) - Core functions and APIs for each module - Storage schema (SQLite tables) - Integration points (UOK, dispatch, gates) - Usage examples and architecture diagram - Performance characteristics - Graceful degradation strategy - Data retention and growth management This serves as: 1. Reference guide for developers using memory system 2. Architecture overview of autonomous learning 3. Integration point documentation for extensions 4. Future enhancement roadmap Discovered during UOK memory integration work: - Memory system already complete (no duplication needed) - Used for pattern learning, dispatch ranking, and diagnostics - Node 24 native SQLite backend (no external deps) - Fire-and-forget async operations (never blocks) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>	2026-05-07 01:36:08 +02:00