Repository navigation
Explain Margin passage retrieval and its verification boundaries - #37
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
This branch was successfully deployed
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.
Margin searched whole transcripts through separate app and agent rankers. This case-study update explains the local shared passage index, the source-preserving read model, and the recovery tradeoffs, with a sanitized architecture diagram.
The copy explicitly distinguishes local retrieval development from an installed release and keeps semantic retrieval behind reviewed relevance evaluation. The existing fictional screenshots remain in place.
Validation: 58 tests passed, TypeScript checked, lint passed with two existing warnings, privacy scan passed, and the production build passed on Node 24. The local case-study page and diagram were inspected in the browser.