Repository navigation
Document stateless remote storage and conservative proactive recall - #6
Merged
Merged
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.
Document the stateless Kimetsu Remote storage modes, disposable SQLite retrieval projections, shared org authorization, explicit memory-write opt-in, provider durability limits, and HTTP/Lambda deployment examples. The overview also explains that proactive recall stays quiet for greetings and uncertain or mismatched evidence.
Companion to RodCor/kimetsu#50; merge after the code PR so the linked storage/deployment documentation is available on main. SDK clients keep the same HTTP MCP API.
Validation:
npm run checkpassed, including lint, types, 29 tests, production build and the static-route checks. Documentation changes only; no deployment or dependency changes.