Add source-bound evidence for the quarantined training snapshot - #3
Merged
Conversation
5 tasks
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.
What this changes
This PR turns the retained 2024 NLLB payload into an auditable quarantine without pretending it is a successful training project.
main.py,requirements.txt, anddev.jsonl;Final reproducible evidence
Final run 31390505649 regenerated the committed six-file bundle and compared every byte successfully.
train-source-audit-31390505649(ID9063453834)sha256:7522108acac1909bebfa3528b90e69e2596b43d5908770f4bdc6c625935176c9The first CodeQL pass correctly found uncontrolled CLI path inputs. Commit
f3f1683removed--rootand--output-dir, confines all reads/writes to fixed repository-local paths, and regenerated the source-bound evidence. FinalAnalyze (python), aggregateCodeQL, and evidence checks are green; all nine generated review threads are resolved and open code-scanning alerts are zero.Claim boundary
This is source/structure evidence, not dataset provenance, a privacy review, a training run, a checkpoint, a metric, or a release. Provider revocation and rights decisions remain human actions in #2.