Repository navigation
Add bounded read recovery and reproducible robustness experiments - #30
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.
Hybrid retrieval currently fails when query embeddings or vector queries experience transient outages, and robustness experiments cannot separate retry, degradation, and rebuild costs. This change adds opt-in BM25 fallback on the same filtered snapshot, shared bounded retries and query deadlines, and structured recovery diagnostics. Invalid requests, authentication failures, and missing local data continue to propagate as errors.
Workspace builds now expose per-attempt reuse, compute, materialization, timing, and provider-reported usage metrics. A reproducible experiment CLI compares no recovery, retry, and fallback policies and tests checkpoint/publication recovery using actual child-process interruption. Fixture outputs are explicitly labeled smoke tests; they do not establish model answer quality or paper benchmark results.
Validation:
Details and live experiment commands:
docs/READ_RECOVERY.md.