Repository navigation
Document how list/hierarchical relevance departs from the proposal - #34
Merged
Merged
Conversation
The machines-oriented proposal has no concept of relevance, includes every unit in hierarchical, and makes pruning opt-in. The engine's default relevant level omits irrelevant records and prunes empty units; the guide now says so and names verbose=True as the unpruned structure. Also correct the claim that a verbose node's own valid marks relevance: a result is relevant only when every node from the root down to it shares the root's valid. In list/hierarchical the dropped* markers classify records, and a unit's valid does not mark relevance even along its path. Tests pin both rules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
The machines-oriented proposal has no concept of relevance, includes every unit in hierarchical, and makes pruning opt-in. The engine's default relevant level omits irrelevant records and prunes empty units; the guide now says so and names verbose=True as the unpruned structure.
Also correct the claim that a verbose node's own valid marks relevance: a result is relevant only when every node from the root down to it shares the root's valid. In list/hierarchical the dropped* markers classify records, and a unit's valid does not mark relevance even along its path. Tests pin both rules.