Repository navigation
Keep public Jieyue while moving interpretation research privately - #31
Open
Crystal32378 wants to merge 2 commits into
Open
Crystal32378 wants to merge 2 commits into
Crystal32378 wants to merge 2 commits into
Conversation
This branch has not been 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.
The existing removal branch predates the public 94-entry Guanyin 解曰 footnote. Removing its producer inputs without separating the tests now breaks verification. This revision keeps the accepted public feature and moves only the interpretation-layer research package and its direct producer dependencies into private custody.
Validation:
Merge dependency: first merge and verify Crystal32378/draw-one-research#1, then review this PR. Both PRs remain unmerged for owner review. No manual deployment is included.
Scope limits: other research directories and production corpus inputs are unchanged. Current-tree removal does not erase past public commits, branches, forks, or caches. Public fingerprints verify approved release bytes; they do not independently revalidate new private source material. Future content changes require private source validation followed by a separately reviewed public artifact/guard/manifest update.