feat: add scoped memory records and knowledge promotion#275
Closed
esafwan wants to merge 18 commits into
Closed
Conversation
Tool wiring (sdk_tools.py + agent_tool_function.json): - Add 5 native tool types: Save Memory Record, Search Memory Records, Get Memory Record, Archive Memory Record, Promote Memory to Knowledge - Each maps to corresponding handler in huf/ai/memory_tools.py Docs (docs/memory/): - zero-to-hero.md: full onboarding guide capturing Agno/Hindsight/Mem0 influences, how existing knowledge backends work, architecture diagrams, scope matrix, design decisions and reasons, glossary - phase-plan.md: per-phase delivery plan (Phases 0-5) with definition of done, security model, backward compatibility notes, open questions
esafwan
added a commit
that referenced
this pull request
May 28, 2026
Three new documentation files covering the full memory architecture: - docs/SCOPED_MEMORY_KNOWLEDGE_BRIDGE_RFC.md — Updated RFC reflecting current state: three live backends (sqlite_fts, sqlite_vec, chroma), Phase 1 implemented via PR #275, phases 2–5 defined with learning profiles and learning agents - docs/memory/zero-to-hero.md — Full onboarding doc capturing intellectual provenance (Agno/Hindsight/Mem0 references), how existing knowledge backends work, the three-layer architecture, what exists today vs what is planned, key files, design decisions and their reasons, glossary - docs/memory/phase-plan.md — Per-phase delivery plan with definition of done, file-level targets, cross-cutting concerns (security, testing, backward compat) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
esafwan
added a commit
that referenced
this pull request
May 28, 2026
Three new documentation files covering the full memory architecture: - docs/SCOPED_MEMORY_KNOWLEDGE_BRIDGE_RFC.md — Updated RFC reflecting current state: three live backends (sqlite_fts, sqlite_vec, chroma), Phase 1 implemented via PR #275, phases 2–5 defined with learning profiles and learning agents - docs/memory/zero-to-hero.md — Full onboarding doc capturing intellectual provenance (Agno/Hindsight/Mem0 references), how existing knowledge backends work, the three-layer architecture, what exists today vs what is planned, key files, design decisions and their reasons, glossary - docs/memory/phase-plan.md — Per-phase delivery plan with definition of done, file-level targets, cross-cutting concerns (security, testing, backward compat)
esafwan
added a commit
that referenced
this pull request
May 28, 2026
…d phase plan - Status changed from Discussion to Active - Three live backends documented (sqlite_fts, sqlite_vec, chroma) - Phase 1 (PR #275) marked implemented - Phases 2-5 defined with learning profiles and learning agent design - Reference architecture section added (Agno, Hindsight, Mem0) - Points to new zero-to-hero and phase-plan docs in feature/scoped-memory-core Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
eba8bca to
3c9b5ce
Compare
esafwan
added a commit
that referenced
this pull request
May 28, 2026
…d phase plan - Status changed from Discussion to Active - Three live backends documented (sqlite_fts, sqlite_vec, chroma) - Phase 1 (PR #275) marked implemented - Phases 2-5 defined with learning profiles and learning agent design - Reference architecture section added (Agno, Hindsight, Mem0) - Points to new zero-to-hero and phase-plan docs in feature/scoped-memory-core
Contributor
Author
|
Superseded by the unified implementation in PR #282. All the code and concepts from this PR have been integrated into that branch, alongside fully functioning background learning agents and hybrid search backends. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the first two development slices from the scoped memory / knowledge bridge plan:
docs: add scoped memory and knowledge bridge RFC #274 core schema + tools
Memory RecordDocType as the canonical scoped memory/data layer.Memory PolicyDocType for capture/retrieval/projection policy configuration.docs: add scoped memory and knowledge bridge RFC #274 → docs: RFC for adapting Agno's knowledge/vectordb architecture into HUF #178 promote memory to knowledge
promote_to_knowledgeon Memory Record.Knowledge Inputflow asTextinputs.Key files
huf/huf/doctype/memory_record/huf/huf/doctype/memory_policy/huf/ai/memory_tools.pyArchitecture note
This intentionally does not implement Hindsight-style learning yet. It creates the stable canonical layer first, then connects it to the existing Knowledge Source / Knowledge Input path.
This PR follows the order discussed in #274:
Related:
Testing
Not run in this environment.
Recommended validation after checkout:
Manual checks:
Memory Recordwithstatus = Active.Promote to Knowledge = 1and choose aKnowledge Source.Knowledge Inputis created and queued/processed.