Repository navigation
Build reusable knowledge guides from saved history - #1975
Merged
Merged
Conversation
santoshkumarradha
marked this pull request as draft
October 26, 2026 21:42
santoshkumarradha
marked this pull request as ready for review
October 26, 2026 22:51
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
The knowledge module separates saved source history, concept organization, generated guides, and human-authored changes.
Initial builds organize the admitted history before publishing guides. Later evidence updates affected concepts or creates distinct concepts. Source citations remain available independently of the concise reader articles.
The Memory screen uses the same published pages as agent recall. Navigation, hover feedback, and stage progress remain separate from background model work.
Evidence
After: catalog-aware reuse preserves page identity, evidence remains attached, and publication validates the complete result.
Merge Danger
Door: code can be reverted; generated organization and identity repairs persist in the profile database.
Blast Radius: knowledge
Changes affect saved-history eligibility, background compilation, generated-page publication, and Memory rendering. Original source text, human edits, and deletion intent remain protected.