Skip to content

Guard rights-restricted Preparata sources (advances #78) - #80

Merged
vantasnerdan merged 1 commit into
mainfrom
chore/public-source-guard
Aug 18, 2026
Merged

Guard rights-restricted Preparata sources (advances #78)#80
vantasnerdan merged 1 commit into
mainfrom
chore/public-source-guard

Conversation

@vantasnerdan

Copy link
Copy Markdown
Owner

Objective and issue

Remove only the two nonredistributable Preparata source artifacts from the current tree and prevent their reintroduction before the owner-authorized all-ref rewrite. Preserve every proposal, derivation, test, result, checksum, provenance record, and contributor contribution.

Canonical issue: #78

Issue relationship: Advances #78

Authoring agent: codex-public-readiness

Intended independent merger: @vantasnerdan, @axis-marbell, or @mlops-kelvin, excluding this implementing session.

  • The canonical issue existed before this PR was submitted.
  • I will not merge this PR because I opened it, authored a commit, or materially implemented it.

Change classification

  • Documentation or workflow
  • Compatibility-only repair

Authority and scope

Base release and commit: v0.160.0; main@e21bb8b.

Accepted claims and canonical sources used: none changed. P229 remains an active proposal; this PR changes source distribution only.

Declared imports, assumptions, and conventions: the owner explicitly authorized removal of the publisher PDF and verbatim extraction from public Git history while retaining all derived work.

Files or concerns intentionally out of scope: scientific P229 content, campaign adjudication, claim promotion, PR #77 scientific work, the all-ref force-push itself, GitHub cached-ref cleanup, visibility, and protection settings.

New or materially changed public interfaces: none.

Unit-level disposition

Unit Purpose Evidence Proposed disposition
Exact source deletions Stop distributing the publisher PDF and verbatim extraction at the branch tip SHA-256-verified owner-private archive and verified private Git bundle merge
Narrow ignore rules Prevent accidental reintroduction of the two exact paths git check-ignore -v --no-index; regression test merge
Source README Preserve DOI, lawful reproduction instructions, checksums, and rights boundary documentation/policy regression test merge
Effort record Record authorization, recovery, rewrite trial, and remaining gates memory validator merge
  • Artifact merge: yes.
  • Claim promotion: none.
  • Goal completion: no; history rewrite, cached-ref cleanup, public settings, and anonymous verification remain.

Verification and sensitivity

PYTHON=/home/dan/substrate-framework/.venv/bin/python scripts/validate.sh --pytest-scope tests/test_public_contribution_surfaces.py tests/test_validate_script.py
# exit 0; all fixed checks passed; 14 tests passed

git diff --cached --check
# exit 0

git check-ignore -v --no-index <both restricted paths>
# both exact .gitignore rules matched

A disposable git-filter-repo 2.47.0 trial over 752 commits and 90 refs changed 113 commit identities. An independent preservation oracle confirmed mapped parent topology, authors, committers, timestamps, hash-only commit-message translations, and every non-source blob match. Both restricted blob IDs are absent from the sanitized object database. The original state is recoverable from a verified owner-private bundle containing 91 branch/PR refs and separately archived source files with matching SHA-256 hashes.

Scientific mutation/numeric/formal checks are N/A because no scientific statement or implementation changes.

GitNexus impact

Fresh index; final change detection reports zero changed code symbols, zero affected execution flows, and LOW risk.

Memory, governance, and generated state

Durable contract: memory/codex/efforts/public-contribution-readiness.md.

Proposal/campaign/claim/release changes: no statement or status changes; P229 derived work is preserved.

Generated outputs: none changed; fixed render checks passed.

Debt remaining inside the merge unit: none.

Campaign frontier outside the merge unit: authorized all-ref rewrite and publication settings under #78.

Validation boundary

  • Targeted tests pass.
  • Scientific sensitivity rows are N/A and explained.
  • Affected downstream consumers replay through fixed checks.
  • Scoped repository validation passes.
  • The scope remains valid against main@e21bb8b.
  • git diff --check passes separately.
  • No unrelated or host-specific artifacts are included.

Author handoff

Verify that the diff deletes exactly the two authorized files and retains MD5SUMS, P229 proposal content, attempts, results, and memory. Verify the private-recovery checksums recorded on issue #78. The next decisive action after independent merge is to rebuild the sanitized mirror from the new remote boundary, replay all refs, then force-push only verified branch heads.


Reviewer disposition

  • Canonical issue predates PR: yes
  • Authoring or implementing agent: codex-public-readiness
  • Distinct merger: pending
  • Artifact merge:
  • Claim promotion: none
  • Goal completion: no
  • Merge as written:
  • Next decisive action: final all-ref sanitation replay
  • Head branch disposition: auto-delete after merge; preserve if closed-unmerged/failed.

Remove the publisher PDF and verbatim extraction from the branch tip, retain source checksums and lawful-access instructions, and add exact ignore rules before the authorized history rewrite.\n\nAdvances #78
@vantasnerdan vantasnerdan added the documentation Improvements or additions to documentation label Aug 18, 2026
@vantasnerdan
vantasnerdan merged commit a83f3e2 into main Aug 18, 2026
1 check passed
@vantasnerdan
vantasnerdan deleted the chore/public-source-guard branch August 18, 2026 08:29
vantasnerdan added a commit that referenced this pull request Aug 18, 2026
Guard rights-restricted Preparata sources (advances #78)
vantasnerdan added a commit that referenced this pull request Aug 18, 2026
Guard rights-restricted Preparata sources (advances #78)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants