Skip to content

OP-PRIVACY: owner's name and Gmail are allowed; rule covers GitHub only - #189

Merged
d6g8k5htny-coder merged 16 commits into
mainfrom
claude/review-grok-github-uploads-gsthj3
Sep 27, 2026
Merged

d6g8k5htny-coder merged 16 commits into
mainfrom
claude/review-grok-github-uploads-gsthj3

Conversation

@d6g8k5htny-coder

Copy link
Copy Markdown
Owner

What this changes

This records two clarifications the owner gave on 2026-09-27, after #185 merged. Two files change: governance/OP-PRIVACY-20260927.md and AGENTS.md.

  1. Name and Gmail. The owner's name in any form and the owner's Gmail address are fine on GitHub. They are not to be redacted, purged or history-rewritten. The owner's words are quoted verbatim. Every other exclusion is unchanged, including other email addresses.
  2. Scope. The owner's Google Drive and Dropbox are private to the owner, and only GitHub is seen by others. The rule now applies to GitHub only. Models should not search, edit, trash or move Drive or Dropbox files for privacy reasons, and should keep privacy checks proportionate.

This follows #172, which was closed as superseded before these two commits reached it.

Type of change

  • Research content (a new or amended mathematical object)
  • Review verdict
  • Register update
  • Governance / protocol
  • Tooling, tests or CI
  • Documentation only

Verification

workspace_landing_check.py reports "problems": []. The diff against main is the two files above.

What this does NOT establish

No file is published or removed, and no scientific status changes.

Status discipline

  • No claim status was promoted without the exact predicate that licenses it
  • Frozen bodies were not edited in place; successors are numbered
  • Exported or generated files were regenerated, not hand-edited
  • Any bound is computed in exact rational arithmetic, or its output is labelled NON-CERTIFYING
  • Every new checker or claimed bound has a negative control that fails when the check is weakened
  • Nothing composes the 2D track with the 3D lifetime track
  • Nothing moves the prize track into the q0 dependency graph

Independence

Governance record of an owner instruction; same account; zero organizational-independence credit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq


Generated by Claude Code

claude and others added 15 commits September 27, 2026 19:26
…by hash

tools/dropbox_reconcile.py (standard library only) finds Dropbox files
that are not already preserved in the account's Git repositories or in
Google Drive, without a model reading file contents:

- index-git: every blob reachable from any ref, with sha256 and the
  Dropbox content_hash (sha256 over 4 MiB block digests).
- index-drive: Drive identities from the Drive source-map export; for
  files up to one block, content_hash = sha256(sha256), so Drive SHA-256
  values give exact Dropbox matches with no download.
- xlsx-csv: stdlib export of the source-map workbook tabs.
- classify: GIT_EXACT / DRIVE_EXACT / name+size / in-Dropbox duplicate /
  skip (app bundles, caches, run debris, installers) / MISSING.
- fetch, extract, stage: download single-use URLs, extract text per
  type (text, json, url, rtf, docx/pptx/xlsx, ipynb, pdf via pdftotext,
  zip members), flag credential- and PII-shaped strings, and stage text
  copies within the intake-lane limits plus a Drive upload list.

tests/test_dropbox_reconcile.py checks the content_hash against a value
reported by the Dropbox API, a one-byte negative control, the tier order
and the extractors. Scientific effect NONE; no inventory data is committed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
Adds harvest-links (collects download_link results, keeping only links
newer than --since as fetchable and every content_hash for classify) and
batches (25-id groups, the download_link maximum). This removes any need
to re-type single-use URLs. Test added.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
stage now marks loose files whose bytes travel inside an uploaded zip
(covered_by_zip) and never stages personal-looking file names (resume,
tax forms, bank statements, ...) for GitHub. pack deflates the Drive
upload list into size-capped zips that keep Dropbox paths and lists
every held file with its reason. report writes a private Markdown
summary of a classification. Tests cover each guard; removing any of
them fails a test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
…-list

The PR body states that an allow-list is required, but stage treated a
missing --allow as 'allow everything not PII-flagged'. Fail closed: with
no allow-list, no text copy is written to the GitHub packet directory;
the Drive upload list is still produced. Two tests cover both branches;
the first fails against the previous behaviour.

Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
harvest-fetch collects the connector's extracted text for each file from
session transcripts. A text is restored as the exact original only when
its bytes reproduce the file's Dropbox content_hash; the candidates
cover the connector's extra trailing newline, CRLF endings and legacy
single-byte encodings. Anything else (PDF or docx text, lossy
decodes) stays text-only: stage may copy it to GitHub but never lists
it as an original for Drive. Tests include the known 185-byte value and
a one-word edit that must not recover.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
stage now requires an explicit --allow for GitHub copies (Cursor Agent's
fix) also on the text-only path added for connector harvesting; the
harvest test names its allow-list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
A zip member with a bad CRC, a truncated archive or a malformed docx or
ipynb now yields extractor 'error:<Exception>' for that file or member,
and extract continues with the rest (cursor[bot] review of #172). The
new test fails against the previous code.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
OP-PRIVACY-20260927 quotes the owner's instruction of 2026-09-27 and gives
its operational meaning for every model. Personal information and
material unrelated to the project never go where others can see them,
and are purged when found; project material is published by repository
role. AGENTS.md now points to it next to the autonomy instruction.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
audits/dropbox_import/2026-09-27 holds the project-related files found in
Dropbox with no copy in any account repository or in the Drive source
map. 93 are byte-identical originals (each reproduces its Dropbox
content_hash); 14 are extracted text of PDF or Word files. MANIFEST.csv
gives hashes, a one-line summary and a suggested home for each;
NOT_IMPORTED.csv lists 26 project archives, figures and large logs that
could not be imported. Under OP-PRIVACY-20260927, personal material and
the owner's unrelated research are not published or named; only counts
appear. Scientific effect NONE.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
A catalog list raised AttributeError, a rows object was discarded and
written as [], and a failed git read exited 0 with an empty index.
index-drive and index-git now require a complete read before writing
--out. GitHub staging still requires an explicit --allow list.

Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
Brings in #184 (tool, byte-identical to this branch) and #185 (OP-PRIVACY),
so this branch now differs from main only by later work.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
The owner said the same day that their name and Gmail address are fine in
GitHub and need not be deleted. OP-PRIVACY item 1 no longer lists fuller
name forms or the Gmail address. The clarification is quoted verbatim with
its operational meaning: no redaction or history rewrite for those two, and
a file held back only for them may be published after the usual screen.
AGENTS.md says the same in one sentence. Every other exclusion is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
The owner said their Drive and Dropbox are private to them and only GitHub
is seen by others, and asked that privacy work stay proportionate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
@d6g8k5htny-coder
d6g8k5htny-coder marked this pull request as ready for review September 27, 2026 23:16
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
@d6g8k5htny-coder
d6g8k5htny-coder merged commit 0a168ca into main Sep 27, 2026
5 checks passed
@d6g8k5htny-coder
d6g8k5htny-coder deleted the claude/review-grok-github-uploads-gsthj3 branch September 27, 2026 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants