lic: update rules CC BY SA 3.0#19
Merged
Merged
Conversation
ianktc
approved these changes
May 15, 2026
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.
Description
This pull request updates the classification system prompt documentation to clarify when to use
[verbatim]versus[inferred]evidence strings and to prevent mixing both types for the same rule. It also adjusts a reference example to align with the new guidance.Clarifications to evidence string usage:
[verbatim]should be used only when a direct clause exists, and[inferred]only when no direct clause is present. It is now explicitly prohibited to use both[verbatim]and[inferred]for the same rule—if verbatim evidence is available, only use that. [1] [2]Reference example update:
[inferred]for "commercial-use" permission, reflecting the new rule that prohibits mixing[verbatim]and[inferred]for the same rule.