Clarify private preservation provenance - #1
Merged
Conversation
There was a problem hiding this comment.
🟡 Not ready to approve
The updated provenance audit paragraph contains internally inconsistent phrasing and a stronger retention-policy claim than the README, which should be reconciled for clarity.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.
Pull request overview
This PR updates the public documentation to clarify the boundary between the GitHub “source-only mirror” and privately held preservation material, removing an explicit Dropbox path while keeping provenance intent intact.
Changes:
- Removes the former Dropbox location from public provenance documentation.
- Clarifies that snapshot archives/notes remain private and that redundant bundles + third-party release downloads are outside this mirror.
- Tightens wording around what is (and is not) preserved/published.
File summaries
| File | Description |
|---|---|
| README.md | Refines the public scope statement for what the mirror contains vs. what remains private. |
| PROVENANCE.md | Replaces the explicit private path with a non-locating description and updates the audit/scope wording. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Lite
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
Comment on lines
+9
to
+12
| The original source was re-audited on 2026-08-03. The four expanded source | ||
| trees matched this repository byte-for-byte, apart from empty directories that | ||
| Git cannot represent. Redundant bundle archives and unmodified third-party | ||
| release downloads were deliberately excluded from long-term retention. |
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 changed
Why
The private preservation source has been compacted and moved out of Dropbox. The public repository should record the preservation boundary without exposing private storage infrastructure.
Validation
git diff --check