feat: add scoped memory records and knowledge promotion#275
Draft
esafwan wants to merge 16 commits into
Draft
Conversation
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.