Repository navigation
Add evidence-grounded beginner paper explanation workflow - #2
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.
Add a beginner paper-explanation workflow and strengthen the metadata-to-study-plan path.
When a learner asks for a detailed explanation in the order motivation → method → experiments → results → limitations → outlook, the paper-roadmap skill now prepares evidence with explainPaper and instructs the host Agent to compose connected prose without headings or lists. The six stages are an internal structure, not a fixed paragraph or length limit.
The new tool and explain-paper CLI return bounded candidate passages, original paragraph/sentence locators, source coverage, missing-material requests, and a host explanation contract. Offline output is explicitly an evidence outline, not a claim to understand arbitrary papers. Authors’ claims, general background and suggestions must remain distinguishable; absent experiments or metrics are not invented. The existing eight tools and legacy JSONL remain supported, with explainPaper added as the ninth MCP tool.
Also includes the independently reviewed paper-path improvements: arXiv metadata normalization, stable-ID paginated retrieval, explicit DOI/PDF degradation, phase checkpoints and budget-gap explanations.
Validation: 321 Python tests passed locally; independent review approved the explanation-evidence fixes. Clean wheel installation, two offline CLI examples, all nine installed MCP tools and three legacy JSONL entry points passed. Multiple candidate passages and bounded source_material preserve context beyond short excerpts; truncated ranges are explicitly reported. Real public-network retrieval, editor GUI attachment and host-Agent explanation-quality evaluation remain pending. No paid-model call or Release publication.