docs: plan PGVector knowledge backend architecture#279
Closed
esafwan wants to merge 1 commit into
Closed
Conversation
4 tasks
Contributor
Author
|
Closing in favor of #280 which now contains both the architecture documentation and the full pgvector implementation. All backend and DocType changes from the original plan have been implemented and tested end-to-end there. |
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
1 participant
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.
Documentation-only PR adding a PGVector implementation plan for HUF Knowledge.
Covers current SQLite Vec and ChromaDB patterns, Knowledge Source/UI wiring gaps, suggested PGVector schema, filtering strategy, implementation phases, and GoHoppy/Genie hotel recommendation use case.
No runtime code changes.