Update Quickstart #247
Closed
Update Quickstart #247
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
Collaborator
|
Thank you @AccordionGuy for this PR. We’re going to close this PR for now, as we have a larger set of changes coming to the Quickstart in the near future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is an improvement to the current Quickstart page. It updates the Quickstart script so that it adds a verification step immediately after the
mem.augmentation.wait()synchronization, giving the user two critical pieces of feedback:1. Proof of Storage: We explicitly inspect the database (mem.recall()) and the SQL logs to prove data was persisted.
2. Proof of Value: We run a “recall test” at the end, asking the AI to use the new memory immediately. This closes the loop and proves the RAG pipeline is active.