Add frozen shared corpus builder - #6
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.
Research question
Can the sealed synthetic-data smoke be scaled into a reproducible, role-isolated 40,000-record shared corpus without weakening determinism or overlap safeguards?
Changed variable
This change adds the frozen
shared-corpus-2026.08.12configuration, schema, coverage matrix, streaming generator, scalable overlap audit, and independent verification entry point. It does not add model training.Data and license boundary
All records are project-authored synthetic content with rebuild-only runtime assets. Terminal benchmark and Customer50 inputs are explicitly absent. Train/development/holdout family isolation and exact/near duplicate checks are hard gates.
Acceptance
Validation
pytest -q— 43 passed.