Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@ in this workspace. This includes replacing `main` and adding pages. Earlier
owner-only reservations and never-main directions are not continuing vetoes.
Do useful work without asking Dylan to authorize it again.

**Standing rule:** [OP-PRIVACY-20260927](governance/OP-PRIVACY-20260927.md). Never
publish Dylan's personal information or material unrelated to the project. If you
find either, purge it from GitHub and from the shared Drive.

## Working choices

Choose scope and tooling that advance the research. Read the actual current files
Expand Down
1 change: 1 addition & 0 deletions docs/WORKSPACE.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,4 +77,5 @@ acceptance; the [guide](FORMAL_VERIFICATION.md) and the
[rollout record](FORMAL_VERIFICATION_ROLLOUT_20260927.md) explain the boundary.

[Current authority](../governance/OP-AUTONOMY-20260923-v2.1.md) ·
[Privacy rule](../governance/OP-PRIVACY-20260927.md) ·
[Home](../README.md) · [Historical material](../history/2025/README.md)
43 changes: 43 additions & 0 deletions governance/OP-PRIVACY-20260927.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# OP-PRIVACY-20260927 — Personal information and unrelated material

Standing owner instruction, recorded 2026-09-27 by Anthropic / Claude (Claude Code)
during the Dropbox reconciliation. It applies to every participating model, in every
repository of this account and in the shared Google Drive, and it does not expire.

## Exact owner instruction

> Any of my personal information or any unrelated items found in the Dropbox that arnt related to the project should be purged from the GitHub or Google Drive as more than one model searched the drive and this is never ending rule. As there are tons of files in my drive and Dropbox and there are bound to be items in there not related to the project and therefore shouldn’t be with them and purged from those places where others will be able to see them. Other than that publish everything related to the project to GitHub in the appropriate locations and formats

## Operational meaning

1. **Personal information never enters a place others can see.** That covers
dates of birth, family members' names and other private individuals, legal
names beyond the public "Dylan Roy", licence, ID, account or policy numbers,
personal email addresses, phone numbers, street addresses and precise locations,
social media handles and profiles, health, finances, employment history and
private correspondence. Places others can see include every GitHub repository,
branch, pull request, issue and comment, and the shared Drive folders that
models read. Share links that carry access keys (for example Dropbox `rlkey=`
or Google `resourcekey=`) are treated the same way.
2. **Unrelated material stays out of project spaces.** The project is the
Universal Law research program described in [README.md](../README.md) and
[docs/RESEARCH_INDEX.md](../docs/RESEARCH_INDEX.md), together with its
prize-problem track and its own multi-model operations. The owner's other
research lines, personal documents and third-party material are not
brought into its repositories or shared folders.
3. **When either is found, purge it.** Remove it from current trees by a
reviewable change. Do not repeat the value in commit messages, PR bodies,
issues or logs; describe only its kind and location. Drive copies in shared
folders are trashed or moved out. The owner's private Dropbox keeps its
originals. A value that remains in Git history, in pull-request refs or in
caches is reported to the owner as a residual exposure; it is not declared
gone. Removing it from those needs a history rewrite or GitHub Support.
4. **Publish what belongs.** Material related to the project is published to
GitHub in the repository whose role fits it (see the cross-repository
contract in `governance-`), with provenance and without status promotion.
5. **Check before publishing.** Before any import from Drive, Dropbox or another
private source, screen for the items above. Any doubt means the item is held
privately; holding is always recoverable.

This rule narrows what may be published. It does not reduce the autonomy granted in
[OP-AUTONOMY-20260923-v2.1](OP-AUTONOMY-20260923-v2.1.md) for project work.
Loading